W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2009

Re: Minutes of Face To Face Meeting Day 1

From: David Poehlman <poehlman1@comcast.net>
Date: Fri, 6 Nov 2009 07:55:49 -0500
Cc: User Agent Working Group <w3c-wai-ua@w3.org>
Message-Id: <7314AB8C-8E75-4738-B6B9-E7D694F93D1A@comcast.net>
To: Jeanne Spellman <jeanne@w3.org>
see the access module for work and also aria.

On Nov 5, 2009, at 8:57 PM, Jeanne Spellman wrote:

Minutes:
http://www.w3.org/2009/11/05-ua-minutes

IRC Log



Text of Minutes
   [1]W3C

      [1] http://www.w3.org/

   User Agent Accessibility Guidelines Working Group Teleconference

05 Nov 2009

   See also: [2]IRC log

      [2] http://www.w3.org/2009/11/05-ua-irc

Attendees

   Present
          Jim, Kim, Greg, Jeanne, Mark, Kelly

   Regrets
          Henny, Jan

   Chair
          Jim, Kelly

   Scribe
          kford

Contents

     * [3]Topics
         1. [4]UA F2F
         2. [5]walk through issues and action items - 1 hr time limit,
            not problem solving, assigning, eliminating, prioritizing
         3. [6]techniques for guideline 4
         4. [7]4.1.2
         5. [8]4.1.3
         6. [9]4.1.4 separate selection from activation
         7. [10]4.1.5 Present Direct Commands in Rendered Content
         8. [11]4.1.6 Standard Text Area Navigation Conventions:
         9. [12]4.1.8 Important Command Functions
        10. [13]4.1.9 Override of UI Keyboard Commands
        11. [14]4.1.11 User Override of Accesskeys
        12. [15]4.1.10 Specify preferred keystrokes
        13. [16]4.1.12 Present Direct Commands in User Interface
        14. [17]4.5 Store preference settings
        15. [18]4.6.1 Search Rendered Content
        16. [19]4.7.1 Structured Navigation
     * [20]Summary of Action Items
     _________________________________________________________



   <trackbot> Date: 05 November 2009

UA F2F

   meetin: UAAG F2F

   <scribe> meeting: UAAG F2F

   <jallan> agenda

   <jallan> + walk through issues and action items - 1 hr time limit,
   not problem solving, assigning, eliminating, prioritizing

