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!
We not only referenced the ADA’s requirements while building the website, but also sat down one-on-one with users who are blind to see how they navigated the site. These individual sessions were invaluable and provided more insights than just the law’s basic requirements. Instead of making assumptions about how these users would interact with the site, we took the time to observe their real interactions and used that data to formulate new features.
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.
A one of a kind plug-in, WP ADA Compliance Check Basic does just that – checking WordPress websites for ADA compliance. There are two ways to use it. First, you can schedule a whole-site scan to find out any ADA compliance issues. Secondly, you can set it to run every time new content is published. When set this way, the plug-in will identify and report on any ADA compliance issues found in the new content as well as recommend possible solutions. The full version even corrects some of the uncovered issues automatically.
Penn in particular nearly made the cut because I really like their keyboard accessibility. It amazes me how few sites provide visible indication of keyboard focus, when it's incredibly simple to achieve (just add a style for a:focus in your style sheet). Penn did this, and consequently it's very easy for sighted keyboard users to keep track of their position as they tab through the page. They also included a keyboard-accessible dropdown menu. However, there are some dynamic features on the Penn home page that really need ARIA markup for full accessibility. They also have a few contrast problems, most notably their slideshow navigation, which is red-on-red:
@Rick, I didn't specifically look at doctype, but Steve Faulkner did in his original article (see the link at the top of this post). He found that 101 of the 130 pages containing role="main" (78%) used the HTML5 doctype, which of course leaves 22% that didn't. I do recommend using ARIA even if using an earlier doctype. Validation is important, but if validation and accessibility conflict, I think most would agree accessibility should trump validation. Assistive technologies that support ARIA landmarks do so regardless of doctype, and otherwise the presence of these role attributes has no ill effects in any user agent.
Although the plugin works, we activated the white label solution. They said: For only $10 you can modify the widget footer, remove the donate link and enable other customizations From then and on they charge me every single month 10$, they don't reply to my messages and the so called "Manage" menu has been disappeared from the widget... BE AWARE! I'm still trying to resolve this....
Upon discovering issues faced by disabled government employees and the public, revisions to section 508 were made. The issues that were uncovered involved websites, documents, and software programs. As of January 2018, the updated 508 standards require all federal agencies and contractors to create web content accessible to all. The updated standards also include Website 508 compliance.
It’s an important tool because Contact Form 7 isn’t so accessible by default. The plugin adds a selection of accessible form types to use as the basis for your new form. Note that it doesn’t affect pre-existing forms – just new ones. For existing forms, you’ll have to recreate them using the new templates. That’s why it’s recommended that you install this companion plugin on your site at the same time as Contact Form 7.
Covered entities are required to provide aids and services unless doing so would result in an “undue burden,” which is defined as significant difficulty or expense. If a particular aid or service would result in an undue burden, the entity must provide another effective aid or service, if possible, that would not result in an undue burden. Determining what constitutes an undue burden will vary from entity to entity and sometimes from one year to the next. The impact of changing economic conditions on the resources available to an entity may also be taken into consideration in making this determination.
According to the DOJ, “Being unable to access websites puts individuals with disabilities at a great disadvantage in today’s society.” With these words in mind, the DOJ has rapidly adopted the role of web accessibility enforcer. A failure to make digital content, including websites, accessible to all individuals regardless of their emotional, physical, or mental disabilities, can result in hefty fines and class action lawsuits. In short, the DOJ is dedicated to making sure that individuals with disabilities have the same equal access to the benefits that are available online. Creating equal access is only possible if organizations a) understand the requirements of web accessibility, b) know that web accessibility is an obligation under the ADA, and c) make web accessibility a priority. The value that awaits when organizations adhere to digital accessibility laws can be measured in more than dollars and cents.