VA has it's hand's full with Section 508...
The URL about says it all:
http://veterans.house.gov/hearing/assessing-inadequacies-in-va-data-usage-for-and-services-provided-to-visually-impaired
By January 2013 all Veterans Affairs Department websites were required to conform with Section 508 of the Rehabilitation Act, but not only are many VA websites non-compliant, the department lacks a clear timeline for meeting the requirement.
Section 508 requires federal agencies to make electronic content and information technology accessible to people with disabilities.
"At this point in time we've not achieved 100 percent conformance with the 508 standard," said Lorraine Landfried, deputy chief information officer for product development at VA. Landfried spoke May 28 before the House Veterans Affairs subcommittee on oversight and investigations.
Landfried later said she could not provide a date when all VA systems would meet the standard.
Anyone out there who has done compliance work for the VA understands the problem here: an entrenched bureaucracy, with contractor's lining their pockets instead of trying to help make documents accessible!!!
Read more: VA websites miss 508 compliance deadline, lack timeline for achievement - FierceGovernmentIT http://www.fiercegovernmentit.com/story/va-websites-miss-508-compliance-deadline-lack-timeline-achievement/2014-05-29#ixzz33DJ9Qwbn
Subscribe at FierceGovernmentIT
Subscribe to:
Post Comments (Atom)
The Truth About the Refresh: WCAG 2.0 It I!
In January 2017, the U.S. Access Board issued the Information and Communication Technology (ICT) Standards and Guidelines, updating its ex...
-
Here's a nice overview showing some real-world examples of what it takes to make documents accessible and compliant with Section 508: ...
-
Every document is unique, and every client has different requirements, so there is no set cost per page to make a document compliant wit...
-
Using best practices for creating accessible documents makes Section 508 compliance much less costly. Adding alternative text for imag...
No comments:
Post a Comment