Minutes: User Agent Accessibility Guidelines Working Group Teleconference 05 May 2011

[Description: W3C]<http://www.w3.org/>

- DRAFT -
User Agent Accessibility Guidelines Working Group Teleconference
05 May 2011

See also: IRC log<http://www.w3.org/2011/05/05-ua-irc>

Attendees
Present
JAllan, Greg, kford, sharper, Mark_Hakkinen, Jim, Kelly, Simon, Mark
Regrets
JSpellman
Chair
JimAllan, KellyFord
Scribe
kford
Contents

  *   Topics<http://www.w3.org/2011/05/05-ua-minutes.html#agenda>
     *   EIR creation for GL 2.8<http://www.w3.org/2011/05/05-ua-minutes.html#item01>
     *   EIR SC 1.11.2 Extended Link Information:: The following<http://www.w3.org/2011/05/05-ua-minutes.html#item02>
     *   EIR for GL 2.9 Provide control of content that may reduce<http://www.w3.org/2011/05/05-ua-minutes.html#item03>
     *   survey results<http://www.w3.org/2011/05/05-ua-minutes.html#item04>
  *   Summary of Action Items<http://www.w3.org/2011/05/05-ua-minutes.html#ActionSummary>

________________________________

<trackbot> Date: 05 May 2011

<JAllan> http://www.w3.org/WAI/UA/2011/ED-IMPLEMENTING-UAAG20-20110406/#gl-configure-controls

<JAllan> information is provided for each link (Level AAA)

<JAllan> :http://www.w3.org/WAI/UA/2011/ED-IMPLEMENTING-UAAG20-20110406/#gl-info-link

<JAllan> accessibility [mostly media]

<JAllan> http://www.w3.org/WAI/UA/2011/ED-IMPLEMENTING-UAAG20-20110406/#gl-control-inaccessible-content

<JAllan> mechanism.http://www.w3.org/WAI/UA/2011/ED-IMPLEMENTING-UAAG20-20110406/#gl-focus-mechanism
EIR creation for GL 2.8

<JAllan> http://lists.w3.org/Archives/Public/w3c-wai-ua/2011AprJun/0028.html

<scribe> Scribe: kford

<JAllan> EIR Proposal

<JAllan> previous iteration: http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0073.html

<sharper> http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0078.html

<sharper> http://silversurfers.digitalunite.com/

<JAllan> 2.8.1 (former 4.8.1) Configure Position:

<JAllan> When graphical user agent user interfaces have toolbars, panels, inspectors, or similar,

<JAllan> the user can add, remove and configure the position of user agent user interface

<JAllan> controls from a pre-defined set. (Level AAA)

Group is combining two proposals for these.

<JAllan> The objective of this criteria is to allow the user to customize the toolbars of a user agent in ways that work best for the method in which he or she is using the browser. This can reduce keystrokes, bring buttons into view that are hidden by default or otherwise allow the user to interact with the user agent in a more efficient fashion. Similarly users with low vision may have to excessively mov

<JAllan> e their magnified view-port to see frequently used controls. Enabling these controls to be situated together removes much of the strain faced by these users, and increases productivity as

<JAllan> task completion times are decreased.

<JAllan> The objective of this criteria is to allow the user to customize the toolbars of a user agent in ways that work best for the method in which he or she is using the browser. This can reduce keystrokes, bring buttons into view that are hidden by default or otherwise allow the user to interact with the user agent in a more efficient fashion. Similarly users with low vision may have to excessively mov

<JAllan> e their magnified view-port to see frequently used controls. Enabling these controls to be situated together removes much of the strain faced by these users, and increases productivity as task completion times are decreased.

<JAllan> The objective of this criteria is to allow the user to customize the toolbars of a user agent in ways that work best for the method in which he or she is using the browser. This can reduce keystrokes, bring buttons into view that are hidden by default or otherwise allow the user to interact with the user agent in a more efficient fashion. Users with dexterity impairments or mobility...

<JAllan> ...impairments may have problems making the large movements required to select between non-adjacent controls which they need to use frequently. Similarly users with low vision may have to excessively move their magnified view-port to see frequently used controls. Enabling these controls to be situated together removes much of the strain faced by these users, and increases productivity as...

<JAllan> ...task completion times are decreased.

<JAllan> Examples of Success Criterion 2.8.1 (former 4.8.1) :

<JAllan> Martin accesses the computer by pressing keys with a stick held in his mouth known as a mouthstick and gets around the user agent with taps on the tab and arrow keys. The designers of a user agent have decided to place a button for printing a web page as the last button on a toolbar. This button requires six presses of a right arrow key to reach for Carl and is the only button he uses on...

<JAllan> ...the toolbar. Using a preferences dialog, Martin is able to configure this toolbar to only show the Print button, reducing the number of presses he must issue with his mouthstick to one.

<JAllan> 2.8.2 (former 4.8.2) Restore Default Toolbars:

<JAllan> The user can restore the default toolbar, panel, inspector, configuration. (Level AAA)

<JAllan> * Intent of Success Criterion 2.8.2 (former 4.8.2) :

<JAllan> Mistakes happen. If a user has modified the toolbar incorrectly it can

<JAllan> often be difficult to return to a stable state so that these errors can

<scribe> ACTION: JS to update document with intent and examples for 2.8.1 and 2.8.2 from last text pasted from JA. [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action01]

<trackbot> Created ACTION-548 - Update document with intent and examples for 2.8.1 and 2.8.2 from last text pasted from JA. [on Jeanne F Spellman - due 2011-05-12].

<JAllan> be corrected. There are additional pressures in this regard for people

<JAllan> with learning difficulties who make more use of toolbars than they do of

<JAllan> textual menus. Building an easily selectable mechanism to restore these

