W3C home > Mailing lists > Public > wai-xtech@w3.org > November 2008

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

From: David Poehlman <david.poehlman@handsontechnologeyes.com>
Date: Tue, 11 Nov 2008 08:57:28 -0500
Message-ID: <B8F2D1219E48485E8E7E049FBF7137A3@HANDS>
To: "Schnabel, Stefan" <stefan.schnabel@sap.com>, "Cain, Sally" <sally.cain@rnib.org.uk>, "David Bolter" <david.bolter@utoronto.ca>, "James Nurthen" <james.nurthen@oracle.com>
Cc: "Joseph Scheuhammer" <clown@utoronto.ca>, <wai-xtech@w3.org>, "earl johnson" <earlj.biker@gmail.com>

two comments.  there is a player #4 and that is the os.

As for what you can do with the AT, many will not use what is considered an 
advanced function of key pass through.

----- Original Message ----- 
From: "Schnabel, Stefan" <stefan.schnabel@sap.com>
To: "Cain, Sally" <sally.cain@rnib.org.uk>; "David Bolter" 
<david.bolter@utoronto.ca>; "James Nurthen" <james.nurthen@oracle.com>
Cc: "Joseph Scheuhammer" <clown@utoronto.ca>; <wai-xtech@w3.org>; "earl 
johnson" <earlj.biker@gmail.com>
Sent: Tuesday, November 11, 2008 3:20 AM
Subject: RE: [DHTML Style Guide] Tablist: Revision of Tab proposal


that's exactly what our CRM Web Client allows for Shortcuts and Access

But don't forget the User Agents. Their Shortcuts and Access Keys should
be configurable, too.

As I see it, there are 3 different players

1) Application
2) User Agent (functional + navigational keys)
3) Assistive Tech

Chances are that 2) and 3) talk with each other to avoid collisions. But
there may be always some of them.
As a matter of last resort, Jaws for instance offers means to ignore its
own keys for the next key stroke (Ins+Numpad 3 to be pressed before any
application hotkey).

- Stefan

-----Original Message-----
From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On
Behalf Of Cain, Sally
Sent: Montag, 10. November 2008 21:34
To: David Bolter; James Nurthen
Cc: Joseph Scheuhammer; wai-xtech@w3.org; earl johnson
Subject: 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.


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


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 -
Received on Tuesday, 11 November 2008 13:58:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:51:38 UTC