- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Fri, 20 Apr 2012 09:53:46 +1000
- To: Cynthia Shelly <cyns@microsoft.com>
- Cc: Laura Carlson <laura.lee.carlson@gmail.com>, Janina Sajka <janina@rednote.net>, 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>
Hmm in the "Details" section the proposed change has this sentence: "At the time of this writing, some screen reader products will read both the accessible name and and accessible name, so authors should take care with the length of text provided via this method." I'm sure there's something wrong with repeating "the accessible name"... ? Cheers, Silvia. On Fri, Apr 20, 2012 at 9:25 AM, Cynthia Shelly <cyns@microsoft.com> wrote: > 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 >
Received on Thursday, 19 April 2012 23:54:35 UTC