- From: Janina Sajka <janina@rednote.net>
- Date: Thu, 19 Apr 2012 20:28:46 -0400
- To: Cynthia Shelly <cyns@microsoft.com>
- Cc: Laura Carlson <laura.lee.carlson@gmail.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, John Foliot <john@foliot.ca>, Joshue O Connor <joshue.oconnor@cfit.ie>, Judy Brewer <jbrewer@w3.org>, "david100@sympatico.ca" <david100@sympatico.ca>, Richard Schwerdtfeger <schwer@us.ibm.com>, James Nurthen <james.nurthen@oracle.com>, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, "Jonas Sicking (jonas@sicking.cc)" <jonas@sicking.cc>
Two suggestions on a quick read ... 1.) The last sentence before: "Feedback from Browser Implementers" seems to need a follow-on, something like, ... Because authors rarely run their content through conformance checkers, authors are likely to point at @hidden content from aria-describedby whether or not we forbid them from doing so. Therefore it is incumbant to document what can, and what cannot be achieved through these techniques. 2.) At the crux of this CP we have a paragraph break where I think one doesn't belong. If I'm correct, the paragraph break hampers comprehension of our key assertions. Am I wrong? Shortly after the quotation from UAIG 5.1.2, there is the following, with paragraph break: It sounds as though a note clarifying this should be added to UAIG. However, section 5.6.1.3. Text Alternative Computation of UIAG states explicitly that authors can provide strings for the accessible name and description via aria references to hidden elements, My suggestion is to tie the last sentence into the next paragraph, something like: It may seem as though a note clarifying this should be added to UAIG. However, section 5.6.1.3. Text Alternative Computation of UIAG states explicitly that authors can provide strings for the accessible name and description via aria references to hidden elements, ... " PS: I think of this as the crux of this CP inasmuch as this is basically saying: "Consider all the facts to arrive at correct conclusions, not some of the facts." Janina Cynthia Shelly writes: > OK, I think I'm close. > http://www.w3.org/html/wg/wiki/Correct_Hidden_Attribute_Section_v2#Accessibility_API_mappings > > 1) rewrote summary to talk more about @hidden being simpler than CSS, rather than @aria-describedby being simpler than something else > 2) changed example to one using an input and a label rather than an image with a short and long description > 3) added section on what happens in the API when the item is hidden or not hidden > 4) added the aria-labelledby row to the table from UIAG to show that the behavior is not just for description > 5) changed the details section to offer stronger advice to authors not to do this with structured content. > 6) minor copy edits, adding <code> styling, etc. > > Jonas, this is an attempt to merge your proposal and Laura's, so that we can get to a single proposal for Issue 204. > > Thanks, > Cynthia -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Chair, Open Accessibility janina@a11y.org Linux Foundation http://a11y.org Chair, Protocols & Formats Web Accessibility Initiative http://www.w3.org/wai/pf World Wide Web Consortium (W3C)
Received on Friday, 20 April 2012 00:29:24 UTC