IRC log of ua on 2012-06-05

Timestamps are in UTC.

08:08:55 [Jan]
Jan has joined #ua
08:09:04 [Jan]
Jan has left #ua
14:00:39 [RRSAgent]
RRSAgent has joined #ua
14:00:39 [RRSAgent]
logging to http://www.w3.org/2012/06/05-ua-irc
14:00:41 [trackbot]
RRSAgent, make logs public
14:00:41 [Zakim]
Zakim has joined #ua
14:00:43 [trackbot]
Zakim, this will be WAI_UAWG
14:00:43 [Zakim]
"WAI_UAWG" matches WAI_UAWG(CHAIRS)10:30AM, and WAI_UAWG()9:00AM, trackbot
14:00:44 [trackbot]
Meeting: User Agent Accessibility Guidelines Working Group Teleconference
14:00:44 [trackbot]
Date: 05 June 2012
14:00:57 [AllanJ]
rrsagent, make minutes
14:00:57 [RRSAgent]
I have made the request to generate http://www.w3.org/2012/06/05-ua-minutes.html AllanJ
14:01:39 [AllanJ]
chair: kellyford, jimallan
14:01:51 [AllanJ]
regrets: simon, wayne
14:02:05 [AllanJ]
present: jim, jan, kelly, greg, kim, jeanne
14:04:50 [AllanJ_]
AllanJ_ has joined #ua
14:07:08 [kford]
kford has joined #ua
14:07:54 [kford]
Apologies for the late start Jan.
14:08:36 [kford]
rrsagent, makeminutes
14:08:36 [RRSAgent]
I'm logging. I don't understand 'makeminutes', kford. Try /msg RRSAgent help
14:08:57 [kford]
rrsagent, make minutes
14:08:57 [RRSAgent]
I have made the request to generate http://www.w3.org/2012/06/05-ua-minutes.html kford
14:14:21 [greg]
greg has joined #ua
14:14:40 [jeanne]
jeanne has joined #ua
14:15:02 [greg]
rrsagent, make minutes
14:15:02 [RRSAgent]
I have made the request to generate http://www.w3.org/2012/06/05-ua-minutes.html greg
14:15:40 [AllanJ]
http://www.marcozehe.de/2012/05/08/first-round-of-accessibility-support-for-android-in-mobile-firefox/
14:16:25 [kford_]
kford_ has joined #ua
14:17:11 [Admin]
Admin has joined #ua
14:17:37 [AllanJ]
AllanJ has joined #ua
14:17:37 [greg]
greg has joined #ua
14:18:08 [Jan]
zakim, who's here?
14:18:08 [Zakim]
sorry, Jan, I don't know what conference this is
14:18:09 [Zakim]
On IRC I see greg, AllanJ, Admin, kford, jeanne, Zakim, RRSAgent, Jan, trackbot
14:18:42 [AllanJ]
zakim, this is UAWG Face to Face
14:18:42 [Zakim]
sorry, AllanJ, I do not see a conference named 'UAWG Face to Face' in progress or scheduled at this time
14:18:43 [jeanne]
we are starting now
14:19:20 [AllanJ]
scribe: jallan
14:21:38 [greg_]
greg_ has joined #ua
14:22:23 [kford]
kford has joined #ua
14:22:26 [Admin]
Admin has joined #ua
14:22:27 [AllanJ]
AllanJ has joined #ua
14:22:59 [AllanJ]
topic: GL 2.4 find
14:23:15 [AllanJ]
basic find with text alternatives
14:23:22 [AllanJ]
find direction
14:23:36 [AllanJ]
case sensitivity (AA)
14:23:40 [AllanJ]
may 31
14:24:48 [Jan]
ATAG wording: http://www.w3.org/TR/2012/WD-ATAG20-20120410/#sc_a351
14:25:05 [Jan]
A.3.5.1 Text Search:
14:25:07 [Jan]
If the authoring tool provides an editing-view of text-based content, then the editing-view enables text search, such that all of the following are true: (Level AA)
14:25:08 [Jan]
(a) All Editable Text: Any text content that is editable by the editing-view is searchable (including alternative content); and
14:25:10 [Jan]
(b) Match: Matching results can be made visible to authors and given focus; and
14:25:11 [Jan]
(c) No Match: Authors are informed when no results are found; and
14:25:13 [Jan]
(d) Two-way: The search can be made forwards or backwards.
14:25:51 [AllanJ]
gl: basic search should be A
14:26:08 [AllanJ]
... split in to two SC A and AA
14:26:41 [AllanJ]
... A basic, bidirectional, highlight found item, alert on wrap
14:27:25 [AllanJ]
... AA etc
14:29:03 [AllanJ]
jr: what is the a11y case for case sensitive search
14:29:23 [AllanJ]
gl: efficiency. see the example in IER
14:30:01 [AllanJ]
Topic: 2.5.3 provide structural navigation
14:30:56 [AllanJ]
kf: there are action items associated with this
14:31:51 [jeanne]
2.5.6 Navigate by structural element: The user agent provides at least the following types of structural navigation, where the structure types exist:(Level AA) (a) by header (b)within tables
14:32:52 [AllanJ]
gl: the example in 2.5.3 is good. it is structural navigation of the database.
14:33:48 [AllanJ]
kf: does someone understand this enough (2.5.3, 2.5.5.2.5.6 2.5.7) to try to write them
14:34:11 [AllanJ]
gl: this section needs work.
14:35:02 [AllanJ]
kp: 2.5.6 and 2.5.7 seem to cover what is needed. the other 2 are confusing
14:35:42 [AllanJ]
kp: what is the overlap. 2.5.3 and 2.5.5 seem prescriptive.
14:36:15 [AllanJ]
gl: 2.5.3 could be rewritten to better reflect the example.
14:38:12 [AllanJ]
gl: 2.5.5 is two things. I am on an item jump me to the containing heading. the other part is the breadcrumbs of the structure.
14:38:39 [AllanJ]
... not sure why they are combined. not clear from the wording if this information is presented to the user directly.
14:38:46 [AllanJ]
kp: is there an overlap
14:41:05 [AllanJ]
gl: 2.5.5 is all about the info on a page.
14:42:06 [AllanJ]
2.5.3 is all about a database structure. something like a play list and different ways of structuring information.
14:43:29 [AllanJ]
gl: I put my focus on something that is too small, I want to make it bigger. first I have to know what this element is. I open firebug to drill down
14:43:39 [AllanJ]
jr: that's the first part.
14:44:10 [AllanJ]
.... labels could be further away in the hierarchy but still associated.
14:44:30 [AllanJ]
js: how is this different from 1.10.1
14:44:48 [AllanJ]
gl: let's delete first part of 2.5.5 and keep 1.10.1
14:45:04 [AllanJ]
gl: 2.5.6 is navigation.
14:45:54 [AllanJ]
+1 all kill first half of 2.5.5 user can access explicitly defined relationships
14:46:27 [AllanJ]
jr: fold content hierarchy in 2.5.5 into 2.5.3
14:46:40 [AllanJ]
gl: no it belongs in principle 1
14:48:00 [AllanJ]
kf: greg and jr to thrash out 2.5.3 and 2.5.5 and principle location
14:48:47 [AllanJ]
topic: GL 2.6 event handlers
14:49:00 [AllanJ]
kf: don't know of any UA that does this.
14:49:09 [AllanJ]
js: it should not be A.
14:49:59 [AllanJ]
kf: the intent is good. need to reword the SC - jeanne
14:53:55 [AllanJ]
ja: rewrite 2.8.1 to include show/hide
14:57:48 [AllanJ]
close action-504
14:57:48 [trackbot]
ACTION-504 Rewrite Background Image Toggle (2.11.1) ier for next week closed
15:00:30 [kford]
Action-716 Believe existing 219 covers this.
15:01:35 [kford]
Close Action-716
15:01:35 [trackbot]
ACTION-716 Will write a sentence for 2.1.4 Intent and/or example of author supplied UI. closed
15:07:24 [kford]
kford has joined #ua
15:07:25 [Admin]
Admin has joined #ua
15:07:37 [greg]
greg has joined #ua
15:07:48 [AllanJ]
AllanJ has joined #ua
15:26:59 [Admin]
2.6.1 Access to input methods:
15:27:01 [Admin]
The user can discover input methods explicitly associated with the keyboard focus element, and be able to activate the element using a modality independent method. (Level A)
15:30:36 [Admin]
2.6.1 Access to input methods:
15:30:38 [Admin]
The user can discover input methods explicitly associated with an element, and be able to activate the element using a modality independent method. (Level AA)
15:33:01 [kford]
2.4.5 Find non-rendered alternatives:
15:33:02 [kford]
Find functionality intended to satisfy UAAG guideline 2.4 offers the ability to search on the following alternatives when they are not visibly rendered but default content for the alternatives offers a visible location to highlight the found result.
15:33:04 [kford]
A. Alternative text
15:33:05 [kford]
Examples:
15:33:07 [kford]
Ronda typically browses the web with images turned off so she sees the alternative text for images rendered in place of images. She visits a favorite web site on a friend's computerand knows she wants to find a link to her favorite rock star's photo gallery. On her computer this is the artist's name so she searches for that word on her friend's computer. The alt text is not dispalyed in...
15:33:08 [kford]
...this case but the star's image is highlighted because her find command has associated the alt text with the image.
15:33:10 [kford]
2.4.6 CaseSensitive Find
15:33:11 [kford]
Find functionality intended to satisfy guideline 2.4 offers a case sensitive option for performing searches (level AA)
15:33:14 [kford]
Intent of Success Criterion 2.4.6 : Searching is much more useful when the user can specify whether case matters in some circumstances. Further this can reduce the number of keystrokes needed to perform a search.
15:33:17 [kford]
15:33:19 [kford]
Examples of Success Criterion 2.4.6:
15:33:21 [kford]
Dennis uses a screen reader. He wants to find all the instances of his friend Bill in a blog post about finances. He needs to specify case in order
15:33:24 [kford]
to avoid stopping at instances of "bill". Later, he searches for his friend's name in a blog post about poetry where the author never uses capital letters.
15:33:27 [kford]
In this instance he specifies that case does not matter.
15:37:14 [kford]
Find functionality intended to satisfy UAAG guideline 2.4 offers the ability to search on the following alternatives when they are present for rendered content.
15:39:03 [AllanJ]
Find functionality offers the ability to search on alternative content when they are not visibly rendered.
15:51:49 [kford]
2.4.5 Find non-rendered alternatives:
15:51:51 [kford]
Find functionality offers the ability to search on alternative content when it is not visibly rendered.
15:51:54 [kford]
A. Alternative text
15:51:56 [kford]
B. Captions
15:51:58 [kford]
Intent:
15:51:59 [kford]
Authors frequently provide alternative content to meet web content accessibility guidelines. The purpose of this success criteria is to ensure that find functionality allows users to locate this content even if it may not be visible rendered.
15:52:01 [kford]
Examples:
15:52:02 [kford]
Ronda typically browses the web with images turned off so she sees the alternative text for images rendered in place of images. She visits a favorite web site on a friend's computer and knows she wants to find a link to her favorite rock star's photo gallery. On her computer this is the artist's name so she searches for that word on her friend's computer. The alt text is not displayed in...
15:52:04 [kford]
...this case but the star's image is highlighted because her find command has associated the alt text with the image.
15:52:05 [kford]
2.4.6 CaseSensitive Find
15:52:07 [kford]
Find functionality intended to meet guideline 2.4 offers the ability to perform case sensitive searches. (level AA)
15:52:09 [kford]
Intent of Success Criterion 2.4.6 : Searching is much more useful when the user can specify whether case matters in some circumstances. Further this can reduce the number of keystrokes needed to perform a search.
15:52:12 [kford]
15:52:14 [kford]
Examples of Success Criterion 2.4.6:
15:52:17 [kford]
Dennis uses a screen reader. He wants to find all the instances of his friend Bill in a blog post about finances. He needs to specify case in order
15:52:19 [kford]
to avoid stopping at instances of "bill". Later, he searches for his friend's name in a blog post about poetry where the author never uses capital letters.
15:52:22 [kford]
In this instance he specifies that case does not matter.
16:07:39 [jeanne]
jeanne has joined #ua
16:07:51 [Admin]
Admin has joined #ua
16:09:20 [AllanJ]
topic: 2.6.1 access to event handlers
16:09:53 [jeanne]
2.6.1 Access to input methods: The user can discover input methods explicitly associated with an element, and be able to activate the element using a modality independent method. (Level AA)
16:09:53 [AllanJ]
access to input methods
16:10:29 [AllanJ]
js: made this broader and more flexible
16:11:04 [jeanne]
Users interacting with a web browser may be doing so by using one or more input technologies including keyboard, mouse, speech, touch, and gesture. No matter how the user is controlling the user agent, the user needs to know the input methods available to a particular piece of content, and activate that element using an modality independent method. In addition, any one input method should not hold back another. For instance, people who don't use a mouse shouldn't
16:11:30 [AllanJ]
changed level to AA from A
16:12:25 [AllanJ]
kf: why lower priority
16:12:42 [AllanJ]
js: really hard to do. this is what the IndieUI group is about.
16:13:16 [AllanJ]
jr: how much does the user need to know about the method of input., to they really need to know or just get it done.
16:13:22 [jeanne]
adding to the intent (irc client truncation) For instance, people who don't use a mouse shouldn't have to map their input methods to the same steps a mouse user would take.
16:13:46 [AllanJ]
kp: they need to know. discovery of method makes it easier for the user to decide what to do.
16:14:03 [AllanJ]
gl: this doesn't seem right.
16:14:24 [AllanJ]
... sc the first and second clause are doing different things
16:14:40 [AllanJ]
first is discovery (non default actions0
16:15:38 [AllanJ]
second doesn't say that you activate the element which means the default action....not do any secondary actions
16:15:56 [AllanJ]
gl: what is input method vs event handler
16:16:58 [AllanJ]
js: author will associate event handler with an element. user needs to discover input methods associated with the handler, then activate in device independent manner
16:17:31 [AllanJ]
gl: first example in the gl, is it handled by the new sc.
16:18:50 [AllanJ]
ja: want user to have the name of the function that the right click handler will do.
16:19:13 [AllanJ]
gl: need to have recognized input methods
16:20:02 [AllanJ]
... input method means some element has 2-finger swipe handler, or right click or double click
16:20:10 [AllanJ]
jr: why?
16:21:26 [AllanJ]
gl: go to element, get context menu...one menu item would have menu list of recognized input actions available.
16:21:49 [Zakim]
Zakim has left #ua
16:22:10 [AllanJ]
jr: if you are going to go somewhere and discover, the user must already know that ...
16:22:25 [AllanJ]
zakim, please join
16:22:33 [Zakim]
Zakim has joined #ua
16:22:55 [jeanne]
rrsagent, make minutes
16:22:55 [RRSAgent]
I have made the request to generate http://www.w3.org/2012/06/05-ua-minutes.html jeanne
16:23:59 [AllanJ]
gl: assume using 1.3.1 user will know which items take input
16:24:29 [AllanJ]
then can choose to hover over an element using a menu
16:24:41 [AllanJ]
kp: showing the doors is 1.3.1
16:24:57 [AllanJ]
gl: what you can do with the door is 2.6.1
16:26:04 [AllanJ]
jr: so they get a menu with mouse over, mouse off, etc. the user might do something that the developer didn[t anticipate that a mouse user could not do.
16:26:45 [AllanJ]
gl: UA should constrain behaviours, that cannot do a mouse up, if a mouse down has not been executed
16:27:26 [AllanJ]
jr: want to build in these contraints, want to keep the user from doing the wrong thing.
16:28:18 [AllanJ]
kp: issues with this. dragon does not allow using spelling when menus are open. when spell would let you jump to a menu item. really frustrating
16:28:34 [AllanJ]
kf: have a new SC
16:29:14 [AllanJ]
js: don't want to set up something that will conflict with IndieUI develops 2 years
16:29:17 [jeanne]
Jeremy cannot use a mouse. He needs to activate a flyout menu that normally appears OnMouseOver. Jeremy can navigate to a link on this flyout menu, pull up a context menu listing the available input methods (e.g. click, double-click, swipe left) and activate it using his keyboard.
16:30:14 [AllanJ]
gl: close. but how did he simulate the mouse over from the menu.
16:30:26 [AllanJ]
editing live in the docv
16:31:51 [greg]
He needs to activate a flyout menu that appears when one hovers the mouse over a button. He navigates to the button and pulls up its context menu, which includes an "Inputs" submenu that lists the available input methods (e.g. click, double-click, swipe left, and hover) and from that he chooses the "Hover" command.
16:33:27 [AllanJ]
gl: note in the intent. UA may want to constrain the available inputs methods based on what is available (e.g. now allowing a mouse up unless a mouse down has been activated)
16:34:36 [AllanJ]
gl: programmers make assumptions that they would never expect a keyup without a keydown
16:34:37 [jeanne]
The user agent can constrain steps such that not allowing a mousedown before a mouseup.
16:35:08 [AllanJ]
kp: still concerns. but ok with it.
16:35:23 [AllanJ]
gl: can be tested with automated testers.
16:35:42 [AllanJ]
kp: ok with JS restatement
16:36:11 [AllanJ]
kf: LOTS of event handlers. this is tough.
16:37:46 [AllanJ]
gl: instead of listing available event handlers, only the handlers that are relevant to the element
16:38:37 [AllanJ]
kf: implement, tab to an element, get a list of relevant handlers and trigger them in sequence only
16:39:36 [AllanJ]
jr: clarify. would you show on mouseDown on every element, or only on registered events available
16:40:23 [AllanJ]
gl: in javascript can you create a generic action watcher without registering the method with the UA
16:41:46 [Admin]
Admin has joined #ua
16:41:50 [greg]
He needs to activate a flyout menu that appears when one hovers the mouse over a button. He navigates to the button and pulls up its context menu, which includes an "Inputs" submenu that lists the available input methods (e.g. events that were registered for this element: click, double-click, swipe left, and hover) and from that he chooses the "Hover" command.
16:42:29 [AllanJ]
resolved: added the above example to 2.6.1
16:46:26 [greg]
Users interacting with a web browser may be doing so by using one or more input technologies including keyboard, mouse, speech, touch, and gesture. Sometimes a web page is scripted so that it assumes and requires an input method that's not available to the user, such as a handling drag events when the user relies solely on the keyboard. In those cases, the user needs to determine which input...
16:46:28 [greg]
...methods available to a particular piece of content, and activate that element using an modality independent method. In addition, any one input method should not hold back another. For instance, people who don't use a mouse shouldn't
16:49:13 [jeanne]
Revised Intent: Users interacting with a web browser may be doing so by using one or more input technologies including keyboard, mouse, speech, touch, and gesture. Sometimes a web page is scripted so that it assumes and requires an input method that is not available to the user, such as handling drag events for a user relying solely on the keyboard. In those cases, the user needs to determine what methods are available and activate that element with a modality in
16:49:38 [jeanne]
In addition, any one input method should not hold back another. For instance, people who don't use a mouse shouldn't have to map their input methods to the same steps a mouse user would take. The user agent can constrain steps such as not allowing a mouseup before a mousedown.
16:55:38 [greg_]
greg_ has joined #ua
16:55:48 [AllanJ]
AllanJ has joined #ua
16:56:29 [kford]
kford has joined #ua
17:09:02 [AllanJ]
resuming meeting
17:09:02 [Admin]
Admin has joined #ua
17:09:19 [AllanJ]
rrsagent, make minutes
17:09:19 [RRSAgent]
I have made the request to generate http://www.w3.org/2012/06/05-ua-minutes.html AllanJ
17:10:16 [jeanne]
2.6.1 Access to input methods: The user can discover recognized input methods explicitly associated with an element, and be able to activate those methods using a modality independent method.
17:10:30 [jeanne]
2.6.1 Access to input methods: The user can discover recognized input methods explicitly associated with an element, and be able to activate those methods using a modality independent manner.
17:11:20 [jeanne]
2.6.1 Access to input methods: The user can discover recognized input methods explicitly associated with an element, and activate those methods in a modality independent manner. (Level AA)
17:12:06 [kford]
2.4.5 Find non-rendered alternatives:
17:12:08 [kford]
Find functionality offers the ability to search on alternative content when it is not visibly rendered.
17:12:09 [kford]
A. Alternative text
17:12:14 [kford]
B. Captions
17:12:15 [AllanJ]
resolved: the above it inserted into the document
17:12:19 [kford]
Intent:
17:12:21 [kford]
Authors frequently provide alternative content to meet web content accessibility guidelines. The purpose of this success criteria is to ensure that find functionality allows users to locate this content even if it may not be visible rendered.
17:12:23 [kford]
Examples:
17:12:24 [kford]
Ronda typically browses the web with images turned off so she sees the alternative text for images rendered in place of images. She visits a favorite web site on a friend's computer and knows she wants to find a link to her favorite rock star's photo gallery. On her computer this is the artist's name so she searches for that word on her friend's computer. The alt text is not displayed in...
17:12:26 [kford]
...this case but the star's image is highlighted because her find command has associated the alt text with the image.
17:12:28 [kford]
2.4.6 CaseSensitive Find
17:12:30 [kford]
Find functionality intended to meet guideline 2.4 offers the ability to perform case sensitive searches. (level AA)
17:12:31 [kford]
Intent of Success Criterion 2.4.6 : Searching is much more useful when the user can specify whether case matters in some circumstances. Further this can reduce the number of keystrokes needed to perform a search.
17:12:34 [kford]
17:12:36 [kford]
Examples of Success Criterion 2.4.6:
17:12:38 [kford]
Dennis uses a screen reader. He wants to find all the instances of his friend Bill in a blog post about finances. He needs to specify case in order
17:12:41 [kford]
to avoid stopping at instances of "bill". Later, he searches for his friend's name in a blog post about poetry where the author never uses capital letters.
17:12:44 [kford]
In this instance he specifies that case does not matter.
17:13:03 [jeanne]
the previous resolved is for 2.6.1, not 2.4.5
17:13:16 [AllanJ]
topic: 2..4.5 find in non-visible content
17:13:53 [AllanJ]
kf: split 2.4.5 into 2 new sc. 2.4.5 and 2.4.6
17:14:18 [AllanJ]
gl: in the sc say EVEN when something is not rendered
17:15:30 [AllanJ]
2.4.5 Find non-rendered alternatives: Find functionality offers the ability to search on alternative content even when it is not visibly rendered.
17:16:55 [AllanJ]
gl: what about the A and B (alt, captions)
17:17:35 [AllanJ]
can search on captions if they are reveals.
17:18:26 [AllanJ]
kf: to I have to download the whole move to search for captions.
17:18:43 [AllanJ]
discussion of methods of captioning and searching
17:19:16 [AllanJ]
kf: do we need a generic SC with examples, or include a list in the SC.
17:19:45 [AllanJ]
jr: if something is not available to the UA (captions) they it can't do anything with it.
17:20:32 [AllanJ]
js: restricting to 'alt' and available captions should be list
17:20:59 [AllanJ]
js: restricting to alternative text with covers
17:21:16 [AllanJ]
...alt now and whatever in the future
17:24:17 [kford]
The user can search for alternative content even when it is not visibly rendered.
17:25:00 [AllanJ]
The user can search alternative content even when it is not visibly rendered.
17:26:08 [AllanJ]
The user can search alternative text and captions even when it is not visibly rendered.
17:27:25 [AllanJ]
The user can search alternative content even when they are not visibly rendered.
17:27:58 [kford]
The user can search alternative content even when it is not visibly rendered.
17:29:31 [AllanJ]
gl: we lost the bit about "that is available to the user agent"
17:29:41 [Jan]
alternative content: Content that can be used in place of default content that may not be universally accessible. Alternative content fulfills the same purpose as the original content. Examples include text alternatives for non-text content, captions for audio, audio descriptions for video, sign language for audio, media alternatives for time-based media. See WCAG for more information.
17:30:10 [AllanJ]
The user can search alternative content even when it is not visibly rendered that is available to the user agent.
17:30:53 [AllanJ]
The user can search alternative content that is available to the user agent even when it is not visibly rendered.
17:33:23 [AllanJ]
resolved: 2.4.5 The user can search alternative content (including captions) that is available to the user agent even when it is not visibly rendered.
17:33:43 [kford]
Authors frequently provide alternative content to meet web content accessibility guidelines. The purpose of this success criteria is to ensure that find functionality allows users to locate this content even if it may not be visible rendered.
17:33:49 [kford]
Examples:
17:33:50 [kford]
Ronda typically browses the web with images turned off so she sees the alternative text for images rendered in place of images. She visits a favorite web site on a friend's computer and knows she wants to find a link to her favorite rock star's photo gallery. On her computer this is the artist's name so she searches for that word on her friend's computer. The alt text is not displayed in...
17:33:52 [kford]
...this case but the star's image is highlighted because her find command has associated the alt text with the image.
17:35:06 [AllanJ]
gl: doesn't say why this is important to pwd
17:35:32 [AllanJ]
kf: yes it does.
17:35:37 [greg]
It only restates the SC.
17:35:55 [AllanJ]
js: it is helpful for users with disabilities to search on this content that is not visible
17:36:41 [AllanJ]
kp: +1 example
17:36:52 [AllanJ]
ja: +1 example
17:36:58 [Jan]
jr +1
17:37:09 [AllanJ]
resolved: 2.4.5 is done above
17:37:26 [kford]
2.4.6 CaseSensitive Find
17:37:31 [kford]
Find functionality intended to meet guideline 2.4 offers the ability to perform case sensitive searches. (level AA)
17:37:33 [kford]
Intent of Success Criterion 2.4.6 : Searching is much more useful when the user can specify whether case matters in some circumstances. Further this can reduce the number of keystrokes needed to perform a search.
17:37:34 [kford]
17:37:36 [kford]
Examples of Success Criterion 2.4.6:
17:37:37 [kford]
Dennis uses a screen reader. He wants to find all the instances of his friend Bill in a blog post about finances. He needs to specify case in order
17:37:39 [kford]
to avoid stopping at instances of "bill". Later, he searches for his friend's name in a blog post about poetry where the author never uses capital letters.
17:37:40 [kford]
In this instance he specifies that case does not matter.
17:38:57 [AllanJ]
gl: we have not used this phrasing in the SC before
17:39:23 [AllanJ]
jr: more useful than case sensitivity is whole word.
17:39:57 [AllanJ]
.... should be one generic SC to include all these bits about searching
17:40:47 [AllanJ]
... accessibility case is efficiency
17:40:57 [AllanJ]
kf: then we need to revise one more time.
17:42:24 [AllanJ]
topic: 2.5.5
17:42:30 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0101.html
17:44:16 [AllanJ]
EXISTING: 2.5.5 Access to Relationships which Aid Navigation: The user can access explicitly-defined relationships based on the user's position in content, and the path of nodes leading from the root of any content hierarchy to that position. (Level AA)
17:44:18 [AllanJ]
PROPOSAL:
17:44:19 [AllanJ]
-some of the SC is covered, by 1.10.1. The rest will be covered by a new SC:
17:44:21 [AllanJ]
1.10.2 Access to Element Hierarchy: The user can determine the path of element nodes from the root element of the element hierarchy to the currently focused or selected element. (Level AA)
17:44:22 [AllanJ]
Intent:
17:44:24 [AllanJ]
Users who have difficulty working with a web page or document can use user style sheets or scripts to modify its presentation or interaction to better meet their needs. This often requires them to identify specific elements, their attributes, and their position in the element hierarchy. The user agent can facilitate this process by allowing the user to navigate to an element, or select it if...
17:44:25 [AllanJ]
...it is not navigable, and querying the information they need. If this features is not provided, the user may not be able to find the corresponding element in the source view or entire document tree.
17:44:28 [AllanJ]
Examples:
17:44:30 [AllanJ]
Jack wants certain content on a web page to be displayed in a larger font, and wants to create a user style sheet that would modify its appearance. He needs to identify the class or ID of the particular element, so he puts the focus onto or selects the text he's interested in, opens the browser's debug window, which shows him that the selected text is an element with class "story" inside a...
17:44:35 [AllanJ]
...paragraph inside a DIV with class "Premiere". He then knows the combination of classes and element types to specify in the user style sheet.
17:50:10 [AllanJ]
discussion of 2.5.3 with itunes example of playlist with songs, artist, album genre, etc with implied relationships
17:52:04 [AllanJ]
kp, ja, kf: +1
17:52:44 [AllanJ]
gl: simon should have a say, since he wrote the original
17:56:57 [AllanJ]
resolved: delete 2.5.5 and add new 1.10.2 as written above
18:01:40 [AllanJ]
greg will write clear description then we will share with simon and discuss
18:05:29 [AllanJ]
gl: 1.10.2 still needs a bit of work
18:07:03 [AllanJ]
topic 2.4.3 match found
18:07:12 [greg]
The remaining issue with 1.10.2 is that a UA could comply with the letter but be entirely useless to the user, by providing a list of elements without their class, ID, or style attributes. Providing those is implied by the Intent and Example, but not required by the SC.
18:07:45 [AllanJ]
Intent for 2.4.3
18:07:48 [AllanJ]
It is important for the user to easily recognize that a search term has been found and that the term is revealed to the user in context. The user agent moves the viewport to include the found term and the term is highlighted in some fashion. It is assumed that the point of regard is the found element in the viewport, any subsequent searches on the same term or other navigation tasks(e.g....
18:07:49 [AllanJ]
...tabbing to the next anchor) begin from this point. New searches would begin from the top of the document.
18:08:34 [AllanJ]
@@ Editors' Note: If the caret has been moved, from its new location.@@
18:08:35 [AllanJ]
remove editor's note, if caret is moved by the user then the point of regard is moved and same search begins from the current point of regard.
18:11:09 [AllanJ]
It is important for the user to easily recognize that a search term has been found and that the term is revealed to the user in context. The user agent moves the viewport to include the found term and the term is highlighted in some fashion. The point of regard is the found element in the viewport. Any subsequent searches on the same term or other navigation tasks (e.g. tabbing to the next...
18:11:10 [AllanJ]
...anchor) begin from this point.
18:14:01 [AllanJ]
resolved: intent for 2.4.3 put into document and editors note deleted
18:17:35 [AllanJ]
close action-671
18:17:35 [trackbot]
ACTION-671 Create a test page for seachring "hidden" content and send to the list closed
18:18:08 [AllanJ]
close action-669
18:18:08 [trackbot]
ACTION-669 Write definition of 'hidden content' - outside viewport, heighth width 0, same color as background closed
18:18:50 [AllanJ]
resolved: remove definition of Hidden Content in 2.4.5 as it is covered in a different SC
18:20:12 [AllanJ]
topic: Principle 3
18:20:35 [AllanJ]
discussion of Editors note before 3.1..2
18:20:50 [AllanJ]
s/3.1..2/3.1.2
18:22:35 [AllanJ]
this should be UAAG next, it is a general interface thing, hard to justify as an accessibility item.
18:24:31 [AllanJ]
issue: sc to be created to remove future warning messages in May 31 draft (editors note in 3.1) to be moved to UAAG.next
18:24:31 [trackbot]
Created ISSUE-94 - Sc to be created to remove future warning messages in May 31 draft (editors note in 3.1) to be moved to UAAG.next ; please complete additional details at http://www.w3.org/WAI/UA/tracker/issues/94/edit .
18:24:57 [AllanJ]
close action-459
18:24:57 [trackbot]
ACTION-459 Add google instant information to the IER for 2.1.2 closed
18:27:30 [AllanJ]
topic: discussion of Action-611, need for new SC addressing spell checking
18:30:28 [Zakim]
Zakim has left #ua
18:30:33 [AllanJ]
resolved: remove editors note from summary of 3.2
18:32:20 [Jan]
http://www.w3.org/TR/2012/WD-ATAG20-20120410/#sc_a421
18:33:07 [AllanJ]
resolved: editors note in 3.2.2, remove second paragraph of intent.
18:34:46 [AllanJ]
kp and ja like the wording of ATAG, change 3.2.2 to match
18:36:02 [AllanJ]
s/3.2.2/3.3.2
18:37:21 [AllanJ]
gl: worried about b: describe in the interface....may be time with the developers say it is described because it is obvious.
18:38:25 [greg]
e.g. hover over a mysterious check box and the tooltip just repeats the same cryptic label text.
18:40:48 [AllanJ]
topic: discussion of removing editors note in 3.3.4 about UA extensions and centralized view of the UA
18:41:19 [AllanJ]
js: its not possible to embed extension help within the UA
18:42:16 [AllanJ]
kp: in the UA in the help if there are extensions then there is a button that links to where you might find help about the extension
18:42:55 [AllanJ]
gl: extensions are separate products, and centralized view of a11y features are in separate area
18:43:10 [AllanJ]
gl: modify intent
18:43:17 [jeanne]
This is on a per-product basis, nested user agents would have separate centralized documentation.
18:44:09 [jeanne]
This is on a per-product basis. Nested user agents or addons may provide separate centralized documentation.
18:44:25 [AllanJ]
resolved: modify the intent of 3.3.4 with above Jeanne statement
18:53:39 [AllanJ]
topic: principle 4
18:54:00 [Jan]
http://www.w3.org/TR/2012/WD-ATAG20-20120410/#sc_a122
18:54:17 [AllanJ]
discussion of 4.1.2 and 4.1.6
18:54:57 [AllanJ]
there is action-651 to combine them
18:55:38 [AllanJ]
ATAG does not specify any of the a11y properties
18:55:45 [Jan]
A.2.2.2 Access to Rendered Text Properties: If an editing-view renders any text formatting properties that authors can also edit using the editing-view, then the properties can be programmatically determined.
19:01:29 [AllanJ]
4.2.1 the user can move the keyboard focus to a nested user agent
19:01:45 [AllanJ]
level A
19:02:12 [AllanJ]
gl: this should be covered by the keyboard SC
19:02:36 [AllanJ]
This is important for testing.
19:03:28 [AllanJ]
gl: combine with 4.2.2 to keep the concept or add as an example for the keyboard SC
19:05:04 [AllanJ]
gl: what is difference between 4.2.2 and 4.2.3 one is user and one is user agent
19:05:33 [AllanJ]
js: 2.1.5 covers 4.2.1 and 4.2.2
19:05:53 [AllanJ]
ja: so they are redundant
19:06:50 [AllanJ]
gl: but if I get into something without the keyboard it does not say I have to get out of the item with the keyboard.
19:07:34 [AllanJ]
kp: mixing and matching is important
19:08:43 [AllanJ]
kp: combine intents and examples between all.
19:08:54 [AllanJ]
jr: they really overlap alot.
19:09:13 [AllanJ]
kp: aria example in 4.2.2 is good an should be kept.
19:10:52 [AllanJ]
gl: can remove all of 4.2 and subsume all uner 2.1.5
19:11:54 [AllanJ]
jr: do we need a note about nested user agents in 2.1.5
19:14:21 [AllanJ]
resolved: delete all 4.2 and reword 2.1.5 and move relevant examples
19:15:06 [AllanJ]
close action-610 all incorporated into 2.1.5
19:18:38 [jeanne]
2.1.5 No Keyboard Trap (former 2.1.3): If keyboard focus can be moved to a component using a keyboard interface (including nested user agents), then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, users are advised of the method for moving focus away. (Level A)
19:19:59 [AllanJ]
need to write examples for 2.1.5
19:23:37 [greg]
greg has joined #ua
19:23:48 [AllanJ]
AllanJ has joined #ua
19:24:01 [Admin]
Admin has joined #ua
19:24:24 [kford]
kford has joined #ua
19:30:09 [Jan]
This might be a nice replacement for 5.3.2 (http://www.w3.org/TR/2012/WD-ATAG20-20120410/#sc_a121)
19:41:25 [AllanJ]
rrsagent, make minutes
19:41:25 [RRSAgent]
I have made the request to generate http://www.w3.org/2012/06/05-ua-minutes.html AllanJ
20:06:09 [AllanJ]
topic: 2.1.5 keyboard trap examples
20:06:14 [Admin]
- Ari has repetitive strain injuries that are exacerbated when he uses the mouse. He is using a video hosting site where each page hosts a
20:06:16 [Admin]
nested media player. He presses Tab until the focus in on the media player, then presses Enter to activate and put the keyboard focus
20:06:17 [Admin]
on it. When he's finished watching the video, he presses Tab to navigate to the comments below the video, but cannot get the focus to
20:06:19 [Admin]
leave the video player. He presses Alt+Left to return to the previous page, but that also fails because the video player is consuming
20:06:20 [Admin]
those keystrokes. Luckily, Ari knows that Shift+Esc will return focus from a nested user agent, with or without its cooperation. Thus,
20:06:22 [Admin]
even a badly behaved nested user agent cannot prevent Ari from getting on with his work.
20:06:23 [Admin]
- Jay has repetitive strain injuries that are exacerbated when he uses the mouse. He moves the focus to a toolbar extension that does not
20:06:25 [Admin]
relinquish control back to the user agent. Jay presses Alt-D to move the focus to the address bar.
20:06:26 [Admin]
- Mary is a blind user who does not use the mouse. She moves the focus to an embedded scripted application that was poorly
20:06:29 [Admin]
programmed. She presses a documented key combination -- Alt+N -- to override the scripting and move the focus to the next element
20:06:32 [Admin]
in the content.
20:06:34 [Admin]
- Katan does not use the mouse and has trouble with short-term memory. He is using a virtual machine. The escape sequence is Shift+Ctrl+Escape. Every time Katan opens the program, it briefly shows the escape sequence near the top right corner of the screen. The VM also has an Exit option in its menu system. The Escape keystrokes are also indicated on the menu.
20:08:03 [Admin]
- Ari has repetitive strain injuries that are exacerbated when he uses the mouse. He is using a video hosting site where each page hosts a nested media player. He presses Tab until the focus in on the media player, then presses Enter to activate and put the keyboard focus on it. When he's finished watching the video, he presses Tab to navigate to the comments below the video, but cannot get...
20:08:05 [Admin]
...the focus to leave the video player. He presses Alt+Left to return to the previous page, but that also fails because the video player is consuming those keystrokes. Luckily, Ari knows that Shift+Esc will return focus from a nested user agent, with or without its cooperation. Thus, even a badly behaved nested user agent cannot prevent Ari from getting on with his work.
20:08:06 [Admin]
- Jay has repetitive strain injuries that are exacerbated when he uses the mouse. He moves the focus to a toolbar extension that does not relinquish control back to the user agent. Jay presses Alt-D to move the focus to the address bar.
20:08:08 [Admin]
- Mary is a blind user who does not use the mouse. She moves the focus to an embedded scripted application that was poorly programmed. She presses a documented key combination -- Alt+N -- to override the scripting and move the focus to the next element in the content.
20:08:11 [Admin]
- Katan does not use the mouse and has trouble with short-term memory. He is using a virtual machine. The escape sequence is Shift+Ctrl+Escape. Every time Katan opens the program, it briefly shows the escape sequence near the top right corner of the screen. The VM also has an Exit option in its menu system. The Escape keystrokes are also indicated on the menu.
20:11:19 [AllanJ]
gl: on Ari, how do I get the focus to leave the video player. its not clear about what you are trying to achieve.
20:11:53 [AllanJ]
... what is the expected behavior that the UA is repairing
20:13:16 [AllanJ]
resolved: add the above examples into 2.1.5
20:14:45 [AllanJ]
topic: 2.8.1 tool bars
20:15:12 [greg]
Existing:
20:15:14 [greg]
2.8.1 Configure Position: The user can add, remove, and reorder any toolbars and similar containers, and the items within them. (Level AA)
20:15:15 [greg]
2.8.2 Restore Default Toolbars: The user can restore the default toolbar, panel, or inspector configuration. (Level AAA)
20:15:17 [greg]
Proposed:
20:15:18 [greg]
2.8.1 Configure Toolbars: The user can add, remove, reorder, show, and hide any toolbars and similar containers, and the items within them. (Level AA)
20:15:20 [greg]
2.8.2 Reset Toolbar Configuration: The user can restore all toolbars and similar containers to their default configuration. (Level AAA)
20:15:21 [greg]
Glossary entry for Toolbars and similar containers:
20:15:23 [greg]
A collection of commonly used controls presented in a region that can be configured or navigated separately from other regions. Such containers may be docked or free-floating, permanent or transient, integral to the application or add-ons. Variations are often called toolbars, palettes, panels, or inspectors.
20:16:59 [AllanJ]
gl: did not review the IER of 2.8.1 and 2.8.2
20:17:46 [AllanJ]
jr: +1 to sc
20:18:07 [AllanJ]
+1
20:18:38 [AllanJ]
close action-514
20:18:38 [trackbot]
ACTION-514 Write glossary definion for toolbar closed
20:18:57 [AllanJ]
jr: what would not be a toolbar in a UA
20:19:43 [AllanJ]
gl: status bar, history sidebar, etc, could expand list
20:20:04 [AllanJ]
gl: if a standard windows app you can't move the menu bar.
20:20:09 [greg]
A collection of commonly used controls presented in a region that can be configured or navigated separately from other regions. Such containers may be docked or free-floating, permanent or transient, integral to the application or add-ons. Variations are often called toolbars, palettes, panels, inspectors, sidebars, or status bars.
20:21:03 [greg]
As Jan points out, menu bars would fit in the definition; Greg points out that in standard Windows-based applications one cannot move the menu bar.
20:21:18 [greg]
But it's AA so OK.
20:22:02 [greg]
A collection of commonly used controls presented in a region that can be configured or navigated separately from other regions. Such containers may be docked or free-floating, permanent or transient, integral to the application or add-ons. Variations are often called toolbars, palettes, panels, inspectors, sidebars, status bars, and menus.
20:23:04 [AllanJ]
resolved: add 2.8.1 and 2.8.2 and glossary add editors
20:23:43 [kford]
3.2.x Provide spell checking functionality
20:23:47 [kford]
User agents provide spell checking functionality for text created inside the user agent (level AA).
20:23:48 [kford]
Intent:
20:23:50 [kford]
Users with various disabilities benefit from the features found in spell checkers today when composing text. It is commonplace to create significant amounts of content inside a user agent today for tasks such as email, social networking and web-based productivity applications such as word processors. The intent of this success criteria is to ensure that users with disabilities can easily...
20:23:52 [kford]
...correct spelling errors when compsoing text.
20:23:53 [kford]
Example:
20:23:55 [kford]
Amanda is dyslecix and frequently spells words incorrectly. She is able to correct words when alerted to the errors. She navigates to her web-based email application and composes a new message. The user agent alerts her to spelling errors as she is typing and she quickly corrects the mistakes and sends an error free message.
20:24:16 [AllanJ]
action: greg to review definition of toolbar as it may include having the entire UI be configurable including menus, status bars, etc
20:24:16 [trackbot]
Created ACTION-735 - Review definition of toolbar as it may include having the entire UI be configurable including menus, status bars, etc [on Greg Lowney - due 2012-06-12].
20:24:44 [kford]
Topic: Spell Checking
20:25:00 [kford]
3.2.x Provide spell checking functionality
20:25:02 [kford]
User agents provide spell checking functionality for text created inside the user agent (level AA).
20:25:03 [kford]
Intent:
20:25:05 [kford]
Users with various disabilities benefit from the features found in spell checkers today when composing text. It is commonplace to create significant amounts of content inside a user agent today for tasks such as email, social networking and web-based productivity applications such as word processors. The intent of this success criteria is to ensure that users with disabilities can easily...
20:25:06 [kford]
...correct spelling errors when composing text.
20:25:11 [kford]
Example:
20:25:13 [kford]
Amanda is dyslexic and frequently spells words incorrectly. She is able to correct words when alerted to the errors. She navigates to her web-based email application and composes a new message. The user agent alerts her to spelling errors as she is typing and she quickly corrects the mistakes and sends an error free message.
20:25:46 [AllanJ]
gl: 'text created' make it text entered
20:26:24 [AllanJ]
jr: entered in UA text areas
20:27:10 [kford]
3.2.x Provide spell checking functionality
20:27:12 [kford]
User agents provide spell checking functionality for text entered inside the user agent by a user. (level AA).
20:27:13 [kford]
Intent:
20:27:17 [kford]
Users with various disabilities benefit from the features found in spell checkers today when composing text. It is commonplace to create significant amounts of content inside a user agent today for tasks such as email, social networking and web-based productivity applications such as word processors. The intent of this success criteria is to ensure that users with disabilities can easily...
20:27:19 [kford]
...correct spelling errors when composing text.
20:27:21 [kford]
Example:
20:27:22 [kford]
Amanda is dyslexic and frequently spells words incorrectly. She is able to correct words when alerted to the errors. She navigates to her web-based email application and composes a new message. The user agent alerts her to spelling errors as she is typing and she quickly corrects the mistakes and sends an error free message.
20:28:02 [greg]
User agents provide spell checking functionality for text users enter in the user agent. (level AA).
20:29:49 [kford]
Intent:
20:29:51 [kford]
Users with various disabilities benefit from the features found in spell checkers when composing text. It is commonplace to create enter significant amounts of content inside a user agent for tasks such as email, social networking and web-based productivity applications such as word processors. The intent of this success criteria is to ensure that users with disabilities can easily correct...
20:29:52 [kford]
...spelling errors when composing text.
20:30:39 [greg]
How about adding to the Intent: "...particularly users with dyslexia and other disabilities that significantly increase their chance of misspelling words.
20:31:30 [greg]
"This is particularly important for..."
20:31:52 [AllanJ]
Users with various disabilities, benefit from the features found in spell checkers when composing text. This is particularly important for users with dyslexia and other disabilities that significantly increase their chance of misspelling words. It is commonplace to enter significant amounts of content inside a user agent for tasks such as email, social networking and web-based productivity...
20:31:54 [AllanJ]
...applications such as word processors. The intent of this success criteria is to ensure that users with disabilities can easily correct .spelling errors when composing text.
20:33:09 [greg]
I'd change "The user agent alerts her to spelling errors as she is typing and she quickly corrects the mistakes and sends an error free message." to "The user agent alerts her to spelling errors as she is typing so she can quickly correct the mistakes and sends an error free message."
20:33:24 [AllanJ]
Amanda is dyslexic and frequently spells words incorrectly. She is able to correct words when alerted to the errors. She navigates to her web-based email application and composes a new message. The user agent alerts her to spelling errors as she is typing and she quickly corrects the mistakes and sends an error free message.
20:34:11 [AllanJ]
resolved: new 3.2.x spell check
20:34:20 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0103.html
20:34:36 [AllanJ]
topic: reword of 5.3.2
20:35:18 [AllanJ]
Suggest moving to the wording of ATAG 2.0 (http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/#sc_a121)
20:35:19 [AllanJ]
Accessibility Guidelines: If the user agent contains non-web-based user interfaces, then those non-web-based user interfaces follow user interface accessibility guidelines for the platform. (Level A)
20:35:21 [AllanJ]
Intent:
20:35:22 [AllanJ]
The intent of this success criterion is to ensure that user agent user interfaces that are not web applications are more accessible to authors with disabilities. Existing platform accessibility guidelines are referenced because accessibility guidelines already exist for many platforms and this wording allows developers the flexibility to conform with accessibility legislation in their markets.
20:35:24 [AllanJ]
Note: Developers should see the documents listed in the "Related Resources for Success Criterion A.1.2.1" section. Unless special circumstances exist (e.g., a document has been superseded, the platform has undergone major architectural changes), the listed resources should be assumed to be relevant to the platforms listed.
20:35:25 [AllanJ]
Examples:
20:35:27 [AllanJ]
Mobile browser: The developer of a browser app for the iPhone platform follows the guidance provided in the "Accessibility Programming Guide for iPhone OS".
20:35:29 [AllanJ]
Related Resources for Success Criterion A.1.2.1:
20:35:31 [AllanJ]
The following is a non-exhaustive list of accessibility guidelines for various platforms:
20:35:33 [AllanJ]
Desktop OS
20:35:35 [AllanJ]
GNOME Desktop on Linux: GNOME Accessibility Developers Guide
20:35:37 [AllanJ]
KDE Desktop on Linux: Developer's Information
20:35:39 [AllanJ]
Mac OS: Accessibility Overview
20:35:41 [AllanJ]
Microsoft Windows: Accessibility Overview
20:35:43 [AllanJ]
Mobile OS
20:35:46 [AllanJ]
Android: Android Developers: Designing for Accessibility
20:35:47 [AllanJ]
BlackBerry: BlackBerry Accessibility
20:35:49 [AllanJ]
iPhone OS: Accessibility Programming Guide for iPhone OS
20:35:51 [AllanJ]
Cross-OS environments
20:35:53 [AllanJ]
Eclipse: Designing Accessible Plug-ins in Eclipse
20:35:55 [AllanJ]
Java SE: Java SE Desktop Accessibility
20:35:58 [AllanJ]
Lotus Notes: Lotus Notes Checklist
20:35:59 [AllanJ]
The following is a non-exhaustive list of general software accessibility guidelines:
20:36:01 [AllanJ]
ISO 9241-171:2008 Ergonomics of human-system interaction - Part 171: Guidance on software accessibility
20:36:03 [AllanJ]
Software Checklist (IBM)
20:36:05 [AllanJ]
Section 508 ยง1194.21 Software applications and operating systems
20:36:08 [AllanJ]
The WAI International Policies Relating to Web Accessibility resource includes links to various international legislation and other policies that may include applicable accessibility guidelines for non-web-based functionality.
20:36:12 [AllanJ]
jr: this replace the old 5.3.2
20:36:14 [AllanJ]
... how do you meet this, review platform a11y specs.
20:36:18 [AllanJ]
... now just grab the right documents/specs and follow them
20:37:08 [AllanJ]
gl: we had a definition of accessibility features.
20:38:05 [AllanJ]
jr: old 5.3.2 was hard for developers to do.
20:38:27 [Jan]
http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0104.html
20:38:40 [AllanJ]
topic: whole word spell check
20:39:10 [AllanJ]
action: jan review new wording on 5.3.2 at the next meeting
20:39:10 [trackbot]
Created ACTION-736 - Review new wording on 5.3.2 at the next meeting [on Jan Richards - due 2012-06-12].
20:39:33 [AllanJ]
action: jim to present 3.3.2 to list and bring up at next meeting
20:39:34 [trackbot]
Created ACTION-737 - Present 3.3.2 to list and bring up at next meeting [on Jim Allan - due 2012-06-12].
20:40:00 [AllanJ]
jr: replace find with Text search
20:40:17 [AllanJ]
... then need change stems in several sc.
20:40:34 [AllanJ]
resolved: replace find with 'text search' in the document
20:41:13 [AllanJ]
jan's proposals"
20:41:18 [AllanJ]
(1) For all of the SCs in 2.4, change "Find" to "Text Search"
20:41:19 [AllanJ]
(2) Splitting out searching alternates (building on what was discussed earlier):
20:41:21 [AllanJ]
2.4.5 Search in alternative content: The user can perform text searches within textual alternative content (e.g.
20:41:22 [AllanJ]
*text alternatives for non-text content*, captions) even when the textual alternative content is not rendered onscreen.
20:41:24 [AllanJ]
Intent:
20:41:25 [AllanJ]
Authors frequently provide alternative content to meet web content accessibility guidelines, which users with disabilities will experience as part of the content. The purpose of this success criteria is to ensure that find functionality allows users to locate this content, even if it may not be visible rendered.
20:41:27 [AllanJ]
Examples:
20:41:28 [AllanJ]
- Ronda typically browses the web with images turned off so she sees the alternative text for images rendered in place of images. She visits a favorite web site on a friend's computer and knows she wants to find a link to her favorite artist's photo gallery. On her computer this is the artist's name so she searches for that word on her friend's computer. The alt text is not displayed in this...
20:41:30 [AllanJ]
...case but the artist's image is highlighted because her find command has associated the alt text with the image.
20:41:32 [AllanJ]
(3) 2.4.X Text Search (Enhanced): The user can specify that a text search will be:
20:41:34 [AllanJ]
(a) case-sensitive; and
20:41:36 [AllanJ]
(b) whole word only.
20:41:39 [AllanJ]
Intent: Many users make use of text search to reduce the number of keystrokes required to reach a known location within web content. The number of unintended search results can be reduced by allowing the user to specify that capitalization of the search term and whether the term is a whole word.
20:41:42 [AllanJ]
Examples:
20:41:44 [AllanJ]
- Dennis uses a screen reader. He wants to find all the instances of his friend Bill in a blog post about finances. He needs to specify case and that the search term is a "whole word" in order to avoid stopping at instances of "bill" or "Billing ...". Later, he searches for his friend's name in a blog post about poetry where the author never uses capital letters. In this instance he...
20:41:49 [AllanJ]
...specifies that case does not matter.
20:42:02 [AllanJ]
gl: comment, alternative content phrase is really long.
20:42:06 [AllanJ]
gl: comment, alternative content phrase is really long.
20:42:12 [AllanJ]
all vote yes
20:42:36 [AllanJ]
resolved: put 2.4.5 above in the document
20:44:41 [greg]
To meet web content accessibility guidelines, authors frequently provide alternative content which users with disabilities will experience as part of the content.
20:45:00 [AllanJ]
rrsagent, make minutes
20:45:00 [RRSAgent]
I have made the request to generate http://www.w3.org/2012/06/05-ua-minutes.html AllanJ
22:08:05 [AllanJ]
AllanJ has joined #ua