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

minutes: UAWG Telecon 14 June 2012

From: Greg Lowney <gcl-0039@access-research.org>
Date: Thu, 14 Jun 2012 11:35:58 -0800
Message-ID: <4FDA3D1E.7040202@access-research.org>
To: WAI-UA list <w3c-wai-ua@w3.org>
 From http://www.w3.org/2012/06/14-ua-minutes.html

User Agent Accessibility Guidelines Working Group Teleconference
14 Jun 2012

See also: IRC log
Attendees

Present
     Jeanne, Greg_Lowney, Jan, kford, Kim_Patch, sharper
Regrets
     Jim
Chair
     SV_MEETING_CHAIR
Scribe
     Greg

Contents

     Topics
         Action-737 Rewording UAAG2 5.1.3 (was 5.3.2) Implement
         Changes to 2.8 Provide toolbar configuration
         Action-737 Rewording UAAG2 5.1.3 (was 5.3.2) Implement
         Changes to 2.8 Provide toolbar configuration
         Changes to UAAG2 2.4.5 Advanced Find
         IER for 1.8.6: Zoom
     Summary of Action Items

<trackbot> Date: 14 June 2012

<kford> Accessibility Features of platform

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0103.html

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0105.html

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0104.html

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0099.html

<kford> [SC changed IER no longer matches SC]

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0082.html

<kford> [need to complete this discussion be Jan and Greg, and update the document]

<kford> Adding links and full agenda. Will not change original entries.

<kford> agenda Action-737 Rewording UAAG2 5.1.3 (was 5.3.2) Implement

<kford> Accessibility Features of platform

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0103.html

<kford> agenda Changes to 2.8 Provide toolbar configuration

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0105.html

<kford> agenda Changes to UAAG2 2.4.5 Advanced Find

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0104.html

<kford> agenda IER for 1.8.6: Zoom

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0099.html

<kford> agenda action-733 definition of shortcut

<kford> Agenda Action-725 - Write IER for "1.2.2 Repair Missing Structure"

<kford> [SC changed IER no longer matches SC]

<kford> Agenda Action-729 Definition of Style Sheet

<kford> http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0082.html

<kford> [need to complete this discussion be Jan and Greg, and update the document]
Action-737 Rewording UAAG2 5.1.3 (was 5.3.2) Implement

<kford> Link: http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0103.html

Existing wording:

5.1.3 Implement Accessibility Features of platform: Implement and cite in the conformance claim the accessibility features of platform technology specifications. Accessibility features are those that are either (Level A) :

identified as such in the specification or

allow authors to satisfy a requirement of WCAG

Jan's proposed new wording:

Accessibility Guidelines: If the user agent contains non-web-based user interfaces, then those non-web-based user interfaces follow user interface accessibility guidelines for the platform. (Level A)

Intent:

The intent of this success criterion is to ensure that user agent user interfaces that are not web applications are more accessible to authors with disabilities. Existing platform accessibility guidelines are referenced because accessibility guidelines already exist for many platforms and this wording allows developers the flexibility to conform with accessibility legislation in their markets.

Note: Developers should see the documents listed in the "Related Resources for Success Criterion A.1.2.1" section. Unless special circumstances exist (e.g., a document has been superseded, the platform has undergone major architectural changes), the listed resources should be assumed to be relevant to the platforms listed.

<Jan> A.1.2.1 Accessibility Guidelines: If the authoring tool contains non-web-based user interfaces, then those non-web-based user interfaces follow user interface accessibility guidelines for the platform. (Level A)

<Jan> Note: The (optional) explanation of conformance claim results should record the user interface accessibility guidelines that were followed.

Greg: We can cross reference the UAAG20 SC about documenting accessibility features.

<kford> Accessibility Guidelines: For those portions of the user agent interrface that are non web-based,then those non-web-based user interfaces follow user interface accessibility

<kford> guidelines for the platform. (Level A)

<Jan> A.1.2.2 Platform Accessibility Services: If the authoring tool contains non-web-based user interfaces, then those non-web-based user interfaces implement communication with platform accessibility services. (Level A)

<Jan> Note: The (optional) explanation of conformance claim results should record the platform accessibility service(s) that were implemented.

