E-mail List Archives
Thread: RE: Section 508 Standards Compliance and Scripts
Number of posts in this thread: 2 (In chronological order)
From: julian.rickards
Date: Thu, Sep 04 2003 1:22PM
Subject: RE: Section 508 Standards Compliance and Scripts
No previous message | Next message →
Section 508 is based on WAI but scattered a bit in terms of Priority levels.
With regard to the JavaScript question, I believe that WAI is a bit more
strict and would be more likely to reject some claims of compliance as
compared with Section 508. If you can achieve compliance with WAI Priority
2, you will be in good standing for Section 508.
>
From: Anitra Pavka
Date: Thu, Sep 04 2003 2:48PM
Subject: Re: Section 508 Standards Compliance and Scripts
← Previous message | No next message
= EMAIL ADDRESS REMOVED = wrote:
>Section 508 is based on WAI but scattered a bit in terms of Priority levels.
>With regard to the JavaScript question, I believe that WAI is a bit more
>strict and would be more likely to reject some claims of compliance as
>compared with Section 508. If you can achieve compliance with WAI Priority
>2, you will be in good standing for Section 508.
>
There is one notable exception to the belief that WAI Priority 2's
encapsulate all Section 508 Web guidelines. Section 508 guideline
1194.22 (p) is not reflected in WAI's WCAG 1.0.
http://www.access-board.gov/sec508/guide/1194.22.htm#(p)
The closest WCAG 1.0 comes to covering it is Guideline 7, but none of
the related checkpoints specifically address the user's ability to
extend time limits.
http://www.w3.org/TR/WCAG10/#gl-movement
Fortunately, the WCAG 2.0 (current) Draft explicitly covers the missing
guideline.
http://www.w3.org/TR/2003/WD-WCAG20-20030624/#time-limits
- Anitra Pavka
Web Developer, www.accesskansas.org
Web Accessibility Advocate, www.anitrapavka.com
>>