walk through issues and action items - 1 hr time limit, not problem
solving, assigning, eliminating, prioritizing

   <jallan> UAAG10 techniques
   [21]http://www.w3.org/TR/UAAG10-TECHS/guidelines.html

     [21] http://www.w3.org/TR/UAAG10-TECHS/guidelines.html

   <jeanne>
   [22]http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/Ma
   sterUAAG20091103.html

     [22] http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/MasterUAAG20091103.html

   Current Action Items:
   [23]http://www.w3.org/WAI/UA/tracker/actions/open

     [23] http://www.w3.org/WAI/UA/tracker/actions/open

   Current Issues: [24]http://www.w3.org/WAI/UA/tracker/issues/open

     [24] http://www.w3.org/WAI/UA/tracker/issues/open

   <scribe> Scribe: kford

   JA: We are going to start for an hour to go through our actions.
   ... We want to clear these up, see if we need to reassign or give
   new dates ro what?

   Closing action 32 as previously completed.

   Closing action 34 as completed.

   Updating action 35 to have a date of March 2010.

   Closing action 37 as completed because section 1 has been updated.

   Updating action 39 to assign to Jim and setting to a due date in
   December.

   Group talking about action 40 around a technique for a simplified
   style sheet for clean printing.

   Closing action 40.

   <greg> Issue: It might be good for an SC to specifically require UA
   to allow the user to use any style sheet, including print-oriented
   style sheets, on the screen. That would allow them to take advantage
   of simplified layouts created for printing.

   <trackbot> Created ISSUE-49 - It might be good for an SC to
   specifically require UA to allow the user to use any style sheet,
   including print-oriented style sheets, on the screen. That would
   allow them to take advantage of simplified layouts created for
   printing. ; please complete additional details at
   [25]http://www.w3.org/WAI/UA/tracker/issues/49/edit .

     [25] http://www.w3.org/WAI/UA/tracker/issues/49/edit

   Updating issue 41 to a December deadline.

   Closing 42, repalced by action 230 which is a more comprehensive
   multimedia success criteria on Mark.

   Closing action 43 dealing with selecting audio only from video
   stream. User agents/content providers may want to consider this as a
   feature but not accessibility specific enough.

   Discussion around action 44 dealing with scaling of captioned text.

   KFord: I think our general let you do what you want with the text
   applies here.

   Greg: We should be more explicit that we want this to apply to all
   text from the author or other sources of text that appear in the
   user agent.

   Updating action 44 to be explicit.

   Updated action 45 with new guideline number and changed the date.

   Closing action 46 becuase is covered by other actions.

   Issue: When working through our docuemnt we need to be sure that
   examples and success criteria reflect our true intnet. Namely, if
   text appears in the UA from any source we want the user to have
   control over as many of the attributes of that text as possible.

   <trackbot> Created ISSUE-50 - When working through our docuemnt we
   need to be sure that examples and success criteria reflect our true
   intnet. Namely, if text appears in the UA from any source we want
   the user to have control over as many of the attributes of that text
   as possible. ; please complete additional details at
   [26]http://www.w3.org/WAI/UA/tracker/issues/50/edit .

     [26] http://www.w3.org/WAI/UA/tracker/issues/50/edit

   Updating date on action 47.

   Issue: Think about concepts around user notification, do we ha

   <trackbot> Created ISSUE-51 - Think about concepts around user
   notification, do we ha ; please complete additional details at
   [27]http://www.w3.org/WAI/UA/tracker/issues/51/edit .

     [27] http://www.w3.org/WAI/UA/tracker/issues/51/edit

   ndle them well in UAAG?

   Closing action 48.

   Closing action 50. When writing our examples we should look at the
   notes from action 50.

   Changing date on on 51. Can we work with Andrew to help draft
   success criteria.

   Updating 53 to a Jan 2010 date.

   Closing action 54 and issue 23 around timely exchanges through APIs.
   Technique for timely exchange needs to indicate that accessibilit

   y APIS should not negatively impact browser performance in a
   perceivalbe way i.e. 300 MS.

   Closing issue 66.

   Closing 79, 81 and 83 and 97 as completed.

   Closing 103 around language on web based and non web based.

   Closing issue 105.

   Updating 107 to 11/12.

   Group developing list of success criteria we want to review at F2F.
   this includes 3.1 and 4.9 as of now.

   Closing 111.

   Closing 115 as part of gneeral 4.9 review.

   Updating action 120 to a December deadline.

   Closing 121.

   Closing 128 as completed.

   Closing 140.

   Updating date on 150 to Jan 2010.

   Closing 158.

   Updating wording in 162.

   Closing 163.

   Closing 164.

   Updating action 169 to 11/19.

   Techniques for 4.1 need to address css overflow not operable by
   keyboard.

   Closing 169.

   Updating 170 to December and assigning to kford.

   Updating 173 to a December date and assigning to Kim.

   Updating 174 to December.

   Taking break at 174 being last completed review of actions.