<Jan> Ignore that last one (A.1.2.2)

Kelly suggested changing "If the user agent contains non-web-based user interfaces" to "For those portions of the user agent interrface that are non web-based".

<Jan> Note: The (optional) explanation of conformance claim results should record the user interface accessibility guidelines that were followed.

<KimPatch> Accessibility Guidelines: Non web-based portions of the user agent interrface should follow user interface accessibility

<kford> So the SC text is as follows:

<kford> Accessibility Guidelines: For those portions of the user agent interrface that are non-web-based, then those non-web-based user interfaces follow user interface accessibility

<kford> guidelines for the platform. (Level A)

<Jan> Accessibility Guidelines: If the user agent contains non-web-based user interfaces, then those user interfaces follow user interface accessibility guidelines for the platform. (Level A)

Could drop the second "user interface".

Resolved: accepting Jan's proposal almost immediately above.

<kford> Close Action-737

<trackbot> ACTION-737 Present 3.3.2 to list and bring up at next meeting closed
Changes to 2.8 Provide toolbar configuration
Action-737 Rewording UAAG2 5.1.3 (was 5.3.2) Implement

Greg: Do we need to merge the existing UAAG and ATAG intent and examples?

Jeanne proposes incorporating Jan's ATAG Intent paragraph as the new 1st paragraph before continuing into our existing Intent paragraphs.

Greg: Our existing third paragraph is about documenting the features, which we have dropped here.

Jan: Would just take 1st paragraph of existing Intent, along with the new Intent paragraph from ATAG.

4.1.1 requires the UA to support a platform accessibility architecture, and presumably 3.3.2 Document Accessibility Features would require that support be documented.

Thus we don't need to address it in 5.1.3, except perhaps cross-reference.

<Jan> JR: Suggests replacing "4.1.1 Platform Accessibility Architecture: The user agent supports a platform accessibility architecture relevant to the operating environment. (Level A)" with "A.1.2.2 Platform Accessibility Services: If the authoring tool contains non-web-based user interfaces, then those non-web-based user interfaces implement communication with platform accessibility services....

<Jan> ...(Level A) Note: The (optional) explanation of conformance claim results should record the platform accessibility service(s) that were implemented."

Jan: Suggests replacing current wording of 4.1.1 Platform Accessibility Architecture with the wording from ATAG that acknowledges only non-web-based UI supports platform accessibility architecture; web-based UI supports WCAG instead.

Greg: Some terminology differences between ATAG and UAAG, e.g. services vs. architecture.

Jan: ATAG changed "Platform Accessibility Architecture" to "Platform Accessibility Services" to harmonize with the new 508 draft.

Greg: I have no problem adopting that term, although it may change again.

<Jan> Link to 508 refresh draft text: http://www.access-board.gov/sec508/refresh/draft-rule.htm#_Toc310327561

Greg: ISO 9241-171 uses the term "accessibility services" as in 8.5.3 "Software that provides user-interface elements shall use the accessibility services provided by the platform to

cooperate with assistive technologies."

Greg: I actually like the ISO wording. Oh, well.

