W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2011

Minutes: UAWG 1 Sept 2011

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 1 Sep 2011 13:47:51 -0500
Message-ID: <CA+=z1WkB6mcV48P8zreWPUpqCwqcY7g=jn11WnpTz6vHA+-gvw@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
from: http://www.w3.org/2011/09/01-ua-minutes.html
User Agent Accessibility Guidelines Working Group Teleconference
01 Sep 2011

See also: IRC log http://www.w3.org/2011/09/01-ua-irc
Attendees

Present
    JimA, KellyF, GregL, KimP, SimonH
Regrets
    Jan, Mark
Chair
    JimAllan, KellyFord
Scribe
    jallan

Contents

    Topics
        Register for TPAC http://www.w3.org/2011/11/TPAC/
        Resolve configure important items, UA determine relationships.
        Review/Resolve outstanding issues
        proposed Summary for 2.1
        Proposed Summary for 2.2
        summary 4.2 Input focus correctly transitions between nested
user agents (4.2.1), the user can determine input focus at any time
(4.2.2) and input focus never gets stuck in any nested user agent
(4.2.3).
        2.7.5 summary
        summary for GL 3.1 -3.4
        proposed Summary for 2.1
        Proposed Summary for 2.2
        Simon's proposal for 2.5
    Summary of Action Items

