- From: Jeanne Spellman <jeanne@w3.org>
- Date: Mon, 23 May 2011 08:19:39 -0400
- To: UAWG <w3c-wai-ua@w3.org>
- Message-ID: <4DDA50DB.3090808@w3.org>
This came in our Public Comments email address, so I am forwarding it for those who are not subscribed to that list. jeanne -------- Original Message -------- Subject: Some Comments on UAAG 5.3 Resent-Date: Sat, 21 May 2011 19:16:21 +0000 Resent-From: public-uaag2-comments@w3.org Date: Sat, 21 May 2011 15:09:40 -0400 From: Taylor, Suzanne <suzanne.taylor@pearson.com> To: public-uaag2-comments@w3.org Please find attached and pasted below some comments on 5.3 designed to include WAI-ARIA and warnings/error messages for content developers. Suzanne Taylor Guideline 5.3 (former 1.3) Support accessibility features of technologies. [Implementing 5.3 <http://www.w3.org/WAI/UA/2011/ED-IMPLEMENTING-UAAG20-20110406/#gl-imple ment-access-features> ] Summary: Implement the accessibility features of all the technologies you're using, such as supporting the platform's multitasking capabilities, HTML's alt attribute for images, and document your implementation. 5.3.1 (former 1.3.1) Accessibility Features: (suggesting separating content & platform SC) Implement and cite in the conformance claim the accessibility features of content specifications. Accessibility features are those that are either (Level A) : * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. 5.3.3 (former 1.3.1) Accessibility Features: (suggestion to include specs like WAI-ARIA) Implement and cite in the conformance claim W3C specifications designed to enhance accessibility of the content technology (e.g. WAI-ARIA) (Level AA) 5.3.4 (former 1.3.1) Accessibility Features: (suggesting error reporting for developers) If the user agent has an error consol, include errors (e.g. missing alt-text) related to the accessibility features of content specifications. Accessibility features are those that are either (Level A) : * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. 5.3.5 (former 1.3.1) Accessibility Features: (suggesting error & warning reporting for developers) Include warnings (e.g. role="application" has significant effects in screen readers- link to ARIA info) and errors (e.g. missing alt-text) related to the accessibility features of content specifications in a developer view or error consol. Accessibility features are those that are either (Level AA) : * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. Ideally, this would be part of general error and warning features, rather than a separate feature. 5.3.6 (former 1.3.1) Accessibility Features: (suggesting separating content & platform SC) Implement and cite in the conformance claim the accessibility features of platform technology <http://www.w3.org/WAI/UA/2011/ED-UAAG20-20110406/#def-Web-Content-Techn ology#def-Web-Content-Technology> specifications. Accessibility features are those that are either (Level A) : * identified as such in the specification or * allow authors to satisfy a requirement of WCAG.
Attachments
- application/msword attachment: UAAG_Comments_5.3_Suzanne_Taylor.doc
Received on Monday, 23 May 2011 12:20:01 UTC