W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2012

minutes: UAWG Telecon 7 June 2012

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 7 Jun 2012 13:28:43 -0500
Message-ID: <CA+=z1Wn34xr8JCaXzFeFSshJRkrbuirYFVMJS+ZidXYdV3kB4A@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
from http://www.w3.org/2012/06/07-ua-minutes.html
User Agent Accessibility Guidelines Working Group Teleconference
07 Jun 2012

See also: IRC log http://www.w3.org/2012/06/07-ua-irc
Attendees

Present
    jim, jeanne, simon, kelly, jan, greg, kim
Regrets
Chair
    jimallan, kellyford
Scribe
    kford

Contents

    Topics
        Action-719 2.7.8 preference wizard
http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0115.html
        rewrite 3.3.2 describe accessibility features
http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0116.html
    Summary of Action Items

<trackbot> Date: 07 June 2012
Action-719 2.7.8 preference wizard
http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0115.html

<JAllan> jr: ATAG decided to remove the SC because of the testability
issue. propose removal for UAAG

<JAllan> ... suggest Preview of display preferences before committing them

<Jan> 2.7.8 Preferences Wizard: One or more wizards help the user to
configure the accessibility-related user agent preferences. (Level
AAA)

<JAllan> js: -1 reword for preference review before commit

<JAllan> kp: what was the issue

<JAllan> jr: one or more wizards is not testable. if we just limit to
display settings

<Jan> no

<scribe> Scribe: kford

<JAllan> kp: we have ability to save and reset settings.

KP: We also have a save and share which makes this less important.

JA: So Kim, what are you advocating for?

KP: I'm vauge, I'm a don't know.

JA: so you are a ~1?

<JAllan> ~1

<JAllan> kf: fine with it going. wizards are out of vogue.

<JAllan> kp: wizards are too prescriptive and too many steps

JR: ATAG had wizards but we moved to what we ended up removing the
item I described earlier.

KP: If you provide documentation and let them save and share and let
them change outside the user agent, then this is covered.

JA: Summarized discussion.
... In general this seems to be covered.

SH: I understand the reasons for removing but the reasons this was
there were also to help collect a bunch of settings that were
scattered all around.
... I understand this but it can be tedious at times. There was a time
when it took 13 steps to change a font in Internet Explorer took 13
steps.

<JAllan> kf: understands all Si points. would like to remove an SC.

SH: I have many instances where people find this too hard.
... In a practical sense I can understand why we might want to keep this around.

<JAllan> kp: there are good examples.

<JAllan> js: like JR proposal ...approve before comit

Group talking about approve before commit.

<JAllan> jr: do I have to have a commit when I changed the volume or
font size...gets complicated

<JAllan> kp: how easy a wizard to implement.

<JAllan> kf: it is not trivial. depends on what setting you are going
to change and where they come from.

<JAllan> ... but what settings?

<JAllan> kf: slim to no chance that the internet settings will be reworked

<JAllan> jr: provides scenario using IE and wizard for a11y settings
or advanced settings. seems like overkill.

<JAllan> js: what if we stick to just display settings.

<JAllan> jr: why just display

<JAllan> gl: not convinced we need this

<JAllan> kf: either keep as is or kick it out.

<JAllan> gl: if we keep it. then use wording for accessibility
preferences that we have defined elsewhere

<JAllan> ... needed to comply with UAAG20.

<JAllan> jr: sure, but isn't this still overkill

<JAllan> gl: at AAA is it harmful.

<JAllan> jr: at CR will need implementations,

<JAllan> js: that will be hard to do.

<Greg> It does not need to replace normal UI, and could be done as an add-it.

<JAllan> proposal: remove 2.7.8 AAA from document

<Jan> JR: +1 to remove

<sharper> +1

<jeanne> -1 but will go with the group

<JAllan> +1

