- From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Date: Sat, 21 Apr 2012 03:24:21 +0100
- 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>
On Fri, Apr 20, 2012 at 10:35 PM, Cynthia Shelly <cyns@microsoft.com> wrote: > For example, it would be incorrect to use the href attribute to link to a section marked with the hidden attribute. Since the content is not rendered, linking to it</del> would have unpredictable behavior</del><ins>would result in behavior the user does not expect</ins> , either dropping the user at a location with no rendered content, or failing to navigate. This still introduces a self-contradiction into the specifications, since the behavior is defined to navigate the user to a location with rendered content. There's no "or" and both your alternatives are wrong. > <p class="note">Any structure in the referenced element, including headings, links, tables, paragraphs, and form elements, will be lost. The text children of the element will be flattened to a string. As such, authors should only use this technique <del>for string content</del> </ins>where such flattened content will provide a good user experience</ins>. At the time of this writing, some screen reader products will read both the accessible name and accessible description, so authors should take care with the length of text provided via this method.</p> Where's the rationale for introducing such text under @hidden rather than in the ARIA specification or the WAI-ARIA section of the HTML5 spec? Saying "The text children of the element will be flattened to a string" is a direct contradiction of the ARIA specification which takes account of various elements and attributes in the calculation of the accessible name and description. Markup is a "string" so "string" is the wrong word to use here: http://en.wikipedia.org/wiki/String_(computer_science) Also, you didn't explain why "should" is the appropriate conformance language here… http://dev.w3.org/html5/spec/infrastructure.html#conformance-requirements -- Benjamin Hawkes-Lewis
Received on Saturday, 21 April 2012 02:25:14 UTC