1) In practice, Section 508 implementation in in the mind of the US Government Agency (in Gov speak called the COTR). Although, sometimes there are spot checks for compliance, in practice, many agencies do not have the budget to complete a Section 508 (or even better a W3 useability) test plan.
2) Flash uses the Windows Accessability toolkit. While good enogh for most, some are on Macs and Unix platforms -- and will not see the accessability features.
3) Section 508 of the American with Diabilities act only applies to US government contracts and projects.
Jeremy Brodie
Edgewater Technology
web: http://www.edgewater.com
phone:(703) 815-2500
nasdaq symbol: EDGE
>Actually, I was wrong. The _web_ part of 508 doesn't require keyboard
>navigation; however, the preceeding section of 508 that covers software
>applications and operating systems does.
>
>--
>Subpart B -- Technical Standards
>
>
>� 1194.21 Software applications and operating systems.
>
>(a) When software is designed to run on a system that has a keyboard,
>product functions shall be executable from a keyboard where the function
>itself or the result of performing a function can be discerned textually.
>
>--
>
>My apologies for the confusion.
>
>
>
>-Kevin
>
>
>
>
>
>----- Original Message -----
>From: "G" <[EMAIL PROTECTED]>
>To: "CF-Talk" <[EMAIL PROTECTED]>
>Sent: Wednesday, January 14, 2004 2:41 PM
>Subject: Re: Section 508
>
>
>> 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]
