XHTML 2 Draft Recommendation:Removal of the KEY attribute from the specification

To whom it concerns,

I work as a web accessibility consultant for the National Council For 
The Blind of Ireland. We audit websites and other ICT systems for 
accessibility and involve a wide range of users with disabilities, as 
well as older people, in our user testing and development processes.

I have read John Foliot's of WATS.ca very informative comment to you at

http://www.wats.ca/articles/xhtmlroleaccessmodulestillflawed/80

and I wish to add that I also have concerns regarding the addition of 
the *@key* attribute in the XHTML 2 Specification. In our experience the 
ACCESSKEY attribute is in itself flawed, for many reasons. It is prone 
to create conflicts with User Agents, as well as the lack of 
international standardisation for its implementation. In our experience, 
it practically does not provide any real utility to the end user. If web 
content is marked up well, users can live quite happily without it.

We do no recommend content authors and web developers use the ACCESSKEY 
attribute at all.

Therefore with regards to the XHTML 2 draft specification, I am 
concerned about the suggested inclusion of the *@key* attribute could 
allow the same flawed model of behavior, as set by ACCESSKEY, to continue.

I trust that you will please bear of these concerns in mind when 
reviewing your draft of the XHTML 2 specifications.

Sincerely

Joshue O Connor

Web Accessibility Consultant

***Centre for Inclusive Technology (CFIT)* * *
National Council for the Blind of Ireland

CFIT Website:www.cfit.ie
joshue.oconnor@cfit.ie +353 1 8821915

Received on Friday, 18 November 2005 12:57:40 UTC