P = People. Who is your target audience? What tools are they using?
We believe in putting people first, and that means our website content must be equally accessible to people with disabilities–some of whom have acquired their disabilities as a result of HIV/AIDS.
Recently, we learned that thousands of our Federal HIV websites are not always accessible to persons with disabilities, including more than one million legally blind, and 28 million deaf or hearing-impaired, citizens. Last week, AIDS.gov sponsored a conference call for over 100 of our Federal colleagues to talk about making our websites “Section 508 compliant.” (This refers to a law that requires Federal information in electronic formats to be accessible to all individuals with disabilities.)
During the call, we learned a lot from our Federal colleagues about the things we need to do to ensure our HIV/AIDS web pages are compliant, as well as some key information for those who receive Federal HIV/AIDS funding.
HIV/AIDS Webpages and 508
Jeremy Vanderlan from AIDS.gov talked about his challenge in developing promotional materials. In using a screen reader that allows you to experience “reading” a document just as a visually impaired person would experience it, he noticed that the screen reader read the phrase “.gov” as “dot governor.” To resolve the problem, Jeremy edited each “.gov” instance to “dot gov.” “As you can imagine, if these are promotional documents for a dot gov website,” Jeremy said, “there were quite a few references to this error.”
Michael LaFlam commented after the call about the CDC’s video podcast accessibility issues. “We had thought that, because we offered a transcript, we were meeting requirement standards,” he said–something those of us at AIDS.gov also had to learn. “We subsequently learned that we needed to make our podcasts open-captioned, which is different from closed-captioned, in that the text appears on the screen without user intervention.” The CDC has to outsource the open-captioning process, which affects their production time-line and budget.
Kristen Kayatta, one of HHS’s Section 508 experts, told those on the call that there are numerous 508 issues on HHS’s 1.6 million Web pages. In fact, there’s an average of 14 issues per Web page. That’s a big job to fix, but Kristen said, “We have a five year plan … we’re well on our way.” She explained 508 compliance to our Federal colleagues in this way:
” … at the most basic level, [508 compliance] requires and ensures that all users have equal access to electronic documents. First, is the development of web pages. This means that all files must be machine-readable. All audio files need to have accompanying text and video files need to be captioned. Secondly, Section 508 applies to all electronic documents, including PDF files, Word files, and the PowerPoint files. And, lastly, this affects not only files that are posted on our site, but also those that are shared through e-mail, through portals, and that are saved on our share drives.”
Kristen offered some resources to help everyone achieve 508 compliance:
- HHS Section 508 Accessibility – This site includes information on Section 508, including: determining how the law applies, assistance in creating compliant documents and Web pages, information on standards and policies, how to gain access to 508 tools, and language to add to contracts to ensure all deliverables are 508 compliant.
- We also recommend that you check out the resources discussed in our January 29, 2008 post on 508 compliance.
- The U.S. Access Board’s standards for Web-based Internet and intranet information and applications (36 CFR 1194.22) for documents (HTML, Word, etc.)–and don’t forget the Access Board’s standards for software, such as scripting or Flash.
Note to AIDS Service Providers
We all need to think about 508 issues for our Web pages, because, sooner or later, if you work with Federal programs, you are going to face this challenge. Federal agencies are required by law to be 508 compliant, and if you receive Federal funds for your work, you are required to consider accessibility, too. Federal contracts now require products to be 508 compliant, and soon, Federal grant proposals will also contain 508 requirements. In addition, state and local government activities are covered by other state laws and the Americans with Disabilities Act.
Bottom line? We need to be accessible, but we still have a lot to learn. HHS is working to ensure that our materials are accessible, but becoming accessible will be a process, not an event. The AIDS.gov team would like to thank the speakers and participants from last Tuesday’s call. Together we can meet our goal of doing the right thing in making all our materials accessible.
Do you have a section 508 challenge or success story? We’d love to hear about it!