W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2011

UAWG question

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 30 Jun 2011 17:23:04 -0500
Message-ID: <BANLkTi=YrXBj+a6UDuOff=028wFftbwZ3w@mail.gmail.com>
To: redux@splintered.co.uk, WAI-ua <w3c-wai-ua@w3.org>
Patrick,
we need some technical help.
at question is GL 4.1
http://www.w3.org/WAI/UA/2011/ED-UAAG20-20110609/#gl-AT-access

we have 4.1.4 which covers devices with DOMs...

4.1.4 Programmatic Availability of DOMs:
If the user agent implements one or more DOMs, they must be made
programmatically available to assistive technologies. (Level A)


we also have 4.1.5 which was intended to be technology agnostic,
non-DOM oriented. It describes most things a DOM would do.
the question is do we need it?
Does this really add anything beyond 4.1.1 and 4.1.2? see after 4.1.5.
We are not sure.

Your thoughts, please.

4.1.5 Access:
If a User Agent keeps an internal representation of the user content
in terms of element structure, relationships between elements, element
meaning, or some combination thereof, it must expose this internal
representation via an appropriate means (normally by using the
platform accessibility architecture or a programmatically available
DOM) (Level A) .

If a platform that does not support a platform accessibility API like
MSAA, and thus 4.1.1 does not apply, 4.1.2 would require the UA to
expose information about each element, but would not require it to
expose information about relationships between them such as any
*order*. 4.1.5 would do that.

4.1.1 Platform Accessibility Architecture:
Support a platform accessibility architecture relevant to the
operating environment. (Level A)

4.1.2 Name, Role, State, Value, Description:
For all user interface components including user interface, rendered
content, generated content, and alternative content, make available
the name, role, state, value, and description via a platform
accessibility architecture. (Level A)

4.1.3 Accessible Alternative:
If a component of the user agent user interface cannot be exposed
through the platform accessibility architecture, then provide an
equivalent alternative that is exposed through the platform
accessibility architecture. (Level A)

thanks to Greg L for some the notes in irc

-- 
Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 30 June 2011 22:23:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 30 June 2011 22:23:34 GMT