RE: [WSG] Access Keys and large sites

2006-07-03 Thread michael.brockington
Patrick,
I'm sure you are aware that the problem with Access Keys is not the
principle, but the potential interference with user agents. With an
Intranet you normally have control over which user agents are in use,
and can therefore ensure that the actual Access Keys that are used do
not interfere. You may still not have a usable set of keys, but at least
things are predictable, and any unwanted effects can be handled
directly. 
In the same way, accessibility in general is always less of an issue on
an Intranet, as you only need to worry about actual problems with your
site/UA combination, not all potential problems with all possible
combinations.

Mike


 -Original Message-
 From: listdad@webstandardsgroup.org 
 [mailto:[EMAIL PROTECTED] On Behalf Of Patrick H. Lauke
 Sent: Friday, June 30, 2006 10:54 PM
 To: wsg@webstandardsgroup.org
 Subject: Re: [WSG] Access Keys and large sites

 And why would an intranet warrant different treatment from 
 any other web 
 content?
 
 P
 -- 
 Patrick H. Lauke


**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



RE: [WSG] Access Keys and large sites

2006-07-03 Thread michael.brockington



I am not a lawyer, but my understanding is that an employer 
must make reasonable adjustments to accommodate specific problems affecting an 
existing or new employee. For an adjustment to be required at that point, one 
must assume that it is not necessary to fix problems that have no effect on an 
employee, or to stretch the point a little, to problems that have not been 
notified.
I am not advocating that web standards be ignored on an 
Intranet, but trying to clarifyPatrick's earlier question. 


Mike

  
  
  From: listdad@webstandardsgroup.org 
  [mailto:[EMAIL PROTECTED] On Behalf Of Matthew 
  PennellSent: Monday, July 03, 2006 12:31 PMTo: 
  wsg@webstandardsgroup.orgSubject: Re: [WSG] Access Keys and large 
  sites
  On 7/3/06, [EMAIL PROTECTED] 
  [EMAIL PROTECTED] 
  wrote:
  
  Patrick,In 
the same way, accessibility in general is always less of an issue onan 
Intranet, as you only need to worry about actual problems with 
yoursite/UA combination, not all potential problems with all 
possiblecombinations.And presumably your 
  company's HR department know that they must avoid hiring anyone with a 
  disability, as they might have trouble using your intranet, yes? 
  **The 
  discussion list for http://webstandardsgroup.org/See 
  http://webstandardsgroup.org/mail/guidelines.cfmfor some hints on posting 
  to the list  getting 
  help**

**The discussion list for  http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help**


RE: [WSG] Access Keys and large sites

2006-06-30 Thread michael.brockington
Well if no-one else is going to say it, then I will have to:
Don't use Access Keys except on an Intranet site.

IF you do a quick Google search for 'Access Keys' and 'Bad'  you should find 
several articles which have researched the number of such keys that do not 
clash with a Browser, OS or AT function. If I remember correctly, there are two 
of them, and I'll give you a tenner myself if you can find either of them on 
your keyboard without looking!

Mike



Cole Kuryakin wrote:
 Hello All -
 
 I'm pretty new to the whole accessibility thing but I'm trying.
 
 The latest question mark that arose in my mind regards to access keys: since
 there's only 10 numeric keys (including 0) what does one do if you're
 building a site that exceeds 10 pages? The one I'm working on now looks like
 it's going to top-out at over 50 pages with some sections containing 2
 different drill-down levels

Food for thought:
http://www.wats.ca/show.php?contentid=32

BTW Firefox in Linux has assigned the numeric keys to the tabs. Pressing 
Alt + 1 takes you to your first tab. Pressing Alt + 2 takes you to the 
second, and so on. Just FYI.

Kat


**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**




**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**
winmail.dat

Re: [WSG] Access Keys and large sites

2006-06-30 Thread Patrick H. Lauke

[EMAIL PROTECTED] wrote:

Well if no-one else is going to say it, then I will have to:
Don't use Access Keys except on an Intranet site.


And why would an intranet warrant different treatment from any other web 
content?


P
--
Patrick H. Lauke
__
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
__
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__


**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**



[WSG] Access Keys and large sites

2006-06-29 Thread Cole Kuryakin
Title: Access Keys and large sites






Hello All 

Im pretty new to the whole accessibility thing but Im trying.

The latest question mark that arose in my mind regards to access keys: since theres only 10 numeric keys (including 0) what does one do if youre building a site that exceeds 10 pages? The one Im working on now looks like its going to top-out at over 50 pages with some sections containing 2 different drill-down levels

No need for anyone to go into a lot of explanation on what to do if theres simply a good link that can be provided that will answer my question.

Appreciate all insight in advance.

Cole



**The discussion list for  http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help**