techniques for guideline 4

   <jeanne>
   [28]http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/Ma
   sterUAAG20091103.html

     [28] http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/MasterUAAG20091103.html

   <jeanne>
   [29]http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/Ma
   sterUAAG20091103.html

     [29] http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/MasterUAAG20091103.html

   Group dividing into pairs to write techniques.

   <jallan> [30]http://www.w3.org/TR/UAAG10-TECHS/guidelines.html

     [30] http://www.w3.org/TR/UAAG10-TECHS/guidelines.html

   Drqaft for 4.1.9.

   Users need to be in control of how they interact with the user
   agent. Assistive technology and physical keyboard input needs mean
   that certain keyboard combinations are easier for a user to enter.
   For example ctrl+f may be a command in a screen reader to read the
   itemm with focus and this is also typically a user agent find
   command. The user agent needs to allow the user to reassign the...

   scribe: find command to a more appropriate key binding. To allow
   this level of user control, a user agent may provide a list of user
   interface features and default keyboard assignments with options for
   the user to assign new key combinations.

   <mth> draft 4.1.11 Intent

   <mth> Content authors may utilize the Accesskey attribute and ARIA
   to define short cut keys which allow quick access to specific parts
   of their Web content. The author selected short cuts may utilize
   keystrokes that

   <mth> are unique to their site, differing from conventions used, and
   or familiar, to users of other similar sites, or sites

   <mth> offering similar functionality. Users of assistive
   technologies who rely upon keyboard input may

   <mth> wish to have a consistent mapping of shortcut keys to commonly
   accessed parts of a Web site. User agents should allow

   <mth> users to define a preferred accesskey for common content
   elements, as defined by their ARIA role, and which override

   <mth> any author specified keybinding for that page content. The
   user should have the option to make any defined override to be

   <mth> persistent across browsing sessions.

   updated 4.1.9 intent and example.

   Users need to be in control of how they interact with the user
   agent. Assistive technology and physical keyboard input needs mean
   that certain keyboard combinations are easier for a user to enter.
   For example ctrl+f may be a command in a screen reader to read the
   itemm with focus and this is also typically a user agent find
   command. The user agent should allow the user to reassign the...

   scribe: find command to a non-conflicting key binding. To allow this
   level of user control, the user agent could provide a list of user
   interface features and default keyboard assignments with options for
   the user to assign new key combinations. User keyboard
   customizations should be saved similar to other user preferences by
   the user agent.

   +4.1.12 draft.

   For many users, including those who use the keyboard or and input
   method such as speech, the keyboard is often a primary method of
   user agent control. It is inportant that direct keyboard commands
   assigned to user agent functionality be discoverable as the user is
   exploring the user agent. For example, the speech input user who
   sees a button on a toolbar needs to be able to determine that...

   scribe: ctrl+p is the keyboard equivalent for activating the print
   button. If such key assignments are not displayed as the user
   interface by default, a user agent should have an option to alter UI
   display to include all direct hotkey assignments visually near the
   commands such assignments activate.

   <jeanne> 4.1.1 Keyboard Operation Intent

   <jeanne> A user should be able to navigate, read and use all of the
   web page or application without needing to use a mouse. Some users
   do not use a mouse, others can only use a pointing device that uses
   the keyboard API. Therefore, nsure that the user can interact with
   enabled elements, select content, navigate viewports, configure the
   user agent, access documentation, install the user agent, and
   operate user interface controls, all entirely through keyboard
   input.

   <jeanne> User agents generally support at least three types of
   keyboard operation:

   <jeanne> 1. Direct (e.g., keyboard shortcuts such a "F1" to open the
   help menu; see checkpoint 11.4 for single-key access requirements),

   <jeanne> 2. Sequential (e.g., navigation through cascading menus),
   and

   <jeanne> 3. Spatial (e.g., when the keyboard is used to move the
   pointing device in two-dimensional visual space to manipulate a
   bitmap image).

   <jeanne> User agents should support direct or sequential keyboard
   operation for all functionalities. Furthermore, the user agent
   should satisfy this checkpoint by offering a combination of
   keyboard-operable user interface controls (e.g., keyboard operable
   print menus and settings) and direct keyboard shortcuts (e.g., to
   print the current page).

   <jallan> comments -example for spatial, should not just be graphics.
   for example navigating a table, or moving to the same horizontal
   location on vertical lines.

   <jeanne> 4.1.1 Keyboard Operation Intent

   <jeanne> A user should be able to navigate, read and use all of the
   web page or application without needing to use a mouse. Some users
   do not use a mouse, others can only use a pointing device that uses
   the keyboard API. Therefore, nsure that the user can interact with
   enabled elements, select content, navigate viewports, configure the
   user agent, access documentation, install the user agent, and
   operate user interface controls, all entirely through keyboard
   input.

   <jeanne> User agents generally support at least three types of
   keyboard operation:

   <jeanne> 1. Direct (e.g., keyboard shortcuts such a "F1" to open the
   help menu; see checkpoint 11.4 for single-key access requirements),

   <jeanne> 2. Sequential (e.g., navigation through cascading menus),
   and

   <jeanne> 3. Spatial (e.g., when the keyboard is used to move the
   pointing device in two-dimensional visual space to manipulate a
   bitmap image).

   <jeanne> User agents should support direct or sequential keyboard
   operation for all functionalities. Furthermore, the user agent
   should satisfy this checkpoint by offering a combination of
   keyboard-operable user interface controls (e.g., keyboard operable
   print menus and settings) and direct keyboard shortcuts (e.g., to
   print the current page).

   <jeanne> 2nd try:

   <jeanne> Example:

   <jeanne> The user must be able to do the following through the
   keyboard alone (or pointing device alone or voice alone):

   <jeanne> * Select content and operate on it. For example, if the
   user can select rendered text with the mouse and make it the content
   of a new link by pushing a button, they also need to be able to do
   so through the keyboard and other supported devices. Other
   operations include cut, copy, and paste.

   <jeanne> * Set the focus on viewports and on enabled elements.

   <jeanne> * Install, configure, uninstall, and update the user agent
   software.

   <jeanne> * Use the graphical user interface menus. Some users may
   wish to use the graphical user interface even if they cannot use or
   do not wish to use the pointing device.

   <jeanne> * Fill out forms.

   <jeanne> * Access documentation.

   <jeanne> An author uses the CSS overflow property to constrain the
   size of a block of content. The user agent provides scroll bars to
   display text that overflows the container. The user can use the
   keyboard to enter the element and operate the scrollbars to visually
   access the content. The user can return to the main flow of the next
   element on the page (see SC 4.1.3)

   <jeanne> The author codes a volume control slider widget. The user
   can focus on the widget, and using the arrow keys to increase or
   decrease the volume, and then hit another key to move to the next
   element in the content.

   <jallan> comments - example - the user places the caret on an
   element with a title attribute, the tooltip should be visible and
   remain visible while the caret is in the element

   <jallan> comment - keyboard user, must navigate to an element to
   interact with the element, direct access is more efficient

   <jallan> comment - tooltip display should be under the control of
   the user. user should be able to turn off tooltip on caret 'focus'
   or element focus on active elements

   <jallan> comment - on additional resources - or an overview of
   guideline 4, write an overview of keyboard accessbility, then get
   specific for success criteria

   <jallan> Intent on the Guideline

   <jallan> ...

   <jeanne> <--

   <jallan> ...

   <jeanne> <--

   <jeanne> 4.1.2

   <jeanne> Intent:

   <jeanne> There are many layers of software that can specify what
   happens when the user presses a key. For example, the operating
   system, the user agent interface, the addons or extensions, and
   author supplied accesskeys or javascript. In addition, the assistive
   technology the user may be employing will also have assigned key
   commands. This results in conflicts in order of operations. These
   conflicts impact user expectations of what will happen when a key is
   pressed, cau

   <jeanne> user expectations of what will happen when a key is
   pressed, causing confusion and failure. The most problematic
   situation is when the author supplied scripting has precedence on
   the keyboard commands. Therefore, the user needs a preference that a
   default order: Operating system, user agent interface,
   addon/extension, accesskeys, javascript.

   <jeanne> comment: Remove :the most problematic"

   <jeanne> The author codes a script that makes bananas dance on the
   screen when the user presses Alt-F. The user expectation is that
   Alt-F will open a file menu. When the bananas dance instead of
   opening the file menu, the user is confused or blocked from opening
   the file menu and has no recourse. Therefore, the user agent
   provides a preference setting that makes the Alt-F open the file
   menu. There needs to be a toggle ability, so that the user who wants
   to make the banan

   <jeanne> the bananas dance can do so.

   <jeanne> comment: repetitive list of the order.

   <jallan> issue: in 4.1.2 how to make a keystroke cascade, trickle
   down from UA interface, extensions, accesskeys, scripts. if ALT F
   opens file menu, but the script need the ALT F how UA provide
   mechanism to pass the ALF F to the script and not open the menu

   <trackbot> Created ISSUE-52 - In 4.1.2 how to make a keystroke
   cascade, trickle down from UA interface, extensions, accesskeys,
   scripts. if ALT F opens file menu, but the script need the ALT F how
   UA provide mechanism to pass the ALF F to the script and not open
   the menu ; please complete additional details at
   [31]http://www.w3.org/WAI/UA/tracker/issues/52/edit .

     [31] http://www.w3.org/WAI/UA/tracker/issues/52/edit

   Group returning from lunch. Picking up with review of techniques.

