RE: CA02 - related 3.1

I wonder if implementing aria-live as per its spec isn't just covered by:
http://jspellman.github.io/UAAG/UAAG20/#sc_512

(5.1.2 Implement Accessibility Features of Content Specifications: Implement the accessibility features of content specifications. Accessibility features are those that are either (Level A):
Identified as such in the content specifications or
Allow authors to satisfy a requirement of WCAG 2.0
Note 1: If a conformance claim is filed, cite the implemented specifications in the conformance claim.
Note 2: When a rendering requirement of another specification contradicts a requirement of UAAG 2.0, the user agent may disregard the rendering requirement of the other specification and still satisfy this guideline.)

...though I know this is a catch-all.

-Jan


(MR) JAN RICHARDS
PROJECT MANAGER
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
OCAD UNIVERSITY

T 416 977 6000 x3957
F 416 977 9844
E jrichards@ocadu.ca<mailto:jrichards@ocadu.ca?Subject=Re%3A%20AUWG%20Teleconference%20for%2017%20March%202014%20%28Boston%20time%20has%20changed%20-%20%20please%20re-check%20time%29&In-Reply-To=%3C0B1EB1C972BCB740B522ACBCD5F48DEB012E4B50AC%40ocadmail-maildb.ocad.ca%3E&References=%3C0B1EB1C972BCB740B522ACBCD5F48DEB012E4B50AC%40ocadmail-maildb.ocad.ca%3E>

________________________________
From: Greg Lowney [gcl-0039@access-research.org]
Sent: July-10-14 3:44 AM
To: Jim Allan; WAI-ua
Subject: Re: CA02 - related 3.1

The reviewer's comment raises a few valid questions about 3.1.1:

1. The first bullet says the user can turn off "Recognized messages that are low priority". Are there any recognized low-priority messages other than those marked with aria-live? Aria-live is used only for content that is being updated or changing, which is already excluded by the third bullet. Thus, if it has the wai-live, it doesn’t matter whether the value says it's low, medium, or high priority. Is there any existing technology that where the first bullet would apply?

2. The second bullet says the user must be able to turn off "Information in the user agent user interface that is being updated or changing". That seems to say that *all* non-modal information and status displays, including errors, need to be optional or replaced by modal displays (message boxes and the like). If a toolbar button switches between enabled and disabled appearances when the focus moves to an element where it’s not applicable, or when the page updates to show or hide playable media, that needs to be optional? How about the enabling and disabling of the Back button? If the scroll button moves as the user scrolls through the document, do they need to be able to hide the scroll bar? Does the user need to be able to prevent the browser’s title bar from changing to reflect changes to the web page’s title?

3. The third bullet says the user can turn off "Rendered content that is being updated or changing". Doesn’t that mean turning off scripts, turning off the ability of scripts to modify the DOM, or turning off screen updates when the DOM changes?

That being said, reviewer seems to have been misled because the phrase "Recognized messages that are low priority" can be taken as including recognized messages that can be *inferred* to have low priority (rather than only recognized messages that have *recognized* low priority). If we keep the clause we should probably change the wording to something like "Recognized low-priority messages (e.g. the aria-live attribute set to 'polite')".

    Greg

-------- Original Message --------
Subject: CA02 - related 3.1
From: Jim Allan <jimallan@tsbvi.edu><mailto:jimallan@tsbvi.edu>
To: WAI-ua <w3c-wai-ua@w3.org><mailto:w3c-wai-ua@w3.org>
Date: 7/8/2014 7:19 AM
Current wording

3.1.1 Reduce Interruptions:
The user can avoid or defer: (Level AA)
a.
Recognized messages that are low priority
b.
Information in the user agent user interface that is being updated or changing
c.
Rendered content that is being updated or changing
-----------------------

CA02: add item and reword
a) Messages and content that are non-essential or low priority for the user
--
​comment: how does UA determine non-essential?​
​ Author provides content. How is UA to determine non-essential content?​

​Propose: not accepted​


b)
​ ​
Messages, features and content that are not part of the core use-cases for the content.
--
​comment: the UA cannot know the use-case for the content. ​
​This is an additional item.
Propose- ​
​not accepted​


c)
​ ​
Information in the user agent user interface that is being updated or changing
​--comment: same as current wording​
​ - no change​


d)
​ ​
Rendered content that is being updated or changing​
--
​comment: same as current wording​
​ - no change​



--
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