WCAG2ICT FPWD Comment from IBM: Inconsistency between 1.4.12 Text Spacing and 4.1.3 Status Messages

[maryjom]

In WCAG2ICT both 1.4.12 Text Spacing and 4.1.3 Status Messages have the language where they only apply to "content implemented using markup language", but the guidance applies them differently to non-web software. These need to be made consistent, and it makes sense to apply the 1.4.12 Text Spacing requirement whenever software supports these text modifications.

4.1.3 allows this SC to be applicable to software - even when not implemented using markup language when it supports programmatic identification of status messages. Language is:

In [content implemented using markup languages, or that supports status message notifications], status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

1.4.12 Text Spacing kept the limitation "in content implemented using markup language" but does not apply the SC more broadly to software that supports changing any of the text spacing options. Language is:

[For non-web documents or software] content implemented using markup languages [in a way that supports modification of] the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:

Suggested modification of 1.4.12 language:
I have a couple of potential options for handling this.

Option 1

[For non-web documents or software] content [implemented using markup languages or software in a way that supports modification of] the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:

Option 2

[For non-web documents or software] content [implemented using markup languages, or that supports modification of] the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:

[pday1]

I prefer the latter option as it slightly broader, but am happy with either possibilities

[maryjom]

I think these two suggestions can go in front of the TF for review. Will add to the survey due 31 January.

[bruce-usab]

If we get consensus on an approach for one, I agree that should be used for the other. With 4.1.3, think I have sorted out the two oppositional approaches as taken literally and go big.

If the TF can rule one or the other out, then we iterate.

[maryjom]

I've created a Google doc for 1.4.12 Text Spacing so we can tweak the guidance for the consistent approach we developed during the 16 Feb. sub-group meeting. See the minutes for 16 Feb.

[maryjom]

Here are the survey results for the proposals in the survey description.

[bruce-usab]

If the survey were still open, what I would say is that SC 1.4.12 can be used as-is without any word substitution whatsoever. We can add notes for products with closed functionality if we like.

In content implemented using markup languages that support the following text style properties...

SC 1.4.12 is already tightly scoped. It works just fine as-is for non-web documents and non-web software.

WCAG2ICT might need to caveat the definition for style properties. Have we started to revisit updating Comments on Definitions in WCAG 2 Glossary?

[maryjom]

The TF had 2 different surveys regarding changes to the editor's draft with follow-up TF discussions that reached consensus on the text:

• Survey on 1.4.12 Text spacing - see the minutes for the 29 Feb. meeting
• Survey on 4.1.3 Status Messages - see the minutes for the 22 Feb. meeting

General guidance and the content in the section on SC Problematic for Closed Functionality were updated.

The agreed changes were implemented in PRs #316 and #314.

[maryjom]

FINAL WCAG2ICT answer:

Thank you for your review and comment on WCAG2ICT. The task force reviewed the language for the 1.4.12 Text Spacing and 4.1.3 Status Messages Success Criteria and agree that these should be changed to better align in their interpretation. We considered your proposed text, but upon further consideration decided to take an approach that better aligns with the WCAG2ICT Task Force work statement's scope of work. In that document, it is considered "out of scope" to propose changes to WCAG 2.x or develop any normative requirements. Therefore, we determined the WCAG2ICT Task Force is not at liberty to expand the scope of the WCAG success criteria beyond what WCAG states - to "content implemented using markup languages".

However, we do agree that it makes sense to more broadly apply to non-web software, and so new notes were developed to indicate that. This will inform outside standards development organizations that they should consider broadening the scope or writing an additional requirement that parallels the WCAG criterion, as they see fit.

You can find the changes to 1.4.12 Text Spacing in PR #316 and to 4.1.3 Status Messages in PR #314. Both have been merged into the editor's draft.

[bruce-usab]

In regards to a question to me from @maryjom on the list...

WCAG2ICT might need to caveat the definition for style properties. Have we started to revisit updating Comments on Definitions in WCAG 2 Glossary?

It's fine.

[maryjom]

See survey results indicating unanimous approval of the draft answer to this issue. TF resolution (Finalize the answer to issue 216, as-is.) documented on 14 March.

[mitchellevan]

To call attention to this message #216 (comment), I've filed the following issue against EN 301 549: Apply SC 4.1.3 Status Messages to native code in software #448