- From: David MacDonald <david100@sympatico.ca>
- Date: Wed, 23 Mar 2016 17:56:04 -0400
- To: Jeanne Spellman <jspellman@spellmanconsulting.com>
- CC: w3c WAI List <w3c-wai-ig@w3.org>
Received on Wednesday, 23 March 2016 21:56:35 UTC
I'm not sure if this was sparked by my IAAP/Twitter post about sighted keyboard users. But if so, I've updated my article. http://davidmacd.com/blog/sighted-keyboard-only-user.html On Wed, Mar 23, 2016 at 11:26 AM, Jeanne Spellman < jspellman@spellmanconsulting.com> wrote: > > > On 3/22/2016 6:11 PM, Phill Jenkins wrote: > > UAAG 2.0 Draft does not seem to have a success criteria to render the > invisible labels that were added to meet success criteria. > Is there a gap in the requirements between WCAG and UAAG that > disproportionately affect sighted users with cognitive disabilities? > > > Phill, > > UAAG 2.0 does address this issue, although it does not explicitly state > that it must be visual. The examples in the UAAG 2.0 reference are for a > low vision user and for a user with a cognitive disability. > https://www.w3.org/TR/UAAG20/#gl-info-link > > 1.10.1 Show Related Elements: The user can access the information from > explicitly-defined relationships in the content, including at least the > following: (Level AA) > > calculated accessible name for images > calculated accessible name for controls (e.g. form fields, buttons) > caption for a table > row and column labels for a table cell > > > FYI, UAAG 2.0 is no longer a draft, but is a completed Guideline published > as a W3C Note. > > jeanne >
Received on Wednesday, 23 March 2016 21:56:35 UTC