WCAG2ICT recommendation for editorial change to 1.3.6 Identify Purpose (AAA) #4797
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WCAG2ICT task force is closely reviewing AAA success criteria.
BLUF: WCAG2ICT recommends replacing “region” in SC 1.3.6 with “section” and removing the former from the glossary.
1.3.6 Identify Purpose (AAA):
The TF found the term “regions” problematic to recontextualize for non-web documents and software. The TF also found the definition to be ambiguous. The TF could not come up with a non-web example which is an analog to landmark role provided in the NOTE of the glossary.
Regardless that the definition for section is also ambiguous, since region depends upon it, nothing is gained by having the additional term. Both the SC and the glossary term for region require programmatically determinability so the SC is redundant on that point. Nothing is achieved by having 1.3.6 use region (instead of section) and nothing is lost by by substituting section for region.
1.3.6 would then read:
The only reference to region is in SC 1.3.6, so with the substitution, the term can (and should be) removed from the glossary.
Please see WCAG2ICT Issue 538 for additional context.