The menu is fully keyboard accessible and contrast levels for text are kept well above the 4.5:1. This theme passes WCAG 2.0 AA standards out-of-box. On wordpress.org, Period is given the “accessibility-ready” tag. This is basically a reminder to users that while all design elements in Period pass accessibility standards, it’s up to the user to make sure their content is accessible too in order for their site to maintain its accessibility.
Reha asked Vu if companies are obligated to comply? Vu said that unlike the physical access world, where any new building has to be compliant no matter what, there’s no such thing in the web world. The Justice Dept. hasn’t said that that’s the default, but they have said that the current regulatory regime requires it anyway. Equal access has been around since 1990.
Up-to-date standards are offered for checking compliance, and it provides a cost-effective way to scan a site for compliance. There's services out there where it'd cost more than $150 (the current cost of a 1 site 1 year license) for the size of the sites I'm working with. I'm very happy to see this offering in the first place, and it's even nicer to see how thorough it looks to be. Of course, it's not perfect so I'd love to see more of the WP.org listing fleshed out (the developer author/contributor mention is missing, etc.), I'd love to see the free version on GitHub (or similar for community development assistance [I have a few things I'd help with] which is very nice to see in a WP.org listing to show there's support / ongoing development for the plugin), and of course I'd love to see the server-side checker come to feature-parity with WAVE (currently WAVE is showing a few things the server-side checker doesn't have [color contrast, etc.]) Keep up the great work!
This plug-in has been around for some time. Recently they were even advising users to uninstall the old version and install a new one. The new version comes with Skip menus, a button to reset font size, a Skip link inside the accessibility sidebar, and a DOM scanner that automatically checks pages and published posts for accessibility errors such as issues in image ALT, titles, and links. Contrast adjustment, color filters, lights off mode, and link highlighting are the other standout features.
@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.
An accessible and ADA compliant website has the potential to increase your sales by over 20%. The market segment of persons with a disability is very loyal to businesses and websites that make legitimate efforts to increase their quality of life. Your businesses social media presence can also be improved as visitors share their favorable interactions with your businesses. Offering your business a significant and fiercely loyal revenue stream.
President George H.W. Bush signed the Americans with Disabilities Act into law July 26, 1990. The ADA prohibits discrimination of people with disabilities and guarantees the same opportunities as everyone else. These opportunities include employment possibilities, purchasing of goods and services and the ability to participate in State and local government programs.