HS: comments on new Opera UA
technology - Opera Turbo (for Instance) - Speed dial thumb
nails etc
... Resizable search field + spell checker and auto updates.
Lots of addition and svg improvements.
... have comprehensive list of feedback on accessibility in
terms v 10
... Largest Accessibility change is Opera Turbo - better access
if location based or compromised network.
... New accessibility stuff is not in this version but is
upcoming in the next (hopefully).

KP: familiar with mouse-less
browsing in Firefox - numbers all links. if opera did this it
will enable all speech.

GL: Should we cover Mouseless
Browsing and the like in the guidelines.

SH: Is this not included in 4.1.7
Keyboard Navigation: The user can use the keyboard to navigate
from group to group of focusable items and to traverse forwards
and backwards all of the focusable items within each group.
Groups include but are not limited to toolbars, panels, and
user agent extensions. (Level AA)

1. 4.1.9 Override of UI Keyboard Commands

<Greg> #70. (Re 4.1.9) Is
4.1.9 actually Level A?: I ask because elsewhere the success
criteria for a guideline are sorted according to Level, but
here 4.1.9 (Level A) follows 4.1.8 (Level AA). Is this a
temporary artifact that will be fixed when items are
renumbered? Or is 4.1.9 miscategorized as A when it should be
AA? (Priority: 3 Low) (Type: Clarify)

<Greg> #71. (Re 4.1.9) Is
overriding all UI keyboard commands too broad?: I'm concerned
because I'm not sure that any browsers allow the user to
override *all* of the platform's UI keyboard commands" (e.g.
ALT to activate the menu bar, CTRL+O for open, CTRL+A for
select all, Tab for sequential navigation, etc.). Is it
possible that the current wording is unintentionally broad?
(Priority: 1 High)...

<Greg> #73. (Re 4.1.9 **)
Define "override" keyboard shortcut bindings: 4.1.9, 4.1.10 and
4.1.11 require the user be able to "override" keyboard
shortcuts, but don't define the term. 4.1.9 and 4.1.11 refer to
"rebinding" and so requires the user to be able to assign new
shortcuts that replace the default ones, whereas 4.1.10 does
not mention this and so implies that the user only needs to be
able...

<Greg> ...to remove default
shortcuts, but the ability to reassign or assign new shortcut
keys is presumably left optional. For the goal of improved
accessibility there are really three potential features: (a)
the ability to delete existing shortcuts is useful when they
conflict with shortcuts used by assistive technology; (b) the
ability to reassign shortcuts for functions that already have
them...

<Greg> ...accomplishes that
goal PLUS retains the ability of shortcuts to reduce the number
of keystrokes and/or steps required to execute an operation;
(c) the ability to assign new shortcuts to functions that don't
have them by default accomplishes both of those goals PLUS
allows the user to further reduce the number of keystrokes or
steps they have to enter. One way of handling these
diverse...

<Greg> ...choices would be to
make the first option be Level A, the second Level AA, and the
third Level AAA. (Priority: 2 Medium) (Type: Clarify)

<Greg> This still needs to be
addressed.

<Greg> #74. (Re 4.1.9 **)
Normalize "keyboard shortcuts" vs. "keyboard shortcut
bindings": 4.1.9 uses the term "keyboard shortcut binding"
while 4.1.10 uses "keyboard shortcut". I assume they are meant
to refer to the same thing, so the document should standardize
on one phrasing. (Priority: 3 Low) (Type: Clarify)

Proposed: 4.1.9 Override of UI
Keyboard Commands: The user can override any keyboard shortcut
binding for the user agent user interface except for
conventional bindings for the operating environment (e.g., for
access to an open command). The rebinding options must include
single-key and key-plus-modifier keys if available in the
operating environment. This does not prohibit a user agent from
supporting user override of conventional bindings for the
operating pl

5 accept / 3 discuss

GL: not everything address - see
above (especially #71)

JR: Should this be AA? It is P2
in UAAG 1.0.

JS: The last sentence is still
not clear. It took me about 4 times through to understand what
it means. recommend inserting before the sentence beginning
"the rebinding options":

This does not prohibit the user agent from
allowing user override of the conventional bindings.

<scribe> scribe:
Harper_Simon

<scribe> scribeNick:
sharper

JS: Specifics (of keyboard
commands) should be included in the glossary - otherwise gets
very confusing in guidelines.

<trackbot> Created ACTION-194
- Work GL and JS to write a definition of Keyboard Command [on
Greg Lowney - due 2009-06-18].

Guideline 4.5 Configure and Store accessibility
preference settings.

5 accept / 2 discuss / 1 neutral

JR: I'm a bit concerned by 4.5.1.
Because it refers to something everyone does anyway (make
preference setting configurable), I think people might
interpret as requiring everything that impacts accessibility to
be controlled by a preference setting.

Portable Profiles: Sets of preferences are
stored such that they can be transferred between different
installations of the same user agent. (Level AA)

KP-discuss: Accessible profiles
sometimes take quite a bit of time to set. Making an accessible
profile portable means you can access multiple computers more
easily and more easily work on other people's computers. This
is a basic in some jobs. Ease of access to a given computer is
a showstopper in many situations.

<Greg> The ISO version is
Level 3 (AAA)

JA-Discuss: current rewrite of
this - see #2 (4.5.4) above has this as AAA.

When this was originally written, the concept
was - user creates a mysettings.profile in UAx, that file can
be used on other UAx on other computers. But would not be
required to work with UAy or any other UA.

The comment above, seems to indicate that the
profile would/might work in all UA cross platform. HTML, CSS,
and JS can hardly do that now. I agree that cross
browser/platform profile usage is beyond our charter. Perhaps
we need some language to limit the profile to individual UAs
and perhaps on a given platform.

<proposed>

4.5.4 Accessibility Portable Profiles: Sets of
preferences are stored as separate files (allowing them to be
transmitted electronically). Note: These profiles may be usable
only with the brand(?) of user agent that created it (Level
AAA)

JR-Discuss: I'm a bit concerned
by 4.5.1. Because it refers to something everyone does anyway
(make preference setting configurable), I think people might
interpret as requiring everything that impacts accessibility to
be controlled by a preference setting.