The irony is strong in this one.
</cf_darth>
Two things to note:
1. It's caused by the unnecessary "overflow: auto" on the body in their CSS.
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.
-Kevin
----- Original Message -----
From: "Paul Vernon" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, January 14, 2004 1:39 PM
Subject: RE: Section 508
> Being from the UK, I had no idea what Section 508 stood for so a quick
> google took me to the Section508.gov site.... so now I know
>
> Now I like to scoll down pages using the keyboard either with the up/down
> arrows or the page up/down keys.... Is it just me or do they not work on
> this site???? Mouse based scrolling works a treat!
>
> I've verified this to be the case on two separate installations of IE and
> also checked the same instances of IE on other web-sites... Keyboard
> navigation is working fine..... This does not bode well for an
accessibility
> focused web-site!!! Incidentally, tabbing through links on the site works
> fine...
>
> The summary breakdown of the standards can be found here....
>
> http://www.section508.gov/index.cfm?FuseAction=Content
> <http://www.section508.gov/index.cfm?FuseAction=Content&ID=11> &ID=11
>
> Hope you have a wheel mouse!
>
> Further links can be found here....
>
> http://www.section508.gov/index.cfm?FuseAction=Content
> <http://www.section508.gov/index.cfm?FuseAction=Content&ID=131> &ID=131
>
> Paul
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