<JAllan> defaults saves user time and reduces stress.

<JAllan> * Examples of Success Criterion 2.8.2 (former 4.8.2) :

<JAllan> Jack, is an 80 year old web surfer who is intellectually very sharp

<JAllan> but experiences tremors in his hands when required to make fine

<JAllan> movements with the mouse. To help himself he is setting up the toolbar

<JAllan> so that 'spacers' are placed between each component to prevent

<JAllan> accidental selection of adjacent buttons. Today his tremors are

<JAllan> particulaly bad and Jack makes a number of mistakes becoming

<JAllan> increasingly frustrated that while trying to correct these errors he

<JAllan> begins to make many more. Jack just wants to start over. Luckily the

<JAllan> Browser manufacturer has included an easy mechanism to restore the

<JAllan> default toolbar configuration. Jack chooses this option and successfully

<JAllan> starts over the next day.

<JAllan> * Related Resources for Success Criterion 2.8.2 (former 4.8.2) :
EIR SC 1.11.2 Extended Link Information:: The following

<JAllan> 1.11.2 (former 3.13.2) Extended Link Information:

<JAllan> The following information is provided for each link (Level AAA) :

<JAllan> link title,

<JAllan> technology type (of the linked Web resource)

<JAllan> internal/external: (whether the link is internal to the resource e.g., the link is to a target in the same Web page)

<JAllan> Simon's Proposal http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0040.html

<JAllan> Greg's Response http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0046.html

<JAllan> current draft: http://www.w3.org/WAI/UA/2011/ED-IMPLEMENTING-UAAG20-20110428/

<Greg> http://www.w3.org/WAI/UA/2011/ED-UAAG20-20110428/MasterUAAG20110426.html

JA: We should already know if these areinternalor external so I'm not sure this is needed.
... On technology tupe I guess this is looking at the source and telling you?

GL: I don't know if there is a standard way to query a server and know this.

JA: KF at one point asked why individuals with disabilities should get more info?
... I'm making a case to pitch this.

GL: Is there a big beneift to people with disabilities to having this?
... How about link title? But this is used inconsistently.
... But the alt would be the default.

<Greg> A use case in favor of providing the user a way to perceive the title attribute: a person using a mouse can have an element's title attribute presented to them by hovering the mouse over it, but a user who cannot use a mouse needs an alternative method.

<mhakkinen> mth .. my dsl went down.

<JAllan> ACTION: js to add "remove 1.11.1 extended link information" on survey for next week [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action02]

<trackbot> Created ACTION-549 - Add "remove 1.11.1 extended link information" on survey for next week [on Jeanne F Spellman - due 2011-05-12].
EIR for GL 2.9 Provide control of content that may reduce

<JAllan> http://www.w3.org/WAI/UA/work/wiki/Guideline_2.9

<JAllan> GL: cites Mark for comma abuse

<mhakkinen> It is a character flaw

<Greg> (Yeah, because it takes one to know one.)

<Greg> In 2.9.5 Intent, might also include the fact that a person may want to slow down the media if they are trying to take notes, and do so slowly because of language or dexterity impairments, etc.

<mhakkinen> Good point

<JAllan> I edited wiki for typos and added Greg's comment

<scribe> ACTION: JS update document with intent and examples from wiki entry for 2.9.5. [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action03]

<trackbot> Created ACTION-550 - Update document with intent and examples from wiki entry for 2.9.5. [on Jeanne F Spellman - due 2011-05-12].

Now moving to survey.

<JAllan> http://www.w3.org/2002/09/wbs/36791/20110503/results
survey results

Looking at 3.4.1, avoid unpredictable focus.

<JAllan> http://www.w3.org/WAI/UA/work/wiki/Keyboard,_Focus,_and_Navigation_Restructuring

<scribe> ACTION: JS update document with text from wiki entry on 3.4.1. [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action04]

<trackbot> Created ACTION-551 - Update document with text from wiki entry on 3.4.1. [on Jeanne F Spellman - due 2011-05-12].

Looking at 3.4.2, avoide side effects of navigation

<Greg> In the April editor's draft it read "1.9.11 (former 3.11.11) On Focus: The user can ensure that moving the keyboard focus to or from an enabled element does not cause the user agent to take any further action. (Level A)".

<JAllan> The user can move the keyboard focus to or from any enabled element without causing the user agent to take any further action. (Level A)

<Greg> People seem to agree with the observation in the survey that we need to exempt some effects, including transient presentation of information and scrolling.

<JAllan> The user can move the keyboard focus without causing the user agent to take any further action, other than the presentation of information (e.g. scrolling or pop-ups that do not change the focus or selection).

All think this looks good.

<scribe> ACTION: JUS update document with wiki text from 3.4.2 [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action05]

<trackbot> Sorry, couldn't find user - JUS

<scribe> ACTION: JS Update document with wiki text for 3.4.2 [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action06]

<trackbot> Created ACTION-552 - Update document with wiki text for 3.4.2 [on Jeanne F Spellman - due 2011-05-12].

Summary of Action Items
[NEW] ACTION: js to add "remove 1.11.1 extended link information" on survey for next week [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action02]
[NEW] ACTION: JS to update document with intent and examples for 2.8.1 and 2.8.2 from last text pasted from JA. [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action01]
[NEW] ACTION: JS update document with intent and examples from wiki entry for 2.9.5. [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action03]
[NEW] ACTION: JS update document with text from wiki entry on 3.4.1. [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action04]
[NEW] ACTION: JS Update document with wiki text for 3.4.2 [recorded in http://www.w3.org/2011/05/05-ua-minutes.html#action06]

[End of minutes]

Received on Thursday, 5 May 2011 18:39:12 UTC