Minutes: User Agent telecon 5 Nov 2015

source: http://www.w3.org/2015/11/05-ua-minutes.html

User Agent Accessibility Guidelines Working Group Teleconference 05 Nov 2015

See also: IRC log  http://www.w3.org/2015/11/05-ua-irc
<http://www.w3.org/2015/11/05-ua-irc>
Attendees
Presentgreg, jim, kim, ericRegretsChairjimScribeallanj
Contents

   - Topics <http://www.w3.org/2015/11/05-ua-minutes.html#agenda>
      1. 4.1.4 Make DOMs Programmatically Available
      <http://www.w3.org/2015/11/05-ua-minutes.html#item01>
      2. 4.1.5 Make Content Interaction Programmatically Available
      <http://www.w3.org/2015/11/05-ua-minutes.html#item02>
   - Summary of Action Items
   <http://www.w3.org/2015/11/05-ua-minutes.html#ActionSummary>

------------------------------

<trackbot> Date: 05 November 2015

scribe allanj

<scribe> scribe: allanj
4.1.4 Make DOMs Programmatically Available

group discussing mobile accessibility, speech input, and "shared
responsibility of author, browser, user, at"

<scribe> *ACTION:* jeanne to update document from june 11 RESOLUTION:
change 4.1.4 to be DOMs Programmatically Available as fallback: If the user
agent accessibility API does not provide sufficient information to one or
more platform accessibility services, then Document Object Models (DOM),
must be made programmatically available to assistive technologies. (Level
A) [recorded in http://www.w3.org/2015/11/05-ua-minutes.html#action01]

<trackbot> Created ACTION-1088 - Update document from june 11 resolution:
change 4.1.4 to be doms programmatically available as fallback: if the user
agent accessibility api does not provide sufficient information to one or
more platform accessibility services, then document object models (dom),
must be made programmatically available to assistive technologies. (level
a) [on Jeanne F Spellman - due 2015-11-12].

it seems that the browsers do this because screen readers can get access to
the DOM based on the screen reader developer comments

all major browsers (except EDGE) on desktops provide some access to DOMs
that are being used by assistive technologies.

*RESOLUTION:*

all major browsers (except EDGE) on desktops provide some access to DOMs
that are being used by assistive technologies.

*RESOLUTION: all major browsers (except EDGE) on desktops provide some
access to DOMs that are being used by assistive technologies.*
4.1.5 Make Content Interaction Programmatically Available

close action-1088

<trackbot> Closed action-1088.

<Greg> As the Intent says "It is often more reliable for assistive
technology to use the programmatic method of access versus attempting to
simulate mouse or keyboard input."

<Greg> Thus, simulating keystrokes and mouse input is not supposed to be
enough to comply with this SC. Rather, if you can identify the control
through MSAA or the DOM, you can control it directly without having to
worry about scripts interfering with the keyboard or mouse events.

there are issues. applications work from keyboard, but when screen reader
is On, it traps space bar and sends something else, and application fails.

kp: notes similar things happen with speech input

*RESOLUTION: we assume based on group experience and comments from AT folks
that desktop browsers do this. Seems not available on mobile browsers.*

zakim: please part
Summary of Action Items *[NEW]* *ACTION:* jeanne to update document from
june 11 RESOLUTION: change 4.1.4 to be DOMs Programmatically Available as
fallback: If the user agent accessibility API does not provide sufficient
information to one or more platform accessibility services, then Document
Object Models (DOM), must be made programmatically available to assistive
technologies. (Level A) [recorded in
http://www.w3.org/2015/11/05-ua-minutes.html#action01]

[End of minutes]

-- 
Jim Allan, Accessibility Coordinator
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