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

Fwd: Re: our SC related to DOM and A11y API

From: Jim Allan <jimallan@tsbvi.edu>
Date: Fri, 22 May 2015 11:59:58 -0500
Message-ID: <CA+=z1WkaLEhaL7mZ1hSu6EGzXzLQ5OX9gpy7aGewAP8hY1BT0w@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
---------- Forwarded message ----------
From: "Richard Schwerdtfeger" <schwer@us.ibm.com>
Date: May 22, 2015 11:34 AM
Subject: Re: our SC related to DOM and A11y API
To: "Jim Allan" <jimallan@tsbvi.edu>
Cc:

Hi Jim,

I am going on vacation, so here is my best shot in the short time I have.
:-)

4.1.1

For APIs you need:

Microsoft Active Accessibility(MSAA)/IAccessible2  - These need to be
combined to a single platform API mapping. It is used by Chrome and Firefox
UI Automation
MSAA/UIA Express Used in IE but will not be used in Edge)
For Linux: ATK/ATSPI
for Mac:
MAC OSX Accessibility Protocol Mac OS

4.1.2

You need to add the bounding rectangle
You need to add Relationships
For text you need a caret position, selected content, text location and
bounds, font and color (foreground and background final format)
 information. You must have bound information to support Braille devices


4.1.4
You don't need to make the DOM available if you can access all the
information needed from the accessibility API mappings


I see you have additional properties but these really are part of the core
pieces. in 4.1.2

Your document should be referencing:

*HTML Accessibility API Mappings 1.0*
<http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CCUQFjAA&url=http%3A%2F%2Fwww.w3.org%2FTR%2Fhtml-aam-1.0%2F&ei=JFFfVcP6B_GasQSvrYPYDA&usg=AFQjCNFzHMIz-9PJPr9SP5OpPgmVNi5Xsw&sig2=qJMNRe59eNz87PKqYaSV2A&bvm=bv.93990622,d.cWc>
*Core Accessibility API Mappings 1.1* <http://www.w3.org/TR/core-aam-1.1/>
*SVG Accessibility API Mappings* <http://www.w3.org/TR/svg-aam-1.0/>
*Accessible Name and Description: Computation and API*

There will be more



Rich Schwerdtfeger

[image: Inactive hide details for Jim Allan ---05/21/2015 01:24:17 PM---can
you review and make comments 4.1.1 Support Platform Accessi]Jim Allan
---05/21/2015 01:24:17 PM---can you review and make comments 4.1.1 Support
Platform Accessibility Services:

From: Jim Allan <jimallan@tsbvi.edu>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
Date: 05/21/2015 01:24 PM
Subject: our SC related to DOM and A11y API
------------------------------



can you review and make comments

*4.1.1 Support Platform Accessibility Services: *

The user agent supports relevant platform accessibility services
<http://w3c.github.io/UAAG/UAAG20/#def-access-platform-arch>. (Level A)


   *Reference for 4.1.1*
   <http://w3c.github.io/UAAG/UAAG20-Reference/#sc_411>


*4.1.2 Expose Basic Properties: *

For all user interface components (including UA user interface
<http://w3c.github.io/UAAG/UAAG20/#def-ua-ui>, rendered content
<http://w3c.github.io/UAAG/UAAG20/#def-rendered-content>, and generated
content) the user agent makes available
<http://w3c.github.io/UAAG/UAAG20/#def-programmatically-avail> the
following properties and any change notifications via a platform
accessibility service
<http://w3c.github.io/UAAG/UAAG20/#def-access-platform-arch>: (Level A)

   - Name
   - Role
   - State
   - Value
   - Selection
   - Focus
   - Change state/value notifications

   *Reference for 4.1.2*
   <http://w3c.github.io/UAAG/UAAG20-Reference/#sc_412>


*4.1.3 Provide Equivalent Accessible Alternatives: *

If UA user interface <http://w3c.github.io/UAAG/UAAG20/#def-ua-ui>
functionality
cannot be exposed through platform accessibility services
<http://w3c.github.io/UAAG/UAAG20/#def-access-platform-arch>, then the user
agent provides equivalent functionality that can be exposed through the
platform accessibility service. (Level A)


   *Reference for 4.1.3*
   <http://w3c.github.io/UAAG/UAAG20-Reference/#sc_413>


*4.1.4 Make DOMs Programmatically Available: *

If the user agent implements one or more Document Object Models
<http://w3c.github.io/UAAG/UAAG20/#def-dom> (DOM), they must be made
programmatically
available <http://w3c.github.io/UAAG/UAAG20/#def-programmatically-avail> to
assistive technologies. (Level A)


   *Reference for 4.1.4*
   <http://w3c.github.io/UAAG/UAAG20-Reference/#sc_414>


*4.1.5 Make Content Interaction Programmatically Available: *

If the user can interact with content (e.g. by checking a box or editing a
text area), the same degree of interaction is programmatically available.
(Level A)


   *Reference for 4.1.5*
   <http://w3c.github.io/UAAG/UAAG20-Reference/#sc_415>


*4.1.6 Expose Additional Properties: *

For all user interface components (including UA user interface
<http://w3c.github.io/UAAG/UAAG20/#def-ua-ui>, rendered content
<http://w3c.github.io/UAAG/UAAG20/#def-rendered-content>, and generated
content) the user agent makes available
<http://w3c.github.io/UAAG/UAAG20/#def-programmatically-avail> the
following properties and any change notifications via a platform
accessibility service
<http://w3c.github.io/UAAG/UAAG20/#def-access-platform-arch>: (Level AA)

   - Bounding dimensions and coordinates
   - Font family of text
   - Font size of text
   - Foreground and background color for text
   - Highlighting
   - *Keyboard commands* <http://w3c.github.io/UAAG/UAAG20/#def-command>



-- 
 <http://www.tsbvi.edu/>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/*
<http://www.tsbvi.edu/>
"We shape our tools and thereafter our tools shape us." McLuhan, 1964


graycol.gif
(image/gif attachment: graycol.gif)

Received on Friday, 22 May 2015 17:00:23 UTC

This archive was generated by hypermail 2.3.1 : Friday, 22 May 2015 17:00:25 UTC