Error prevention on important forms (3.3.4): For pages that create legal commitments or financial transactions or any other important data submissions, one of the following is true: 1) submissions are reversible, 2) the user has an opportunity to correct errors, and 3) confirmation is available that allows an opportunity to review and correct before submission.
I think it's a pretty good sample of doubtlessly accessible websites. Of course they have put a special effort in getting this label, but somehow it shows that it's possible. I also like the fact that they are pretty diverse in their purposes and target audiences, and are not visually different than the usual production. Which confirms our claims that accessible does not mean boring or not visually appealing - at least, if it's the case, then blame the designer, not accessibility!
If the user selects this button, the page is read aloud while text is highlighted. This is powered by ReadSpeaker, which I think is a really cool product. It provides improved accessibility to a vast audience of people who might not otherwise have their own assistive technology, such as people who are not native to the language of the page, or people with dyslexia or other reading challenges.
UPDATE: Since writing this post in August 2017, several important changes have taken place in the laws regarding ADA compliance for websites. On December 26, 2017, the Department of Justice announced that they have withdrawn the Obama-era Advance Notice of Proposed Rulemaking mentioned in this article which intended to require ADA website compliance. The DOJ’s withdrawal announcement stated, “The Department will continue to assess whether specific technical standards are necessary and appropriate to assist covered entities with complying with the ADA.”
You probably won't have to check your site with all of the available evaluation tools out there, but it is a good idea to do so for the most common web browsers. Just as accessibility software makes it easier for people with disabilities to navigate the Internet, these tools make it easier for developers to ensure accessibility from the start. When you think you've mastered it, go back through the Section 508 compliance checklist to ensure you've met every goal.
The 2014 case involving Peapod, an online grocery retailer emphasizes that being ADA compliant goes beyond your website. The settlement required Peapod to make its mobile applications accessible by March 2015 and its website accessible by September 2015. Since mobile apps are fast becoming the preferred method of online shopping, e-commerce sites must focus on app accessibility too.
Read our case study of VisionCorps, ‘The Importance of ADA Website Compliance,’ to realize first-hand the impact an accessible website can have, and see real-world examples of ADA website compliance. VisionCorps’ total page views increased 157.64% after redesigning their website to be ADA compliant. Get more facts and figures by reading the case study now.
When you insert an image into a post or page, consider providing a rich description for the caption that will improve the reading experience for everyone, but especially folks who can’t see the image. Be creative. Instead of “My son on his swing,” try “My son is playing on his favorite swing. His face is filled with pure joy on a beautiful Spring day. Perfection.” The goal here is to convey the feeling of the image.
Eric Kazda is a leading expert in the interactive development industry with over fifteen years of experience. With a mastery of critical development technologies, Eric has crafted innovative award-winning work for clients both large and small. Coupling this knowledge with a real world understanding of usability and technological feasibility, his work is developed to be accessible by every user.
more than the list of websites, I appreciate the 10-second method you describe. I think it's worth explaining to developers and site owners that there are indeed some simple tricks to quickly assess a web page without having a deep understanding of the WCAG. Personally, I like removing all the CSS styles (with the Web Developer Toolbar in Firefox, shortcut is Shift+Ctrl+S). If the page is still pretty readable, with no clumsy technical code; if it shows a neat heading structure; if lists appear well structured and appropriately used; if all text, is in black (except links), left-aligned, and with its default font and size; then it's been probably properly coded, HTML-wise.
The Department of Justice may file lawsuits in federal court to enforce the ADA Compliance, and courts may order compensatory damages and back pay to remedy discrimination if the Department prevails. Under title III, the Department of Justice may also obtain civil penalties of up to $55,000 for the first violation and $110,000 for any subsequent violation of ADA Compliance.