<kford> ACTION: JS to replace platform accessibility language to updated as platform accessibility services thorughout document. [recorded in http://www.w3.org/2012/06/14-ua-minutes.html#action01]

<trackbot> Created ACTION-739 - Replace platform accessibility language to updated as platform accessibility services thorughout document. [on Jeanne F Spellman - due 2012-06-21].

Jan will email to the list his proposal for replacing 4.1.1 Platform Accessibility Architecture with wording based on ATAG.
Changes to 2.8 Provide toolbar configuration

<kford> Link: http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0105.html

Existing:

2.8.1 Configure Position: The user can add, remove, and reorder any toolbars and similar containers, and the items within them. (Level AA)

2.8.2 Restore Default Toolbars: The user can restore the default toolbar, panel, or inspector configuration. (Level AAA)

Proposed:

2.8.1 Configure Toolbars: The user can add, remove, reorder, show, and hide any _toolbars and similar containers_, and the items within them. (Level AA)

2.8.2 Reset Toolbar Configuration: The user can restore all _toolbars and similar containers_ to their default configuration. (Level AAA)

Glossary entry for _Toolbars and similar containers_:

A collection of commonly used controls presented in a region that can be configured or navigated separately from other regions. Such containers may be docked or free-floating, permanent or transient, integral to the application or add-ons. Variations are often called toolbars, palettes,

panels, or inspectors.

Jan: The SC has been around for many years, but difficulty differentiating toolbars from other containers, and it would be asking too much to expect all of them to be configurable.
... ATAG dropped this because they could not resolve this point.

Simon: Might toolbars be identified by reliance on graphics and have horizontal layout?

Kim: Making UI flexible creates potential workarounds, such as her product has taken advantage of to optimize user experience.

Jan: Agreed it's important for access, but difficulty in writing it so it can be testable.
... Wouldn't want to fail something that had a wonderfully configurable toolbar at the top, but the status bar isn't configurable.

Kim: Hiding is particularly important e.g. for people who are distractable.

Greg: Worried about panels, panes, and window regions that aren't really toolbar-like. How would they be distinguished for testing purposes?

Kim: Transient things like the Ctrl+I pop-up in Internet Explorer is less of a problem than persistent UI elements.

Jan: Maybe we want them to have a toolbar when there's functionality not available on the first layer, allowing users to expose shortcuts to things normally hidden or more difficult to reach.

Kim: That's good for adding shortcuts, but also want to be able to hide the ones that are there by default.

ISO 9241-171 has two relevant guidelines:

8.4.2 Optimize the number of steps required for any task

Software should be designed to optimize the number of steps that the user has to perform for any given task.

8.3.6 Enable persistent display: When users can activate a menu, control, or other user-interface element to display additional information or controls, software should allow that information or control to persist while the user engages in other tasks, until the user chooses to dismiss it

[44] , if it is appropriate to the task.

Those are both "Should" guidelines, meaning recommended but not required, equivalent of our Level AA.

Jan will think about this offline.

Greg: We could reduce to AAA if the only other option is dropping it altogether.
... As in, making everything configurable is a noble, lofty goal, even if not usually feasible.
Changes to UAAG2 2.4.5 Advanced Find

http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0104.html

<kford> Link: http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0104.html

It all looks pretty good. Only minor concern is the phrase "known location"; usually they're not using text search to go to a known location (e.g. particular page or heading), but to find a desired occurrence of a phrase or string.

<sharper> 'even if it may not be visible rendered' -> even if it may not be visibly rendered

<sharper> "ensure that find functionality allows" -> 'ensure that 'find' functionality allows' as find is being used as a noun in this case.

Greg: Interestingly, there are other advanced search options which are equally or nearly as useful, such as turning on or off searching for word variants.
... But they're not crucial.

Intent with Simon's edits:

Authors frequently provide alternative content to meet web content accessibility guidelines, which users with disabilities will experience as part of the content. The purpose of this success criteria is to ensure that "find" functionality allows users to locate this content, even if it may not be visibly rendered.

Or: Authors frequently provide alternative content to meet web content accessibility guidelines, which users with disabilities will experience as part of the content. The purpose of this success criteria is to ensure that text search allows users to locate this content, even if it may not be visibly rendered.

(That's using "text search" instead of "'Find' functionality".)

Resolved: adopt Jan's wording in the email, replacing the Intent paragraph with the one immediately above.
IER for 1.8.6: Zoom

Link: http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0099.html

<kford> Link: http://lists.w3.org/Archives/Public/w3c-wai-ua/2012AprJun/0099.html

Existing wording:

1.8.6: Zoom [was 1.8.X]: The user can rescale content within graphical viewports as follows: (Level A)## DONE 26 April

(a) Zoom-in: to at least 500% of the default size; and

(b) Zoom-out: to at least 10% of the default size, or such that the content fits within the height or width of the viewport.

These are already in the latest editor's draft.

<kford> http://www.w3.org/WAI/UA/scribing.html

Summary of Action Items

[NEW] ACTION: JS to replace platform accessibility language to updated as platform accessibility services thorughout document. [recorded in http://www.w3.org/2012/06/14-ua-minutes.html#action01]

[End of minutes]
Received on Thursday, 14 June 2012 18:37:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 14 June 2012 18:37:17 GMT