It's interesting that someone mentioned "nothing in 508 requires support for keyboard navigation".

I was discussing 508 with a co-worker here who had been studying up on it for some time, when he got tired of my questions, he basically told me "the best way to ensure that you are 508 compliant, is to make sure that anything and everything on your website can be done without a mouse (using only the keyboard)".

So now i'm a bit confused. Is mouseless navigation a key component for 508 compliance??

Brian
  ----- Original Message -----
  From: Paul Vernon
  To: CF-Talk
  Sent: Wednesday, January 14, 2004 2:07 PM
  Subject: RE: Section 508

  > 2. Even though it may cause an accessibility problem, it's not technically
  > broken by 508 guidelines. Nothing in 508 requires support for keyboard
  > navigation.

  Wow, that is poor! My step-mother has Retinitis Pigmentosa (RP) and was
  diagnosed with it when she was 11 or 12. She lost her sight totally about 10
  years ago. About a year ago, we bought a DELL laptop that I configured with
  screen reader software and I also sat there for two hours sticking on
  transparent braile stickers over the keys so it was more friendly for her to
  use. She uses the keyboard for everything. The mouse is a waste of time for
  her, it is there only for other people to use when they need to work on her
  PC.

  The fact that there is no mandatory requirement in Section 508 for keyboard
  navigation seems somewhat flawed for legislature that is designed for
  accessibility purposes does it not?

  And yes, they need to work on their CF code a bit..... :)

  Paul
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to