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

RE: UAAG techniques for checkpoints 1 and 2 - comments

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 15 Jun 2006 13:05:06 -0500
To: Catherine Laws <claws@us.ibm.com>, WAU-ua <w3c-wai-ua@w3.org>
Message-id: <HDEAKIPKOHBCMDILOOPNGEKCGCAB.jimallan@tsbvi.edu>

Cathy Laws wrote:

> Here are a couple of comments about some of the techniques for UAAG
> Checkpoints 1 and 2:
> Under 1.2 Activate event handlers, we reference DOM Level 2 but not DOM
> Level 3, which now has descriptions for text events and keyboard
> events. We
> even have a reference about DOM Level 2 not having a key event, which we
> need to replace with a DOM Level 3 reference.

I agree with the DOM 3 references.
Should we reference other APIs, such as accessibility APIs??
> Under 1.3 Provide text messages, we need to add a technique about allowing
> non-essential alerts and text messages to be optional (turned off by the
> user if desired).

sounds interesting. What is a non-essential alert? How is the UA to
determine what is essential?
Many UA are including icons in the status bar to indicate security, etc.
Others include icons in the address bar that indicate (visually) the
presence of an RSS feed. I have not a screen reader announce the icon or its

I think a non-visual user should have information about these content and
feature indicators.

> Under 2.1 Render content according to the spec, we need to expand the
> Example 2 technique about dynamic content changes. Users need to have an
> option to know when content has changed and where the changes are in
> additional to having access to the changes when they happen to navigate to
> the content that has changed.

Right, this falls into the accessibility issues with AJAX

Received on Thursday, 15 June 2006 18:11:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:34 UTC