4.1.2

   <jallan> comment - direct access for keystroke...go to a menu of
   bound keys, then ALT-F will have 3 items in a sub menu - file menu,
   accesskey binding, script function

   <jallan> or user hits ALT-F dialog pops-up listing bindings, file
   menu, accesskey function, scripted function

   <jallan> what is still needed is a way for javascript to provide a
   list of bound keys to the UA with human friendly names

   Twitter list of HTML 5 task force people.

   [32]https://twitter.com/laura_carlson/html5accessibilitytf

     [32] https://twitter.com/laura_carlson/html5accessibilitytf

   <jallan> to support i18n, localizaition, the UA should provide a
   mechanism for JS to present binding info - key, name, etc. to the UA
   to resolve conflicts

   <jallan> is the above a requirement. this would allow the discovery
   of keys in use and provide alternative access methods

   <jallan> perhaps send to APIWG?

4.1.3

   <jeanne> Intent: If the user can put focus on an element, that they
   can remove focus and move on to the next element. This is often a
   problem with embedded objects. The user agent needs to provide a way
   to always return to the previous or next element in the content, or
   a known location, such as the address bar. The user agent also needs
   to be able to take control back from the embedded object, no matter
   what it is.

   <jeanne> a) The user can press tab to put focus on an embedded
   object and can press shift-tab to move focus to the previous object
   and tab to move focus to the next object.

   <jeanne> b) the user has moved the focus to a toolbar extension that
   does not relinquish control back to the user agent. The user can
   press Alt-D to move focus to the address bar.

   <jeanne> c) the user has moved the focus to an embedded scripted
   application that was poorly programmed. the user can press alt-N (or
   any documented key combination) that overrides the scripting and
   moves the focus to the next element in the content.

   <jallan> comment- what happens if this function is not there. the
   user cannot move out of the object/element without restarting
   browser or restarting computer

   <jallan> issue: need definition of 'browser extension'

   <trackbot> Created ISSUE-53 - Need definition of 'browser extension'
   ; please complete additional details at
   [33]http://www.w3.org/WAI/UA/tracker/issues/53/edit .

     [33] http://www.w3.org/WAI/UA/tracker/issues/53/edit

   <jallan> comment - used to an issue in Flash, could move focus in,
   move around but never out again, only solutions was to refresh the
   page

