See also: IRC log
<trackbot> Date: 23 February 2012
SPREADSHEET, so we can make decisions on Thursday. there are 115 SC
to add your thoughts (numbers) to. Also, add implementations if you
discussion on the A11y Professional Association
<scribe> scribe: JimAllan
kf: question: will we be able to
do the spreadsheet? or should we try something else?
... why is this taking so long.
gl: 115 rows,by 13 columns and
comments....its a lot. SS is difficult
... doesn't work well for me, just navigating.
kf: what can we do and call it success.
js: go down the implementation column and see what we know about browsers
gl: implementation was also hard. created test files.
<Greg> I'd find the columns more intuitive if they were specific disabilities rather than the current terms, which I find vague.
js: when Kim and I talked the implementation was to be off the top of head. not so detailed
kp: getting the numbers down and
if there is a cluster of @@ then we can talk about those.
... column heads were to be functional rather than disability specific.
kf: start with Principle 2
js: basically everyone does this.
gl: there are bugs. what about mobile browsers (those designed specifically for touch screen)
kp: ipad configuring swipes and multiple touches.
js: need to get a rough count. easy to do or rough count. not discuss and get detailed.
kp: generally implemented
kf: are there any features that are not keyboard accesible
every browser has some features that are not keyboard accessible.
js: is this something that is easy and should be an A or very hard and be a AAA
keyconfig addon for FF change binding
sh: why looking only at browsers. if a given function can be demonstrated in some other application, then it is possible and should be counted in implementaions.
kf: MS word is a browser, and can do lots of things we are looking for.
generally supported, FF has issues
FF does well (at one time) , IE does not, Jaws does
generally true, check by looking at the UI to see if underscore and shortcut keys
could be rewritten to be 'indicate keyboard shortcuts'
kf: leave it.
gl: this is similar to 214.
... perhaps change to "author supplied user interface controls" to clarify.
214 is author supplied, 219 is UI controls
<scribe> ACTION: JAllan to compare keyboard section with jb keyboard section from 2 years ago [recorded in http://www.w3.org/2012/02/23-ua-minutes.html#action01]
<trackbot> Created ACTION-714 - Compare keyboard section with jb keyboard section from 2 years ago [on Jim Allan - due 2012-03-01].
js: does the IER match?
<Greg> We need to move the Elaine example from 2.1.4 to 2.1.9. Kim will write a sentence for 2.1.4 Intent and/or example of author supplied UI.
<jeanne> ACTION: jeanne to move the Elaine example from 2.1.4 to 2.1.9. [recorded in http://www.w3.org/2012/02/23-ua-minutes.html#action02]
<trackbot> Created ACTION-715 - Move the Elaine example from 2.1.4 to 2.1.9. [on Jeanne F Spellman - due 2012-03-01].
<jeanne> ACTION: Kim will write a sentence for 2.1.4 Intent and/or example of author supplied UI. [recorded in http://www.w3.org/2012/02/23-ua-minutes.html#action03]
<trackbot> Created ACTION-716 - Will write a sentence for 2.1.4 Intent and/or example of author supplied UI. [on Kimberly Patch - due 2012-03-01].
generally done by everyone. exception for mobile. FF does not do object/embed navigation
generally everyone, except mobile devices
no one knows of a UA that does this
<mhakkien> better late than never (i hope)
<KimPatch> Cell R81
<Greg> Chrome with ChromeVox add-on provides sequential navigation to selected types of structural or operable elements (e.g. next/previous h2).
<Greg> Which SC does that fall into? Is that structural navigation or sequential navigation with filtering?
<Greg> (Thanks to Mark for info on ChromeVox.)
discussion about direct navigation and sequential navigation of important elements.
<Greg> Definition of Important Elements: This specification intentionally does not identify which "important elements" must be navigable because this will vary by specification. What constitutes "efficient navigation" may depend on a number of factors as well, including the "shape" of content (e.g. sequential navigation of long lists is not efficient) and desired granularity (e.g. among tables,...
<Greg> ...then among the cells of a given table). Refer to the Implementing document [Implementing UAAG 2.0] for information about identifying and navigating important elements. @@ Editors' Note: Update links
mh: what is an element? html element, and combination of HTML div span, etc with a "role" (aria)
kp: structural and operable elements
<kford> ACTION: KFord Resolve direct and sequential navigation to important elements 2.3.1 and 2.2.1. [recorded in http://www.w3.org/2012/02/23-ua-minutes.html#action04]
<trackbot> Created ACTION-717 - Resolve direct and sequential navigation to important elements 2.3.1 and 2.2.1. [on Kelly Ford - due 2012-03-01].
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/nave/nav/ No ScribeNick specified. Guessing ScribeNick: JAllan Found Scribe: JimAllan Present: Harper_Simon WARNING: Fewer than 3 people found for Present list! Regrets: jan Found Date: 23 Feb 2012 Guessing minutes URL: http://www.w3.org/2012/02/23-ua-minutes.html People with action items: direct jallan jeanne kford kim navigation resolve sequential[End of scribe.perl diagnostic output]