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

Minutes: User Agent 6 August 2015 telecon

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 6 Aug 2015 13:47:00 -0500
Message-ID: <CA+=z1W=tm0-F66sRTEVhrjKjvf-8dPZyNU+xS=Px3gyQkhkp7w@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
source : http://www.w3.org/2015/08/06-ua-minutes.html

User Agent Accessibility Guidelines Working Group Teleconference 06 Aug 2015

See also: IRC log   http://www.w3.org/2015/08/06-ua-irc
<http://www.w3.org/2015/08/06-ua-irc>
Attendees
Presentjeanne, jim, gregRegretsChairjimScribeallanj
Contents

   - Topics <http://www.w3.org/2015/08/06-ua-minutes.html#agenda>
      1. 4.1.4 comment <http://www.w3.org/2015/08/06-ua-minutes.html#item01>
      2. comment on 1.7 user style sheets
      <http://www.w3.org/2015/08/06-ua-minutes.html#item02>
   - Summary of Action Items
   <http://www.w3.org/2015/08/06-ua-minutes.html#ActionSummary>

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

<trackbot> Date: 06 August 2015

http://www.w3.org/WAI/UA/work/wiki/Comments_%26_Responses_30_April_2015

<jeanne> Sorry, head down, lost track of time. OMW.

<scribe> scribe: allanj

open Item 1
4.1.4 comment

http://www.w3.org/WAI/UA/work/wiki/Comments_%26_Responses_30_April_2015

js: proposes referencing the ARIA mappings the AAPI (AAM) documents on an
informative basis to document what is sufficient.

http://www.w3.org/TR/2015/WD-html-aam-1.0-20150407/

Core Accessibility API Mappings - http://www.w3.org/TR/core-aam-1.1/

Accessible Name and Description: Computation and API Mappings [ACCNAME-AAM]

http://www.w3.org/TR/accname-aam-1.1/

Core Accessibility API Mappings [CORE-AAM]

http://www.w3.org/TR/core-aam-1.1/

HTML Accessibility API Mappings [HTML-AAM]

http://www.w3.org/TR/html-aam-1.0/

SVG Accessibility API Mappings [SVG-AAM]

http://www.w3.org/TR/svg-aam-1.0/

<jeanne> Assistive technologies need all possible information. Applications
such as user agents and assistive technologies use a combination of DOMs,
Accessibility Application Programming Interfaces (AAPI), native platform
APIs, and hard-coded heuristics to provide an accessible user interface and
accessible content. While most assistive technology vendors prefer to use
the AAPIs, if the AAPI cannot provide

<jeanne> enough access to the content, then it is the user agent's
responsibility to expose the DOM to assistive technology.

<jeanne> What is "sufficient" information can be determined by using the
WAI ARIA Accessibility API Mappings:

<jeanne> Core Accessibility API Mappings (CORE-AAM)

<jeanne> HTML Accessibility API Mappings (HTML-AAM)

<jeanne> Accessible Name and Description: Computation and API Mappings
(ACCNAME-AAM)

<jeanne> SVG Accessibility API Mappings (SVG-AAM)

gl: timeliness of aapi interaction is an issue

kp: if the aapi is too slow then users get confused.

js: too difficult to determine what is causing the delay - OS, platform,
browser, etc

kp: slow speech interaction is an ongoing problem

js: yes, it is an issue.

http://w3c.github.io/UAAG/UAAG20-Reference/#sc_414

js: delete old references?

ja: +1

<jeanne> +1

kp: +1

gl: +1

<Greg> +1

*RESOLUTION: accept adding the AAM as reference for SC 4.1.4*

What is "sufficient" information can be determined by using the WAI ARIA
Accessibility API Mappings:

Core Accessibility API Mappings (CORE-AAM)

HTML Accessibility API Mappings (HTML-AAM)

Accessible Name and Description: Computation and API Mappings (ACCNAME-AAM)

SVG Accessibility API Mappings (SVG-AAM)
comment on 1.7 user style sheets

<Kim>
http://developer.apple.com/mac/library/documentation/AppleApplications/Conceptual/SafariJSProgTopics/Tasks/DOM.html

<Kim> https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model

<jeanne> Mechanisms exist to allow users and authors to customize the
rendering of web content (e.g. CSS stylesheets).

*RESOLUTION: change intent of 1.7.1 - 3 to be*

Mechanisms exist to allow users and authors to customize the rendering of
web content (e.g. CSS stylesheets). Such customization is frequently used
to make web content accessible to a wide range of user needs. These success
criteria ensure that users can take full advantage of this ability to
customize stylesheets. Since different websites may require different style
changes to be readable,...

scribe: it is recommended that user agents provide a feature that lets the
user specify which stylesheet should be automatically applied to different
web pages as they are loaded (e.g. based on a list of domain names or URL
templates).

js: changed CSS to "stylesheet" in 1.7.4

<scribe> DONE WITH COMMENTS!

*RESOLUTION: Publish the document*

close item 1

close item 2

open item 3

list of google extensions developed by google in support of UAAG

https://chrome.google.com/webstore/detail/caret-browsing/fklpgenihifpccgiifchnihilipmbffg?hl=en-GB

https://chrome.google.com/webstore/detail/image-alt-text-viewer/hinbolcnfifkhlcehoakdledkfjiaeeg?hl=en-GB

https://chrome.google.com/webstore/detail/high-contrast/djcfdncoelnlbldjfhinnjlhdjlikmph?hl=en-GB

https://chrome.google.com/webstore/detail/long-descriptions-in-cont/ohbmencljkleiedahijfkagnmmhbilgp?hl=en-GB

https://chrome.google.com/webstore/detail/dvorak-left/daedidciajfkjpjfmailopfppehmdlkn?hl=en-GB

https://chrome.google.com/webstore/detail/dvorak-right/ibmblmkjihglholefminaiddohamopnn?hl=en-GB

<Greg> Doing a web search for "offered by Google Accessibility" will show a
number of other accessibility add-ins for Chrome developed by Google
itself. In addition to those you list, it includes "Color Enhancer",
"Animation Policy", etc.

plugins run only on explicit request - chrome - settings - privacy -
content settings - plugins - let me choose when to run plugins (and manage
exceptions)

<Greg> Animation Policy - Chrome Web Store

<Greg>
https://chrome.google.com/webstore/detail/animation-policy/ncigbofjfbodhkaffojakplpmnleeoee?hl=en

<Greg> would apply to 2.11.1.

<Greg> "Run animations only once, or disable animation completely. Disable
image animation, or make animations run only once. Works on all animated
image formats and animated SVG. Does not affect video."

<Greg> Image Alt Text Viewer - Chrome Web Store
https://chrome.google.com/webstore/detail/image-alt-text-viewer
/hinbolcnfifkhlcehoakdledkfjiaeeg?hl=en "Replace images with their alt
text. Adds a "browser action" icon to your toolbar. When you press it, it
replaces all images in the current tab with their alt text, plus a button
to Undo and turn them back. Useful for testing sites for accessibility." Re

<Greg> 1.1.1.

<Greg> HTML5 Audio Description (via text to speech) - Chrome Web Store
https://chrome.google.com/webstore/detail/html5-audio-description-v/jafenodgdcelmajjnbcchlfjomlkaifp?hl=en
"This extension plays audio description track elements of HTML5 videos via
Chrome text to speech extension." This applies to 1.1.1 ("Render
alternative content").
Summary of Action Items [End of minutes]

-- 
[image: http://www.tsbvi.edu] <http://www.tsbvi.edu>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
Received on Thursday, 6 August 2015 18:47:29 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 6 August 2015 18:47:29 UTC