4.1.4 separate selection from activation

   <jeanne> This is a repair function for when an author violates WCAG,
   but the user still needs to be able to read a page without
   necessarily activating any controls.

   <jeanne> when a user opens a drop down menu from the keyboard, they
   must be able to use the arrow keys to move up and down the list,
   without triggering an action from the items they are moving past.

   <jeanne> A list of radio buttons where putting the focus on the
   radio button to read it causes the radio button to be selected. The
   user should be able to arrow or tab through the list of radio
   buttons without causing any one to be selected. Selection is a
   separate discrete operation like spacebar. This overrides any author
   provided scripting behavior.

   <jallan> comments - intent, not just WCAG, only 1 example violates
   wcag

   <jallan> another example - form field has data validation, user can
   not exit field until user enters valid data.

4.1.5 Present Direct Commands in Rendered Content

   <greg> Intent:

   <greg> Make it easy to for users to discover or be reminded of
   keyboard shortcuts and similar commands without leaving the context
   in which they're working. Easy keyboard access is especially
   important for people who cannot easily use a mouse.

   <greg> Examples:

   <greg> "[Ctrl+t]" displayed after a link whose accesskey value is
   "t".

   <greg> An audio browser reading the value or label of a form control
   followed by "accesskey control plus t").

   <greg> Mnemonic letters in menu titles are shown with an underline.

   <jallan> comment - applicable shortcut indicated or otherwise
   highlighted

4.1.6 Standard Text Area Navigation Conventions:

   <greg> Intent:

   <greg> Providing a full set of keyboard inputs allows users to
   efficiently--or at all--perform necessary tasks.

   <greg> Making these inputs consistent within and across programs
   greatly reduces learning curve, cognitive load, and errors.

   <greg> Examples:

   <greg> Directional keys, letter keys, and the Enter key function
   should allow navigation within and activation of drop-down menus.

   <greg> Ctrl+C or Command+C should copy selected text to the
   clipboard, allowing the user to avoid manually retyping, and
   possibly needing to memorize, large amounts of data.

   <jallan> comment - what happens when things are not consistent.
   closing dialog boxes are inconsistent ESC or ALT-F4,

   <jallan> ...might be text area keyboard conventions/controls, not
   just navigation.

   <jallan> Ctrl-C is not a navigation command

   <jallan> not menus, use select text in content,

   <jallan> need to update examples

   <jallan> topic 4.1.7 Keyboard Navigation

   <jallan> issue: do we have a SC to support OS conventions for cut
   copy paste etc

   <trackbot> Created ISSUE-54 - Do we have a SC to support OS
   conventions for cut copy paste etc ; please complete additional
   details at [34]http://www.w3.org/WAI/UA/tracker/issues/54/edit .

     [34] http://www.w3.org/WAI/UA/tracker/issues/54/edit

   <greg> Intent:

   <greg> Let the user navigate between sections without having to
   sequentially navigate through everything in every section. Efficient
   keyboard navigation is especially important for people who cannot
   easily use a mouse.

   <greg> Examples:

   <greg> Ctrl+Tab moves the focus to the first navigable item in the
   next frame.

   <greg> The Tab key moves the focus to or away from a group of radio
   buttons, and then directional keys move between buttons within that
   group.

   <jallan> comment - need to be able to choose to go to first item or
   to last point of regard in a viewport

   <jallan> Kim: no this is Ok

   <jallan> GL: need a keystroke to get to first or last active element
   on a page. what about moving within a group of radio buttons

   <jallan> example - consistency - menu wrapping navigation. ISO
   should warn user of wrapping

   <jallan> 4.1.7 seems ambiguious, apply only to UI toolbars, menus or
   also to content groups of radio buttons

   <jallan> issue: 4.1.7 seems ambiguious, apply only to UI toolbars,
   menus; or apply also to content - groups of radio buttons

   <trackbot> Created ISSUE-55 - 4.1.7 seems ambiguious, apply only to
   UI toolbars, menus; or apply also to content - groups of radio
   buttons ; please complete additional details at
   [35]http://www.w3.org/WAI/UA/tracker/issues/55/edit .

     [35] http://www.w3.org/WAI/UA/tracker/issues/55/edit

   <jeanne>
   [36]http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/Ma
   sterUAAG20091103.html#gl-keyboard-access

     [36] http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/MasterUAAG20091103.html#gl-keyboard-access

   <jallan> note - fix example of ctrl+tab so it does not proscribe
   specific focus location

