See also: IRC log
<trackbot> Date: 17 April 2014
comments document: http://www.w3.org/WAI/UA/2014/LCcomments.html
<scribe> scribe: allanj
do we want to have a f2f there?
jr: +1
kp: +1
<jeanne> +1
gl: +1
kp: first 2 days?
gl: yes
Resolution: we are having a F2F in Santa Clara
open item 2
js: git - exploring for several
months, jeanne has had some training
... proposing the group use it for some time, to see if we like
it. if we like it can move to W3 space
... advantages - anyone in group could edit doc. robust
history, track changes, includes bug tracking system, etc.
etc.
kp: first step, download?
js: it is a web repository, no downloads needed. just create an account
w3c.github.io/UAAG/UAAG20/
3 ways to edit...jeanne gives permission, edit in browser, or download a local version of the file - edit with whatever tool - then upload again
or you can FORK the file in your own account or locally on your computer
w3 backs up all w3 space in github
<jeanne> https://github.com/jspellman/UAAG
js: after forking, you can go to
the UAAG page, and create a PULL request, and JS can fetch the
changes, one at a time
... you can also create a BUG on the spec, when the document is
updated, the bug is updated, and tracks everything all the
time.
... send Jeanne credentials you want to use and she will create
accounts
<jeanne> http://jspellman.github.io/UAAG/UAAG20/
above link is where to see the final product
js: best practice...make many
small changes, and commit individually with comments on what
was done
... april 10 updated 1.9.1
... if doing a proposal...could fork the spec, do proposal in
the fork, and send everyone a link
... fork to your account, and send a link to your account (not
the UAAG doc).
... forking allows creating a new branch, when finalized, it
can be merged with the 'master' document
http://www.w3.org/2011/webtv/wiki/Use_Case
http://www.w3.org/2011/webtv/wiki/Main_Page
waiting for coordination with other parties.
open item 3
<Jan> URL?
<jeanne> http://jspellman.github.io/UAAG/UAAG20/#abstract
original:
UAAG 2.0 guides developers in designing user agents that make the Web more accessible to people with disabilities. User agents include browsers, media players and applications that retrieve and render Web content. A user agent that follows UAAG 2.0 will improve accessibility through its own user interface and its ability to communicate with other technologies, including assistive technologies. UAA
G and supporting resources are also intended to meet the needs of different audiences, including developers, policy makers, and managers. All users, not just users with disabilities, will benefit from user agents that follow UAAG 2.0.
In addition to helping developers of browsers and media players, UAAG 2.0 benefits developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a user agent that follows UAAG 2.0. Assistive technologies not addressed directly by UAAG 2.0 (e.g. braille rendering) are still essential to ensuring Web access for some users...
scribe: with disabilities.
The "User Agent Accessibility Guidelines 2.0" (UAAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).
proposed:
<Jan> Comment spreadsheet: http://www.w3.org/WAI/UA/2014/LCcomments.html
UAAG 2.0 guides developers in designing user agents that make the Web more accessible to people with disabilities. User agents include browsers, media players and applications that retrieve and render Web content. A user agent that follows UAAG 2.0 will improve accessibility through its own user interface and its ability to communicate with other technologies, including assistive technologies. UAA
G and supporting resources are also intended to meet the needs of different audiences, including developers, policy makers, and managers. All users, not just users with disabilities, will benefit from user agents that follow UAAG 2.0.
In addition to helping developers of browsers and media players, UAAG 2.0 benefits developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a user agent that follows UAAG 2.0. Assistive technologies not addressed directly by UAAG 2.0 (e.g. braille rendering) are still essential to ensuring Web access for some users...
scribe: with disabilities.
The "User Agent Accessibility Guidelines 2.0" (UAAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).
LC version
UAAG 2.0 provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities. User agents include browsers, media players and applications that retrieve and render Web content. A user agent that conforms to these guidelines will promote accessibility through its own user interface and its ability to communicate with other technologies (especially ass
istive technologies). All users, not just users with disabilities, should find conforming user agents to be more usable.
In addition to helping developers of browsers and media players, UAAG 2.0 will benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by UAAG 2.0 (e.g. assistive technologies for braille rendering) will be essential to ensuring Web access for...
scribe: some users with disabilities.
The "User Agent Accessibility Guidelines 2.0" (UAAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).
proposed change
UAAG 2.0 guides developers in designing user agents that make the Web more accessible to people with disabilities. User agents include browsers, media players and applications that retrieve and render Web content. A user agent that follows UAAG 2.0 will improve accessibility through its own user interface and its ability to communicate with other technologies, including assistive technologies. UAA
G and supporting resources are also intended to meet the needs of different audiences, including developers, policy makers, and managers. All users, not just users with disabilities, will benefit from user agents that follow UAAG 2.0.
In addition to helping developers of browsers and media players, UAAG 2.0 benefits developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a user agent that follows UAAG 2.0. Assistive technologies not addressed directly by UAAG 2.0 (e.g. braille rendering) are still essential to ensuring Web access for some users...
scribe: with disabilities.
The "User Agent Accessibility Guidelines 2.0" (UAAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).
jr: not sure it is really an
abstract to the document. reads more like a section on "who
will benefit"
... should touch on 5 areas/principles
eric: agree
... something about conformance is needed
<Jan> http://www.w3.org/TR/WCAG20/#abstract
kp: tried to address the comment, but seems the abstract should be an abstract
<jeanne> ACTION: jeanne to revise the Abstract to include more about the document structure: Principles, levels, conformance, and structure (principle, guideline, success criteria [recorded in http://www.w3.org/2014/04/17-ua-minutes.html#action01]
<trackbot> Created ACTION-969 - Revise the abstract to include more about the document structure: principles, levels, conformance, and structure (principle, guideline, success criteria [on Jeanne F Spellman - due 2014-04-24].
Topi AP02 2.6.1 access and activation of input methods
comment: In the specific case of this one: 2.6.1 Allow Access and Activation of Input Methods: I'm hopeful this one will be solved by IndieUI Events.
<Greg> 2.6.1 Allow Access and Activation of Input Methods: The user agent provides a means for the user to determine recognized input methods explicitly associated with an element, and a means for the user to activate those methods in a modality independent manner. (Level AA)
gl: IndieUI doesn't exist yet
js: we can only mention it informatively.
<Greg> Could include a link to IndieUI in our Related Resources.
response: UAAG will add a link to IndieUI in the Implementing Resources section for 2.6.1
<Greg> http://lists.w3.org/Archives/Public/public-uaag2-comments/2014Jan/0001.html
limiting the user configuration, what about using extensions?
would chrome be compliant is using extensions?
gl: would be compliant, very similar to AP01 (user style sheets, user scripting)
<Greg> We certainly allow use of extensions. We can adapt the wording we came up with AP01, which was "In order to claim compliance, the claimant must demonstrate that solutions, and any required additional components, are available to non-expert users. Enabling the creation of such solutions is not by itself sufficient."
<Greg> We could add "We strongly recommend any such extensions or add-ons be included with the product, even if they are not active by default."
ja; concerns about UAs changing and extensions no longer working
scribe: would want browser developed extensions that are updated with new versions of the UA
eric: nothing in the conformance
specifies whether the extension is activated or not. for
platform claimant must state the actual configuration changes
made to the platform
... conformance says document the extensions used, but not
whether they must be activated or are included with the
install
jr: every browser has its own way of handling extensions
<Jan> We already ask for:
<Jan> Name and manufacturer
<Jan> Version number or version range
<Jan> Required patches or updates, human language of the user interface and documentation
<Jan> Configuration changes to the user agent that are needed to meet the success criteria (e.g. ignore author foreground/background color, turn on Carat Browsing)
<Jan> Plugins or extensions (including version numbers) needed to meet the success criteria (e.g. mouseless browsing)
eric: this should cover it.
jr: wouldn't mind adding some language about turn extension on.
WW: introduces self, and a bit
about WebTV, developing a11y requirements
... comments, use cases due end of May
WW to come to meeting in 2 weeks to discuss WebTV
ja: seems "turning on extension" wording would be picky
jr: change the order of the list plugins first then configuration, would solve the problem
<Jan> EDITS:
<Jan> Name and manufacturer
<Jan> Version number or version range
<Jan> Required patches or updates, human language of the user interface and documentation
<Jan> Plugins or extensions (including version numbers) needed to meet the success criteria (e.g. mouseless browsing)
<Jan> Configuration changes to the user agent, plugins and/or extensions that are needed to meet the success criteria (e.g. ignore author foreground/background color, turn on Carat Browsing)
+1
<jeanne> ACTION: jeanne to draft sentences for the Introduction with Kim to make it more clear that extensions are allowed to meet conformance. [recorded in http://www.w3.org/2014/04/17-ua-minutes.html#action02]
<trackbot> Created ACTION-970 - Draft sentences for the introduction with kim to make it more clear that extensions are allowed to meet conformance. [on Jeanne F Spellman - due 2014-04-24].
eric: +1 to reinforce extensions.
<scribe> ACTION: jeanne to craft response statement to CR01 based on AP01 and stuff in minutes above [recorded in http://www.w3.org/2014/04/17-ua-minutes.html#action03]
<trackbot> Created ACTION-971 - Craft response statement to cr01 based on ap01 and stuff in minutes above [on Jeanne F Spellman - due 2014-04-24].
eric: should also reinforce platform capabilities in the draft of the Abstract for action 970
concerned about line, font settings
js: we have another comment on
this, seems our approach is flawed.
... comments are saying we are too specific.
... we are too html and css centric, and specific
gl: sent comments for CR in January
http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JanMar/0016.html
DM: * Settings that allow the user
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Mam/May/ Found Scribe: allanj Inferring ScribeNick: allanj Default Present: Jim_Allan, Jeanne, Greg_Lowney, Kim_Patch, Jan, Eric, wuwei Present: Jim_Allan Jeanne Greg_Lowney Kim_Patch Jan Eric wuwei Regrets: Kelly Found Date: 17 Apr 2014 Guessing minutes URL: http://www.w3.org/2014/04/17-ua-minutes.html People with action items: jeanne[End of scribe.perl diagnostic output]