RE: [DHTML Style Guide] Tablist: Revision of Tab proposal

Dear all,

Just a general comment on this thread. I agree with simplification of
keyboard shortcuts, but there is a balance to be found here and it is
*not* easy. 
We need to provide navigation that is accessible, predictable and simple
without clashing with access technology. 

In a desktop application environment I recommend to developers that you
provide all of the above and if there are then clashes with access
technology then the *application* should provide the functionality to be
flexible enough to change the keyboard shortcuts. In a web application
you do not have that same flexibility and the last thing we want is a
user to be constantly changing the keyboard shortcuts in their own
access technology as they just won't use the web application.

Thanks
Sally

Sally Cain
Digital Accessibility Development Officer
Digital Accessibility
RNIB Birmingham
Tel: 0121 665 4226
Email: sally.cain@rnib.org.uk



-- 
DISCLAIMER:

NOTICE: The information contained in this email and any attachments is 
confidential and may be privileged.  If you are not the intended 
recipient you should not use, disclose, distribute or copy any of the 
content of it or of any attachment; you are requested to notify the 
sender immediately of your receipt of the email and then to delete it 
and any attachments from your system.

RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants.  However, it 
cannot accept any responsibility for any  such which are transmitted.
We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email and 
any attachments are those of the author and do not necessarily represent
those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk



This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com

Received on Monday, 10 November 2008 21:01:31 UTC