Summary of Action Items
[NEW] ACTION: Greg to write new SC 3.2.x about spell checking
[recorded in http://www.w3.org/2011/09/01-ua-minutes.html#action03]
[NEW] ACTION: jallan to revisit Nested User Agents 2.1.2, 2.1.3,
.2.2.1, 2.2.2, -- these should be cross referenced with gl 4.2 <--
should also be reviewed. [recorded in
http://www.w3.org/2011/09/01-ua-minutes.html#action02]
[NEW] ACTION: revisit Nested User Agents 2.1.2, 2.1.3, .2.2.1, 2.2.2,
-- these should be cross referenced with gl 4.2 <-- should also be
reviewed. [recorded in
http://www.w3.org/2011/09/01-ua-minutes.html#action01]

NOTE: ALL EXCEPT SUMMARY FOR 2.2 AND 2.5 WERE PUT INTO THE WORKING DRAFT.

<trackbot> Date: 01 September 2011

<jeanne> http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JulSep/0010.html

<kford> Sorry I keep trying to connect with the phone but it doesn't
seem to be working.
Register for TPAC http://www.w3.org/2011/11/TPAC/

<jeanne> TPAC will be an unconference format. See the list of ideas
for sessions <- http://www.w3.org/wiki/TPAC2011/SessionIdeas

Dates for UAWG meeting is Nov 3 & 4

registration closes 14 october and registration fee goes up
Resolve configure important items, UA determine relationships.

<jeanne> JS: I don't think we have enough people for a viable
consensus. Postpone until next week.
Review/Resolve outstanding issues

<jeanne> JA: Principle 1 is complete

<jeanne> ... Principle 5 is complete

<jeanne> ... need a summary for 4.2

<jeanne> ... 4.2.1 and 4.2.2need intent. (already have examples)

<jeanne> [group breaks for writing]

http://www.w3.org/WAI/UA/2011/ED-UAAG20-20110819

<kford> Possible Summary for 2.2:

<kford> That's 4.2.

<kford> Input focus correctly transitions between nested user agents
(4.2.1), the user can determine input focus at any time (4.2.2) and
input focus never gets stuck in any nested user agent (4.2.3).

<kford> Possible summaries for 4.2 and 2.7:

<kford> 4.2

<kford> Input focus correctly transitions between nested user agents
(4.2.1), the user can determine input focus at any time (4.2.2) and
input focus never gets stuck in any nested user agent (4.2.3).

<kford> 2.7

<kford> The user can customize user agent settings related to
accessibility (2.7.1) with settings changes being saved between
sessions (2.7.2) and restore settings to default values (2.7.3). Users
can have multiple sets of preferences (2.7.4), have related settings
restored to default as a group (2.7.5) and adjust preferences outside
the user agent main user interface (2.7.6). Users can also...

<kford> ...transfer settings between devices (2.7.7) and are offered a
wizard to assist in user customization (2.7.8).

possible summaries for 3.1-3.4

3.1 Users can turn off non-essential messaes from the author or user-agent.

3.2 Users can choose to confirm form submissions.

3.3 User documentation is available in an accessible format (3.3.1),
it includes accessbilbity features (3.3.2), delineates differences
between versions (3.3.3), provides a centralized views of the browser
meets UAAG2.0 (3.3.4), and is available as context sensitive help in
the UA (3.3.5).

3.4 Moving the focus allow presentation of information (e.g. tooltips)
but does not cause any other action (3.4.2). Users can prevent
non-requested focus changes (3.4.1).
proposed Summary for 2.1

<jeanne> Guideline 2.1 - Ensure full keyboard access.

<jeanne> Users have many ways to input information into a computer or
device, including mouse, keyboard, gesture, and speech. The keyboard
paradigm is the most universal interface for text input - even devices
that do have a keyboard (like mobile phones) support a software
interface for them. All functions can be operated only using a
keyboard (2.1.1), the focus can be moved by the keyboard (2.1.2,
2.1.3),

<jeanne> important or commonly used features of the web page or
application should have shortcut keys for direct navigation (2.1.8).
and the user can override keyboard shortcuts and user interface
controls (2.1.4). Users should have a mechanism to escape keyboard
traps such as embedded objects that do not return focus to the main
web page (2.1.5). Users can set a preference that selecting an item in
a

<jeanne> dropdown list or menu, does not activate that item or move to
that new web page (2.1.6). Text entry should use the standard keys for
that platform (2.1.7).
Proposed Summary for 2.2

<jeanne> Guideline 2.2 - Provide sequential navigation

<jeanne> Users need to be able to move through all the enabled content
in the web page in a logical sequential fashion (2.2.1 and 2.2.2).
Unless the author specifies a different navigation order, the default
is the document order (2.2.3). Users can prevent or request
notification when wrapping to the start of the page, to prevent
unwanted repetition (2.2.4).

<KimPatch> 2.1.2 Keyboard Focus (former 1.9.1):

<KimPatch> Every viewport has an active or inactive keyboard focus at
all times. (Level A)

<KimPatch> 2.1.3 Viewport Navigation (former 1.9.2 & 1.9.4):

<KimPatch> The user can move the active keyboard focus to any
viewport. (Level A)

<KimPatch> 2.2.1 Sequential Navigation Between Elements [replaces
1.9.8 Bi-Directional and 2.1.8 Keyboard Navigation]

<KimPatch> The user can move the keyboard focus backwards and forwards
through all recognized enabled elements in the current viewport.
(Level A)

<KimPatch> 2.2.2 Sequential Navigation Between Viewports [NEW]:

<KimPatch> The user can move the keyboard focus backwards and forwards
between viewports, without having to sequentially navigate all the
elements in a viewport. (Level A)

<scribe> ACTION: revisit Nested User Agents 2.1.2, 2.1.3, .2.2.1,
2.2.2, -- these should be cross referenced with gl 4.2 <-- should also
be reviewed. [recorded in
http://www.w3.org/2011/09/01-ua-minutes.html#action01]

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

<scribe> ACTION: jallan to revisit Nested User Agents 2.1.2, 2.1.3,
.2.2.1, 2.2.2, -- these should be cross referenced with gl 4.2 <--
should also be reviewed. [recorded in
http://www.w3.org/2011/09/01-ua-minutes.html#action02]

<trackbot> Created ACTION-610 - Revisit Nested User Agents 2.1.2,
2.1.3, .2.2.1, 2.2.2, -- these should be cross referenced with gl 4.2
<-- should also be reviewed. [on Jim Allan - due 2011-09-08].

<sharper_> Users can discover the keys which facilitate direct
navigation and activation (2.5.1), view their location in the
structural hierarchy (2.5.3), along with the relationships within that
hierarchy (2.5.5), and specify the elements (2.5.7+1.10.3) important
to building and navigate different hierarchical views (1.10.2).
summary 4.2 Input focus correctly transitions between nested user
agents (4.2.1), the user can determine input focus at any time (4.2.2)
and input focus never gets stuck in any nested user agent (4.2.3).

summary 4.2 Input focus correctly transitions between nested user
agents (4.2.1), the user can retrieve input focus at any time (4.2.2)
and input focus never gets stuck in any nested user agent (4.2.3).
2.7.5 summary

The user can customize user agent settings related to accessibility
(2.7.1) with settings changes being saved between sessions (2.7.2) and
restore settings to default values (2.7.3). Users can have multiple
sets of preferences (2.7.4), have related settings restored to default
as a group (2.7.5) and adjust preferences outside the user agent main
user interface (2.7.6). Users can also...

scribe: transfer settings between devices (2.7.7) and are offered a
wizard to assist in user customization (2.7.8).

Users can customize user agent settings related to accessibility
(2.7.1) with settings being saved between sessions (2.7.2) and restore
settings to default values (2.7.3). Users can have multiple sets of
preferences (2.7.4), have related settings restored to default as a
group (2.7.5) and adjust preferences outside the user agent main user
interface (2.7.6). Users can also transfer settings...

scribe: between devices (2.7.7) and are offered a wizard to assist in
user customization (2.7.8).
summary for GL 3.1 -3.4

3.1 Users can turn off non-essential messaes from the author or user-agent.

3.2 Users can choose to confirm form submissions.

3.3 User documentation is available in an accessible format (3.3.1),
it includes accessbilbity features (3.3.2), delineates differences
between versions (3.3.3), provides a centralized views of the browser
meets UAAG2.0 (3.3.4), and is available as context sensitive help in
the UA (3.3.5).

3.4 Moving the focus allow presentation of information (e.g. tooltips)
but does not cause any other action (3.4.2). Users can prevent
non-requested focus changes (3.4.1).

gl: what about an SC requiring spell checking for folks with reading
or writing disabilities.

all agree.

<scribe> ACTION: Greg to write new SC 3.2.x about spell checking
[recorded in http://www.w3.org/2011/09/01-ua-minutes.html#action03]

<trackbot> Created ACTION-611 - Write new SC 3.2.x about spell
checking [on Greg Lowney - due 2011-09-08].

3.3 User documentation is available in an accessible format (3.3.1),
it includes accessibility features (3.3.2), delineates differences
between versions (3.3.3), provides a centralized views of conformance
UAAG2.0 (3.3.4), and is available as context sensitive help in the UA
(3.3.5).
proposed Summary for 2.1

Users have many ways to input information into a computer or device,
including mouse, keyboard, gesture, and speech. The keyboard paradigm
is the most universal interface for text input - even devices that do
have a keyboard (like mobile phones) support a software interface for
them. All functions can be operated only using a keyboard (2.1.1), the
focus can be moved by the keyboard (2.1.2, 2.1.3),

important or commonly used features of the web page or application
should have shortcut keys for direct navigation (2.1.8). and the user
can override keyboard shortcuts and user interface controls (2.1.4).
Users should have a mechanism to escape keyboard traps such as
embedded objects that do not return focus to the main web page
(2.1.5). Users can set a preference that selecting an item in a

dropdown list or menu, does not activate that item or move to that new
web page (2.1.6). Text entry should use the standard keys for that
platform (2.1.7).
Proposed Summary for 2.2

Guideline 2.2 - Provide sequential navigation

Users need to be able to move through all the enabled content in the
web page in a logical sequential fashion (2.2.1 and 2.2.2). Unless the
author specifies a different navigation order, the default is the
document order (2.2.3). Users can prevent or request notification when
wrapping to the start of the page, to prevent unwanted repetition
(2.2.4).

<scribe> scribe: jallan

kf: first couple of sentences read more like an intent.

JS: move first 2 sentences to intent of 2.1.1

<Greg> "important or commonly used features should have shortcut keys
for direct navigation (2.1.8)"

<KimPatch> Users can operate all functions (2.1.1), and can move focus
(2.1.2, 2.1.3) using just the keyboard.

gl: but need to distinguish between 212 and 213

Users can override author keyboard shortcuts and user interface controls (2.1.4)

can override keyboard shortcuts and user interface keyboard controls (2.1.4)

Users can escape keyboard traps such as embedded objects that do not
return focus to the main web page (2.1.5).

<Greg> "Users can override keyboard shortcuts in content and the user
agent's user interface (2.1.4)"

<KimPatch> Users can operate all functions (2.1.1), and move focus
(2.1.2, 2.1.3) using just the keyboard. Users can activate important
or common features with shortcut keys, (2.1.8), override keyboard
shortcuts and user interface controls (2.1.4), escape keyboard traps
(2.1.5), specify that selecting an item in a dropdown list or menuoes
not activate that item or move to that new web page (2.1.6),...

<KimPatch> ...and use standard keys for that platform (2.1.7).

<sharper_> Users can discover the keys which facilitate direct
navigation and activation (2.5.1), view their current location in the
structural hierarchy (2.5.3) as well as the relationships within that
hierarchy (2.5.5), and specify the elements (2.5.7+1.10.3) important
to building and navigating different hierarchical views (1.10.2).
Simon's proposal for 2.5

<KimPatch> Users can operate all functions (2.1.1), and move focus
(2.1.2, 2.1.3) using just the keyboard. Users can activate important
or common features with shortcut keys, (2.1.8), override content and
interface keyboard shortcuts (2.1.4), escape keyboard traps (2.1.5),
specify that selecting an item in a dropdown list or menuoes not
activate that item or move to that new web page (2.1.6) and use...

<KimPatch> ...standard keys for that platform (2.1.7).

need lots of discussion about 1.10.2 1.10.3 and 2.5.7 and 2.5.4

<KimPatch> Users can operate all functions (2.1.1) and move focus
(2.1.2, 2.1.3) using just the keyboard. Users can activate important
or common features with shortcut keys (2.1.8), override content and
interface keyboard shortcuts (2.1.4), escape keyboard traps (2.1.5),
specify that selecting an item in a dropdown list or menu doesn't
activate or move item to that new web page (2.1.6). User can use...

<KimPatch> ...standard keys for text entry (2.1.7).

<Greg> "override keyboard shortcuts in content and user interface (2.1.4)"

<Greg> (Don't want it to read like "override content and override
interface keyboard shortcuts.)


[End of minutes]

-- 
Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 1 September 2011 18:48:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 1 September 2011 18:48:22 GMT