Accessible Poetry comes with a toolbar with buttons to change font size, adjust contrast, disable animations, and more. Also, Skiplinks are available that let users navigate between main areas of the page using the keyboard, and if an image doesn’t have Alt text, you’ll be alerted (you can even add ALT text without leaving this screen). Beyond that, outline effects for objects in focus mode, link underlining, and custom CSS/JS code addition are supported. To access this resourceful toolbar, just click the floating button on the screen.
Now you know that some types of content and format on webpages can pose barriers for people with disabilities. The next steps are to develop an action plan to fix web content that is currently inaccessible and implement procedures to ensure that all new and modified web content is accessible. The website accessibility checklist included in this section helps you assess what needs to be done.
Because they only read text, screen readers and refreshable Braille displays cannot interpret photographs, charts, color-coded information, or other graphic elements on a webpage. For this reason, a photograph of a mayor on a city’s website is inaccessible to people who use these assistive technologies, and a blind person visiting the website would be unable to tell if the image is a photo, a logo, a map, a chart, artwork, a link to another page, or even a blank page.
Without a crystal ball, it’s difficult to gauge where the Trump administration will direct the DOJ on ADA regulations in relation to websites moving forward, if they do at all. The administration has already emphasized a desire to move away from regulation and those with a vested interest in the application of the ADA to websites have taken that as a signal that the already thrice delayed process will continue to be pushed down the list of priorities.
DOJ’s September 25 response did not do what the members asked, but it did provide some helpful guidance and invited Congress to take legislative action to address the exploding website accessibility litigation landscape. DOJ first said it was “evaluating whether promulgating specific web accessibility standards through regulations is necessary and appropriate to ensure compliance with the ADA.” (This is helpful – to at least know this issue has not fallen totally off DOJ’s radar.) It continued: 

In a society in which business is increasingly conducted online, excluding businesses that sell services through the Internet from the ADA would ‘run afoul of the purposes of the ADA’” in that it would prevent “‘individuals with disabilities [from] fully enjoy[ing] the goods, services, privileges, and advantages, available indiscriminately to other members of the general public.
Leading web developers have been pioneering accessibility and publishing standards since 1994. In 1999, the Web Accessibility Initiative (WAI) and the World Wide Web Consortium (W3C) created the Web Content Accessibility Guidelines (WCAG). In essence, the people who determine how the internet is written came together to advise web developers on how to make websites accessible not only to people with disabilities, but to all web users, including those with highly limited devices.
Your site would need to have a text only option, with all functionality accessible through a keyboard for visitors with mobility issues. Once you make these and other changes to meet ADA guidelines, your site would need to be tested by a website development company familiar with ADA compliance issues to be sure that visitors who use assistive technology such as screen readers are able to access your web content fully.
On Dec. 26, 2017, the DOJ withdrew the proposed rulemaking for Title II and Title III, effectively killing any forward progress on adoption (more on that here: While disappointing, this is not surprising, given the current administration's commitment to deregulation. That said, I fully expect the courts to continue to fill the gap and hold businesses accountable, so I would encourage you to take accessibility standards into account as you work up the governance for your enterprise intranet services. If it would be helpful for me to put you in touch with an attorney with experience in these matters, I'd be more than happy to do so. Feel free to shoot me an email anytime at [email protected] Best of luck!
HTML tags – specific instructions understood by a web browser or screen reader. One type of HTML tag, called an “alt” tag (short for “alternative text”), is used to provide brief text descriptions of images that screen readers can understand and speak. Another type of HTML tag, called a “longdesc” tag (short for “long description”), is used to provide long text descriptions that can be spoken by screen readers.
In a society in which business is increasingly conducted online, excluding businesses that sell services through the Internet from the ADA would ‘run afoul of the purposes of the ADA’” in that it would prevent “‘individuals with disabilities [from] fully enjoy[ing] the goods, services, privileges, and advantages, available indiscriminately to other members of the general public.
Webpage designers often have aesthetic preferences and may want everyone to see their webpages in exactly the same color, size and layout. But because of their disability, many people with low vision do not see webpages the same as other people. Some see only small portions of a computer display at one time. Others cannot see text or images that are too small. Still others can only see website content if it appears in specific colors. For these reasons, many people with low vision use specific color and font settings when they access the Internet – settings that are often very different from those most people use. For example, many people with low vision need to use high contrast settings, such as bold white or yellow letters on a black background. Others need just the opposite – bold black text on a white or yellow background. And, many must use softer, more subtle color combinations.
Consequently, the Department intends to publish a Notice of Proposed Rulemaking (NPRM) to amend its Title II regulations to expressly address the obligations of public entities to make the websites they use to provide programs, activities, or services or information to the public accessible to and usable by individuals with disabilities under the legal framework established by the ADA.
Use the plugin, follow its instruction, and resolve the compliance issues identified. You’ll find that using the plugin will save you an incredible amount of time as you maintain your site’s compliance on a month-to-month basis. The best part, it identifies the compliance issues and tells you exactly which code elements are out of compliance and why! Our average customer is reporting a 10x-20x time savings over manually identifying and fixing these problems. In extreme cases more than 30x time savings has been reported! Using the plugin alone does not guarantee compliance. Some parts of accessibility can’t be automatically scanned and must be manually audited but we also provide independent 3rd-party audits and certifications of compliance. The Accessibility Suite Pro Plugin for WordPress makes this process profoundly easier.
The statement that “noncompliance with a voluntary technical standard for website accessibility does not necessarily indicate noncompliance with the ADA” is new and significant.  It is a recognition that a website may be accessible and usable by the blind without being fully compliant with the privately developed Web Content Accessibility Guidelines (WCAG) 2.0 or 2.1.  The statement confirms what some courts have said so far:  That the operative legal question in a website accessibility lawsuit is not whether the website conforms with WCAG, but whether persons with disabilities are able to access to a public accommodation’s goods, services, and benefits through the website, or some alternative fashion.