4.1.8 Important Command Functions

   <greg> Intent:

   <greg> Let the user access commonly used functions as efficiently as
   possible. Efficient keyboard navigation is especially important for
   people who cannot easily use a mouse.

   <greg> Examples:

   <greg> The user can open a document by pressing Ctrl+O or Command+O.

   <greg> The user can temporarily enlarge the rendered content by
   pressing Ctrl+Plus, rather than having to invoke a menu, choose a
   command to display a dialog box, select a tab, etc.

   #HTML5 WG #tpac09 Nov 5, breakout sessions irc://irc.w3.org/
   #html-wg #html-wg2 #aapi & #video

   <jeanne> resources should link to 1.1 Comply with applicable
   specifications and conventions

   <jallan> comment - seems these are specific instances of why to use
   OS conventions (cut/copy/paste, file menu, etc)

   <jallan> ...1.1 is so generic. we need to write techniques

4.1.9 Override of UI Keyboard Commands

   4.1.9

   Intent:

   Users need to be in control of how they interact with the user
   agent. Assistive technology and physical keyboard input needs mean
   that certain keyboard combinations are easier for a user to enter.

   Example:

   Ctrl+f may be a command in a screen reader to read the itemm with
   focus and this is also typically a user agent find command. The user
   agent should allow the user to reassign the find command to a
   non-conflicting key binding. To allow this level of user control,
   the user agent could provide a list of user interface features and
   default keyboard assignments with options for the user to...

   scribe: assign new key combinations. User keyboard customizations
   should be saved similar to other user preferences by the user agent.

   <jallan> another example - one handed keyboardist needs to map all
   keys to the left side of the keyboard

4.1.11 User Override of Accesskeys

   <mth> 4.1.11 Intent

   <mth> Content authors may utilize the Accesskey attribute to define
   short cut keys which allow quick access to specific elements,
   actions, or parts of their Web content. The author selected short
   cuts may utilize keystrokes that are unique to their site, differing
   from conventions used, and or familiar, to users of other similar
   sites, or sites offering similar functionality. Users of assistive
   technologies who rely upon keyboard input may wish to have a

   <mth> consistent mapping of shortcut keys to similar, or common
   actions or functions across the sites they visit.

   <mth> User agents should allow users to define a preferred key
   combination for specific instances of author defined accesskeys. The
   user should have the option to make any defined override to be
   persistent across browsing sessions.

   <mth> User agents may also offer the user the option to
   automatically apply preferred key combinations for content which has
   author supplied accesskey bindings, based upon the associated text,
   label, or ARIA role, and which override any author specified
   keybinding for that page content.

   <mth> Example

   <mth> A speech recognition user has defined standard commands to
   access commonly used parts of a Web site. For example, speaking the
   the command "site search" will take the user to a Web site's search
   function. A site author may assign an access key to set focus to the
   search input field, basing the accesskey on the first letter of the
   search engine used (e.g., G for Google or B for Bing, rather than
   the mnemonic S for search). The speech user has specified

   <mth> an override key mapping of S, which is consistent with the
   keystroke issued by the speech recognizer they are using.

   <mth> A mobile device user, whose primary keyboard interface is
   their phone's numeric keypad, maps common Web site actions to
   numeric shortcut keys. For example, the user prefers to have the 1
   key to activate a site's "skip to content" function. An author of a
   site visited daily by this user defines "S" as the accesskey for the
   skip to content function. The user overrides the author defined
   accesskey of "S" with "1".

   <jallan> comment - good place to add i18n example, accesskey - o
   umlaut, but not on local keyboard

   <jallan> comment - intent explains how you do it, not why you do it.

   <jallan> ...seem to be a technique. where do techniques go.

   <jallan> intent - is why, understanding the issue. examples seem to
   scenarios with expected behaviors.

   <jallan> do we need another section for expanding intent, need more
   subheads...intent, examples, how, resources, ???

