W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2010

Fwd: formats need to make shortcuts recognizable

From: Jeanne Spellman <jeanne@w3.org>
Date: Wed, 25 Aug 2010 11:38:07 -0400
Message-ID: <4C7538DF.9060308@w3.org>
To: UAWG <w3c-wai-ua@w3.org>
This is an old email I ran across concerning the reform of @accesskey. 
It probably has been overtaken by events, but in case it is still useful.

-------- Original Message --------
Subject: formats need to make shortcuts recognizable
Resent-Date: Wed, 17 Dec 2008 14:59:19 +0000
Resent-From: w3c-wai-ua@w3.org
Date: Wed, 17 Dec 2008 09:58:36 -0500
From: Al Gilman <Alfred.S.Gilman@IEEE.org>
To: User Agent Working Group <w3c-wai-ua@w3.org>
CC: w3c-wai-pf@w3.org PF <w3c-wai-pf@w3.org>



This note is to make a record of a conversation that Jim and I had at
TPAC.

He pointed out that UAAG requires user agents to provide necessary
services
to users for shortcuts that they can recognize.

I said "and it's PFWG's job to get the formats to make sure that the UA
can recognize the shortcuts that the format defines."

The most immediate application of this is in the reform of ACCESSKEY in
HTML5.  I have given this an issue-of-record, ISSUE-85 in our tracker
which
will now be linked to this bit of coordination.

http://www.w3.org/WAI/PF/Group/track/issues/85

Al

PS:  Where the shortcut functionality is created by scripting, and
not by
using a defined format feature, the format can't guarantee the browser
recognizes the shortcut for a shortcut.  In this case, the active
content has to
itself meet "software accessibility" requirements comparable to the
requirements that
UAAG places on the browser when the browser implements shortcut
features in a format.

http://lists.w3.org/Archives/Public/w3c-wai-ua/2008OctDec/0078.html
Received on Wednesday, 25 August 2010 15:38:19 UTC

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