1-3-5 Revision

Proposed Revision for contextual information from list 20-12-2017

Identify Purpose (new label) AAA

In content implemented using markup languages, the purpose of User Interface Components, icons, and regions can be programmatically determined.

Definitions

region: a perceivable, programmatically determined section containing content. Note: Any area designated with a landmark role would be a region.

334

https://github.com/w3c/wcag21/issues/334

Proposed response (from AWK): The specific language has been removed from this SC. The point that a website could invent their own vocabulary is valid, as this would be allowed by the current version of the SC, but there would also need to be accessibility support for the vocabulary used to satisfy the SC. The need for support by user agents will make the custom approach substantially less viable.

342

https://github.com/w3c/wcag21/issues/342

Proposed response (from AWK): The point that a website could invent their own vocabulary is valid, as this would be allowed by the current version of the SC, but there would also need to be accessibility support for the vocabulary used to satisfy the SC. The need for support by user agents will make the custom approach substantially less viable.

399

https://github.com/w3c/wcag21/issues/399

Proposed response (from AWK): This SC is paired with a AA SC, "Identify Common Purpose". The AA SC is focused on a constrained set of defined purposes, which the WG feels is testable, and this SC covers an expanded set of purposes.

410

https://github.com/w3c/wcag21/issues/410

Proposed response (from AWK): The specific language mentioned in this comment has been removed from this SC.

428

https://github.com/w3c/wcag21/issues/428

Proposed response (from AWK): The specific language mentioned in this comment has been removed from this SC. This SC differs from 4.1.2 because that SC requires a name for UI Components, but this SC requires a programmatically determined purpose, which is different than the name. We will clarify this in the Understanding document.

429

https://github.com/w3c/wcag21/issues/429

Proposed response (from AWK): Similar to the response to #428, this SC is focused on the programmatically defined purpose rather than on the information, structure, and relationships covered through presentation. We will clarify this in the Understanding document.

430

https://github.com/w3c/wcag21/issues/430

Proposed response (from AWK): We have added a definition for region. Please review this in the editor's draft.

431

https://github.com/w3c/wcag21/issues/431

Proposed response (from AWK): Related to the specific question, an image of an asterisk used to indicate a required field could have its purpose identified using schema.org metadata, or any other metadata with accessibility support necessary to provide benefit to end users.

432

https://github.com/w3c/wcag21/issues/432

Proposed response (from AWK): The specific language has been removed from this SC. The point that a website could invent their own vocabulary is valid, as this would be allowed by the current version of the SC, but there would also need to be accessibility support for the vocabulary used to satisfy the SC.

487

https://github.com/w3c/wcag21/issues/487

Proposed response (from AWK): The intent is not to encourage use of the title attribute. We will clarify this in the Understanding and Techniques documents.

547

https://github.com/w3c/wcag21/issues/547

Proposed response (from AWK): There is planned work within ARIA, but using COGA semantics in ARIA is not the only way to satisfy this SC.