4.1.10 Specify preferred keystrokes

   <jallan> perhaps should be AAA and follow 4.1.11

   <jallan> intent: User agents may also offer the user the option to
   automatically apply preferred key combinations for content which has
   author supplied accesskey bindings, based upon the associated text,
   label, or ARIA role, and which override any author specified
   keybinding for that page content.

   <jallan> comment - not reader friendly, techanleze

   <greg> Rewrite of 4.1.10 ("Specify preferred keystrokes") includes
   the clause "except for conventional bindings for the operating
   environment"; please rewrite to clarify whether this is PROHIBITED
   or OPTIONAL.

   <greg> The previous also applies to 4.1.9, and possibly others.

4.1.12 Present Direct Commands in User Interface

   4.1.12

   Intent:

   For many users, including those who use the keyboard or and input
   method such as speech, the keyboard is often a primary method of
   user agent control. It is inportant that direct keyboard commands
   assigned to user agent functionality be discoverable as the user is
   exploring the user agent.

   Example:

   The speech input user who sees a button on a toolbar needs to be
   able to determine that ctrl+p is the keyboard equivalent for
   activating the print button. If such key assignments are not
   displayed as part of the user interface by default, a user agent
   should have an option to alter UI display to include all direct
   hotkey assignments visually as part of the controls the hotkeys
   activate.

   <jallan> using this draft
   [37]http://www.w3.org/WAI/UA/2009/ED-UAAG20-20091103/

     [37] http://www.w3.org/WAI/UA/2009/ED-UAAG20-20091103/

   <jallan> what is difference between 4.1.12 and 4.1.5

   <jallan> should be next to each other.

   <jallan> why were they separated.

   <jallan> 4.1.5 is A, 4.1.12 is AA, web content changes - access keys
   can change, UAs generally do not change so revealing keybindings not
   as important

   <scribe> ACTION: Jeanne to renumber 4.1.12 so it is closer to 4.1.5.
   These are the UI and content discovery items for hotkeys. [recorded
   in [38]http://www.w3.org/2009/11/05-ua-minutes.html#action01]

   <trackbot> Created ACTION-241 - Renumber 4.1.12 so it is closer to
   4.1.5. These are the UI and content discovery items for hotkeys. [on
   Jeanne Spellman - due 2009-11-12].

   <jallan> ...currently no UA meets 4.1.12 Present Direct Commands in
   User Interface

   <jallan> comment - need to normalize intent across SC

   Intent:

   Users who rely on accessibility settings do so for multiple reasons
   and may want to adjust software settings in many differing fashions.
   It is key to allow software settings that impact accessibility to be
   configured to meed these differing needs. The easier such settings
   are to discover, the more rapidly the user looking for such settings
   can tailor the software to suit his or her needs. ...

   scribe: Saving such configuration changes between browsing sessions
   allows the software to work the way the user wants each time the
   application is used.

   Example:

   A user who relies on larger text sizes when browsing web pages,
   locates a text adjustment setting in a browser's menus. The user
   sets the text size to the size that makes web contnet readable and
   each time the browser is used, the text is adjusted to that user's
   settings.

   A user locates a control in a web browser called options. Activating
   this control leads to a series of tabs for adjusting multiple
   browser settings. One tab is listed as accessibility and has
   settings such as text size, use custom style sheet, display
   alternative text in place of images, enable caret browsing and other
   settings determined to be of benefit to users with disabilities.

   A user is exploring settings for a web browser and locates an option
   called accessibility. The user is then guided through a series of
   questions asking about how he or she prefers to use software.
   Questions such as color preference, text size, ability to view
   images, the need for captions on videos and such are asked. When the
   user completes these questions, appropriate browser options...

   scribe: are configured and stored.

   A user who has configured accessibility settings in a browser needs
   to use that application on another computer. The browser allows the
   user to transfer such settings from one computer to another, saving
   the need to reconfigure the second machine.

4.5 Store preference settings

   <jallan> comment - change title to 'configure and store preference
   settings'

   <jallan> implementing master document:
   [39]http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/Ma
   sterUAAG20091103.html

     [39] http://www.w3.org/WAI/UA/2009/ED-IMPLEMENTING-UAAG20-20091103/MasterUAAG20091103.html

   <jallan> comment - should include what happens if configure and
   store is not implemented

   <jallan> comment - change font size (control+) is temporary. should
   indicate that temporary change should not be persistent.

   <jallan> ...user locates the permanant configuration of font size,
   sets the size and saves it.

   <jallan> " if feature not implemented then user must change the
   settings every browser session"

   <jallan> new example - user is able to set the default/base font and
   font-size for when the author has not defined a font and font size

   <Judy> SCORM:
   [40]http://en.wikipedia.org/wiki/Sharable_Content_Object_Reference_M
   odel

     [40] http://en.wikipedia.org/wiki/Sharable_Content_Object_Reference_Model

   <jallan> example - user can override author style sheet for font and
   font size

4.6.1 Search Rendered Content

   <jallan> would be good to label examples with specific success
   criteria

   <jallan> comment - image with alt HOME, search alt text should be a
   preference setting

   <jallan> make 2 SC - search text, search alternative

   <jallan> or make an option within search (match case, alternative
   content, up/down)

   <jallan> or provide option to only search alternative content.

   <jallan> discussion of Chrome visual indicator on scroll bar of
   location of hits. helps show clustering of hits on the page. how
   does that get exposed to screen reader etc.

   <jallan> it is meta information. not actionable.

4.7.1 Structured Navigation

   <greg> Intent:

   <greg> Let the user use the keyboard to navigate forwards and
   backwards through elements that they are likely to be interested in
   interacting with. These elements must include, but are not limited
   to, enabled links and controls. This allows the user to jump between
   elements without having to navigate through intervening content such
   as blocks of text. Efficient keyboard navigation is especially...

   <greg> ...important for people who cannot easily use a mouse.

   <jallan> comment - important or structural elements are not defined

   <greg> Examples:

   <greg> The user can press the Tab key to move the focus to the next
   link or control in the page, or press Shift+Tab to move in the
   reverse order.

   <jallan> ...may be many other elements (divs, class), roles, that
   user wants to navigate by

   <greg> Related Resources:

   <greg> See 4.1.4 for discussion of letting the user configure the
   list of important elements to suit their task.

   <jallan> issue: definition of important or structural elements are
   vague, rewrite

   <trackbot> Created ISSUE-56 - Definition of important or structural
   elements are vague, rewrite ; please complete additional details at
   [41]http://www.w3.org/WAI/UA/tracker/issues/56/edit .

     [41] http://www.w3.org/WAI/UA/tracker/issues/56/edit

   <jallan> issue: create low priority search - regular expressions,
   word forms, colors, text attribute - bold etc.

   <trackbot> Created ISSUE-57 - Create low priority search - regular
   expressions, word forms, colors, text attribute - bold etc. ; please
   complete additional details at
   [42]http://www.w3.org/WAI/UA/tracker/issues/57/edit .

     [42] http://www.w3.org/WAI/UA/tracker/issues/57/edit

   <jallan> issue: searching from base UA through embedded UAs (time
   based object, svg, etc). how is user to know difference between
   natively rendered video (html5) and embedded video (quicktime).
   should the base UA query the embedded UA for its search results.

   <trackbot> Created ISSUE-58 - Searching from base UA through
   embedded UAs (time based object, svg, etc). how is user to know
   difference between natively rendered video (html5) and embedded
   video (quicktime). should the base UA query the embedded UA for its
   search results. ; please complete additional details at
   [43]http://www.w3.org/WAI/UA/tracker/issues/58/edit .

     [43] http://www.w3.org/WAI/UA/tracker/issues/58/edit

   <jallan> GL: change title of 4.7.1 to Navigate filtered structure
   elements

   <jallan> ...what you you want to navigate between.

   <jallan> GL: burning issues

Summary of Action Items

   [NEW] ACTION: Jeanne to renumber 4.1.12 so it is closer to 4.1.5.
   These are the UI and content discovery items for hotkeys. [recorded
   in [44]http://www.w3.org/2009/11/05-ua-minutes.html#action01]

   [End of minutes]


-- 
Jonnie Appleseed
with his
Hands-On Technolog(eye)s
reducing technology's disabilities
one byte at a time
Received on Friday, 6 November 2009 12:56:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:38 UTC