18:00:11 RRSAgent has joined #ua 18:00:11 logging to http://www.w3.org/2015/11/05-ua-irc 18:00:13 RRSAgent, make logs public 18:00:13 Zakim has joined #ua 18:00:15 Zakim, this will be WAI_UAWG 18:00:15 I do not see a conference matching that name scheduled within the next hour, trackbot 18:00:16 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 18:00:16 Date: 05 November 2015 18:00:24 chair: jim 18:00:28 scribe allanj 18:00:33 scribe: allanj 18:00:45 rrsagent, set logs public 18:06:00 Greg has joined #ua 18:08:29 Kim has joined #ua 18:14:00 topic: 4.1.4 Make DOMs Programmatically Available 18:28:13 group discussing mobile accessibility, speech input, and "shared responsibility of author, browser, user, at" 18:36:27 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) 18:36:27 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]. 18:37:53 it seems that the browsers do this because screen readers can get access to the DOM based on the screen reader developer comments 18:39:56 all major browsers (except EDGE) on desktops provide some access to DOMs that are being used by assistive technologies. 18:40:20 RESOLUTION: 18:40:22 all major browsers (except EDGE) on desktops provide some access to DOMs that are being used by assistive technologies. 18:40:34 RESOLUTION: all major browsers (except EDGE) on desktops provide some access to DOMs that are being used by assistive technologies. 18:40:55 topic: 4.1.5 Make Content Interaction Programmatically Available 18:47:42 close action-1088 18:47:42 Closed action-1088. 18:47:57 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." 18:48:57 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. 18:49:54 there are issues. applications work from keyboard, but when screen reader is On, it traps space bar and sends something else, and application fails. 18:50:12 kp: notes similar things happen with speech input 18:52:21 RESOLUTION: we assume based on group experience and comments from AT folks that desktop browsers do this. Seems not available on mobile browsers. 18:53:55 rrsagent, make minutes 18:53:55 I have made the request to generate http://www.w3.org/2015/11/05-ua-minutes.html allanj 18:55:40 zakim: please part 18:55:53 present+ greg, jim, kim, eric 18:56:05 rrsagent, make minutes 18:56:05 I have made the request to generate http://www.w3.org/2015/11/05-ua-minutes.html allanj 18:56:17 zakim, please part 18:56:18 Zakim has left #ua 18:56:18 leaving. As of this point the attendees have been greg, jim, kim, eric 18:56:29 rrsagent, make minutes 18:56:29 I have made the request to generate http://www.w3.org/2015/11/05-ua-minutes.html allanj