<Greg> ~1 (I'm fine either way)

+1, it goes away.

<JAllan> kp: ~1 go with group

<JAllan> resolved: remove 2.7.8 from document

Resolved: 2.7.8 gets removed.

<JAllan> close action-719

<trackbot> ACTION-719 Locate a link to Jutta's work on SCORM for 2.7.8
Resources closed
rewrite 3.3.2 describe accessibility features
http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0116.html

JA recaps message contents.

JR and JA go over minor editorial issues.

<JAllan> intent: Users with disabilities that need to use the
accessibility features of

<JAllan> the user agent user interface can easily find descriptions of how to

<JAllan> use and configure the features to work with assistive technology.

<JAllan> These descriptions can be provided in the documentation or user

<JAllan> interface of the user agent or by the underlying platform, if the

<JAllan> feature is in fact a service of that platform.

<JAllan> example 1:

<JAllan> Andromeda has a tremor that makes using the mouse efficiently

<JAllan> difficult. She prefers using keyboard. Andromeda decides to explore

<JAllan> using a new browser. Opening Help, she finds a section entitled

<JAllan> "Browser Features Supporting Accessibility", a vendor provides a

<JAllan> detailed description of user agent features which provide

<JAllan> accessibility. In the Accessibility section she finds an item called

<JAllan> Keyboard Shortcuts which lists all of the functions and commands

<JAllan> available from the keyboard.

<Greg> We should add to Intent that ideally it should be in
documentation easily and freely available to end users, or those who
need it.

<Greg> The example would be slightly easier to read with a minor edit:
"Andromeda has a tremor that makes using the mouse efficiently

<Greg> difficult, so she prefers using keyboard. She decides..."

<JAllan> intent: Users with disabilities that need to use the
accessibility features of

<JAllan> the user agent user interface can easily find descriptions of how to

<JAllan> use and configure the features, including assistive techlogy.

<JAllan> These descriptions can be provided in the documentation or user

<JAllan> interface of the user agent or by the underlying platform, if the

<JAllan> feature is in fact a service of that platform. The
documentation is easily available to the end user.

<Greg> "It is strongly recommended that the documentation be easily
available to end users, and without charge."

<JAllan> intent: Users with disabilities that need to use the
accessibility features of

<JAllan> the user agent user interface can easily find descriptions of how to

<JAllan> use and configure the features, including assistive technology.

<JAllan> These descriptions can be provided in the documentation or user

<JAllan> interface of the user agent or by the underlying platform, if the

<JAllan> feature is in fact a service of that platform. It is strongly
recommended that the documentation be easily available to end users,
and without charge.

Group talking more about SC.

<Greg> In the first two bullet items, the parts after the colons are
pretty redundant to the "handle" before the colon. But not major.

<Greg> We could say that end-user features are in end-user
documentation or the UI, while features only relevant to developers
can be in developer documentation.

<Jan> (d) Not used by authors: The feature is not used directly by
authors (e.g., passing information to a platform accessibility
service).

<JAllan> for UAAG (d) Not used by end users: The feature is not used
directly by end users (e.g., passing information to a platform
accessibility service).

<JAllan> kf: what is the definition of developer, web developer, or AT developer

<Greg> (d) Developer documentation: features only relevant for
developers (e.g. how information is exposed to assistive technology)
may be documented in developer documentation.

<Jan> 4.1.3 Accessible Alternative:

<JAllan> kf: go with previous proposal. then add greg's (d) in 4 and
create new SC

<Greg> also e.g. "how nested user agents determine accessibility
settings of the host".

<JAllan> kf: could create a new SC in programmatiic access. seems the
most practical way to move forward

<JAllan> proposed:

<JAllan> 3.3.2 Describe Accessibility Features:

<JAllan> For each user agent feature that is used to meet UAAG 2.0, at least

<JAllan> one of the following is true: (Level A)

<JAllan> (a) Described in the documentation: Use of the feature is
explained in the user agents's documentation; or

<JAllan> (b) Described in the interface: Use of the feature is
explained in the user agent user interface; or

<JAllan> (c) Platform service: The feature is a service provided by an
underlying platform.

<JAllan> (d) Not used by authors: The feature is not used directly by
authors (e.g., passing information to a platform accessibility
service).

<JAllan> Intent of Success Criterion 3.3.2 :

<JAllan> intent: Users with disabilities that need to use the
accessibility features of the user agent user interface can easily
find descriptions of how to

<JAllan> use and configure the features, including assistive
technology. These descriptions can be provided in the documentation or
user

<JAllan> interface of the user agent or by the underlying platform, if
the feature is in fact a service of that platform. It is strongly
recommended that the documentation be easily available to end users,
and without charge.

<JAllan> Examples of Success Criterion 3.3.2 :

<JAllan> Andromeda has a tremor that makes using the mouse efficiently
difficult, so she prefers using keyboard. She decides Andromeda
decides to explore

<JAllan> using a new browser. Opening Help, she finds a section
entitled "Browser Features Supporting Accessibility", a vendor
provides a

<JAllan> detailed description of user agent features which provide
accessibility. In the Accessibility section she finds an item called

<JAllan> Keyboard Shortcuts which lists all of the functions and
commands available from the keyboard.

<JAllan> A user is exploring the menus of a user agent and finds a
feature named Use My Style Sheet. Activating the feature, the user
quickly

<JAllan> learns that this feature allows custom CSS stylesheets to be
created to help make web content more accessible.

<JAllan> new (d) (d) Not used by end users: The feature is not used
directly by end users (e.g., passing information to a platform
accessibility service).

<Greg> "a vendor provides" to "where the vendor provides"

<JAllan> Andromeda has a tremor that makes using the mouse efficiently
difficult, so she prefers using keyboard. She decides to explore using
a new browser. Opening Help, she finds a section entitled "Browser
Features Supporting Accessibility", where the vendor provides a
detailed description of user agent features which provide
accessibility. In the Accessibility section she finds an item called
Keyboard

<JAllan> Shortcuts which lists all of the functions and commands
available from the keyboard.

<Greg> "Activating the feature, the user quickly" to "Activating the
feature brings up a dialog box that not only allows her to install
such a style sheet, but also explains an overview of the feature."

Group working on another example.

<JAllan> George is exploring the menus of a user agent and finds a
feature named Use My Style Sheet. Activating the feature brings up a
dialog box that not only allows her to install such a style sheet, but
also explains an overview of the feature.

<Greg> "e.g., passing information to a platform accessibility service"
to "e.g. how the user agent passes information to assistive
technology"

<Greg> Summary: Users can have form submissions require confirmation
(3.2.1), go back after navigating (3.2.2), and use spell-checking
facilities (3.2.3).

<Greg> Summary: Users can have form submissions require confirmation
(3.2.1), go back after navigating (3.2.2), and have their text checked
for spelling errors (3.2.3).

Resolved: Summary for 3.2 to be above wording.

<JAllan> proposed:

<JAllan> 3.3.2 Describe Accessibility Features:

<JAllan> For each user agent feature that is used to meet UAAG 2.0, at least

<JAllan> one of the following is true: (Level A)

<JAllan> (a) Described in the documentation: Use of the feature is
explained in the user agents's documentation; or

<JAllan> (b) Described in the interface: Use of the feature is
explained in the user agent user interface; or

<JAllan> (c) Platform service: The feature is a service provided by an
underlying platform.

<JAllan> (d) Not used by end users: The feature is not used directly
by end users (e.g. how the user agent passes information to assistive
technology)

<JAllan> Intent of Success Criterion 3.3.2 :

<JAllan> intent: Users with disabilities that need to use the
accessibility features of the user agent user interface can easily
find descriptions of how to use and configure the features, including
assistive technology. These descriptions can be provided in the
documentation or user interface of the user agent or by the underlying
platform, if the feature is in fact a service of that platform. It
is...

<JAllan> ...strongly recommended that the documentation be easily
available to end users, and without charge.

<JAllan> Examples of Success Criterion 3.3.2 :

<JAllan> Andromeda has a tremor that makes using the mouse efficiently
difficult, so she prefers using keyboard. She decides to explore using
a new browser. Opening Help, she finds a section entitled "Browser
Features Supporting Accessibility", where the vendor provides a
detailed description of user agent features which provide
accessibility. In the Accessibility section she finds an item
called...

<JAllan> ...Keyboard Shortcuts which lists all of the functions and
commands available from the keyboard.

<JAllan> George is exploring the menus of a user agent and finds a
feature named Use My Style Sheet. Activating the feature brings up a
dialog box that not only allows her to install such a style sheet, but
also explains an overview of the feature.

Resolved: Use previous text for wording for 3.3.2

<scribe> ACTION: JS to update document with resolved items from this
week and publish new editor's draft. [recorded in
http://www.w3.org/2012/06/07-ua-minutes.html#action01]

<trackbot> Created ACTION-738 - Update document with resolved items
from this week and publish new editor's draft. [on Jeanne F Spellman -
due 2012-06-14].
Summary of Action Items
[NEW] ACTION: JS to update document with resolved items from this week
and publish new editor's draft. [recorded in
http://www.w3.org/2012/06/07-ua-minutes.html#action01]

[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, 7 June 2012 18:29:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 7 June 2012 18:29:11 GMT