See also: IRC log
<trackbot> Date: 15 March 2012
<jeanne> https://www.w3.org/WAI/UA/tracker/actions/468
<jeanne> https://www.w3.org/WAI/UA/tracker/actions/468
It's not the most clearly worded of SC. Not clear how "priority properties defined by the author or user agent" is or relates to the Intent or Examples. Could fix SC or fix IER to better explain it.
Current wording:
3.1.2 Option to Ignore: The user can turn off rendering of non-essential or low priority text messages or updating/changing information in the content based on priority properties defined by the author or the user agent. (Level AA)
<kford> We are phoning back in two minutes.
Proposed rewrite to 3.1.2:
3.1.2 Reduce Interruptions: The user can turn off recognized non-essential or low priority messages and updating/changing information in the user agent user interface and rendered content.
Intent of Success Criterion 3.1.2 :
Messages designed to inform the user can be a burden to users for whom keypress is time-consuming, tiring, or painful. It's important that these users be able to avoid unnecessary messages. Similarly, users with some cognitive impairments find it difficult to deal with constant distractions caused by updating visual or audio information, and would prefer to hide unnecessary updates.
Examples of Success Criterion 3.1.2 :
• The browser has an update ready. The user should have the option to be informed of an update or, instead, only get update information when the user actively requests it.
• A web page has a stock market ticker that is marked as having a low priority level using the WAI-ARIA aria-live:polite value. Shirley has a cognitive disability and is distracted by the page flicker, so she changes the browser’s preference setting to indicate that regions with low priority level should not be automatically updated.
Once again, here's the proposed rewrite:
3.1.2 Reduce Interruptions: The user can turn off recognized non-essential or low priority messages and updating/changing information in the user agent user interface and rendered content.
Intent of Success Criterion 3.1.2 :
Messages designed to inform the user can be a burden to users for whom keypress is time-consuming, tiring, or painful. It's important that these users be able to avoid unnecessary messages. Similarly, users with some cognitive impairments find it difficult to deal with constant distractions caused by updating visual or audio information, and would prefer to hide unnecessary updates.
Examples of Success Criterion 3.1.2 :
• The browser has an update ready. The user should have the option to be informed of an update or, instead, only get update information when the user actively requests it.
• A web page has a stock market ticker that is marked as having a low priority level using the WAI-ARIA aria-live:polite value. Shirley has a cognitive disability and is distracted by the page flicker, so she changes the browser’s preference setting to indicate that regions with low priority level should not be automatically updated.
Revised Intent per Jeanne:
It's important that users be able to avoid unnecessary messages. Messages designed to inform the user can be a burden to users for whom keypress is time-consuming, tiring, or painful. Similarly, users with some cognitive impairments find it difficult to deal with constant distractions caused by updating visual or audio information, and would prefer to hide unnecessary updates.
<mth> should it be
<mth> 'keypress" or "keypresses are"?
"pressing keys"
An improvement per Mark:
3.1.2 Reduce Interruptions: The user can avoid or defer recognized non-essential or low priority messages and updating/changing information in the user agent user interface and rendered content.
A new example:
Shirley has turned off automatic display of low priority notifications, but she can call up a list of previous notifications to see if she wants to actually deal with any of them.
<KimPatch> Shirley has turned off automatic display of low priority notifications, but she can call up a list of previous notifications if she wants to review any of them.
<KimPatch> Shirley has turned off automatic display of low priority notifications, but she can call up a list of previous notifications if she wants to review
<KimPatch> them.
<KimPatch> 3.2.2 Back Button: The user can return to a previous state or view using a navigational back button or its equivalent.
<KimPatch> Intent of success criterion 3.2.2
<KimPatch> This type of backtracking is important for users whose means of input is not 100% accurate, such as speech input users, to be able to go back to a previous state or view and have a second try. It's also important for users with cognitive issues that involve memory and confusion.
<KimPatch> Examples of Success Criterion 3.2.2
<KimPatch> Joe is using speech input in a relatively noisy room. The program hears an especially loud word from across the room and interprets it as Joe saying "Enter" to click a selected link. Joe says "Go Back" to go back to the page key was on.
<KimPatch> Mike's head injury leaves him easily distracted. He is in the middle of a search when the phone rings. When he comes back he says "Go Back" to reorient himself.
Could add to the end of the Intent paragraph, "This is also beneficial for users for whom navigation is time consuming, tiring, or painful, as it allows them to avoid having to re-enter long URLs or form input."
<jeanne> Intent: Being able to retrace a navigation step is important for users with cognitive issues that involve memory and confusion, as well as users whose means of input is not 100% accurate, such as speech input users or users with fine motor challenges. This is also beneficial for users for whom navigation is time consuming, tiring, or painful, as it allows them to avoid having to re-enter long URLs
<jeanne> or form input.
<mth> It's also beneficial for users with cognitive issues, such as memory impairments, by providing a means for reviewing the steps need to reach a specific page or result.
<KimPatch> Being able to retrace a navigation step is important for users with cognitive issues that involve memory and confusion. It's also important for users whose means of input is not 100% accurate, such as speech input users or users with fine motor challenges. and it's also beneficial for users for whom navigation is time consuming, tiring, or painful, because it allows them to avoid having to...
<KimPatch> ...re-enter long URLs
Re the Mike example, it's not clear to me why being interrupted by a phone call would make him have to use the back button.
<KimPatch> Mike's head injury leaves him easily distracted. He is in the middle of a search when the phone rings. When he comes back he says "Go Back" to go back to the original search page so he can reorient himself.
<KimPatch> Being able to retrace a navigation step is important for users with cognitive issues that involve memory and attention. It's also important for users whose means of input is not 100% accurate, such as speech input users or users with fine motor challenges. and it's also beneficial for users for whom navigation is time consuming, tiring, or painful, because it allows them to avoid having to...
<KimPatch> ...re-enter long URLs.
Discussion of whether a list of previous documents counts, and it probably does.
<jeanne> RESOLUTION: Add SC 3.2.2 as a level A
We discussed the fact that some media players don't implement the back button, but most do implement a list of previous media if they're not completely driven by their host application.
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) No ScribeNick specified. Guessing ScribeNick: Greg Inferring Scribes: Greg Default Present: Jeanne, kford, Greg_Lowney, Kim_Patch, sharper, +1.609.734.aaaa Present: Greg Jeanne Kim Simon Mark Kelly Regrets: Jim Wayne Jan WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 15 Mar 2012 Guessing minutes URL: http://www.w3.org/2012/03/15-ua-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]