ADA Compliance Checklist (WCAG)

Modified on Fri, 28 Mar at 10:57 AM

Enfoldsystems makes every effort to be ADA compliant. We are always working on the themes and
features. However a large part of being compliant is in the hands of the editor.


Ploud WCAG Compliance Document 

Not all testing tools are a 100% accurate and false positives can be detected. So understand the testing software you are using. One such tool is a browser plug-in called WaveAlthough not the best tool its free and can get you started.

Here are a couple of things you can run into that will break compliance


Carousels - Screen readers don't play well with read slides and often it will come out as gibberish. If you do chose to use a carousel test it with a screen reader.


Copy & Paste - Copying from such editors such as MS Word can brings in the formatting of the source document which MS translates into in-line CSS forcing the text to try to look like it did in Word. As an example text color could be set to red and would not be compliant.

* Indicates a local edit highlighting items that are not discoverable via current ADA testing software.

  1. Every image, video file, audio file, plug-in, etc. has an alt tag

  2. * Complex graphics are accompanied by detailed text descriptions

  3. The alt descriptions describe the purpose of the objects

  4. * If an image is also used as a link, make sure the alt tag describes the graphic and the link destination

  5. * Decorative graphics with no other function have empty alt descriptions (alt= "")

  6. Add captions to videos

  7. Add audio descriptions

  8. Create text transcript

  9. Create a link to the video rather than embedding it into web pages

  10. Add a link to the media player download

  11. Add an additional link to the text transcript

  12. The page should provide alternative links to the Image Map

  13. The <area> tags must contain an alt attribute

  14. Data tables have the column and row headers appropriately identified (using the <th> tag)

  15. * Tables used strictly for layout purposes do NOT have header rows or columns

  16. Table cells are associated with the appropriate headers (e.g. with the id, headers, scope and/or axis HTML attributes)

  17. Make sure the page does not contain repeatedly flashing images

  18. Check to make sure the page does not contain a strobe effect

  19. A link is provided to a disability-accessible page where the plug-in can be downloaded

  20. All Java applets, scripts and plug-ins (including Acrobat PDF files and PowerPoint files, etc.) and the content within them are accessible to assistive technologies, or else an alternative means of accessing equivalent content is provided
  21. When form controls are text input fields use the LABEL element

  22. When text is not available use the title attribute

  23. Include any special instructions within field labels

  24. Make sure that form fields are in a logical tab order

  25. Include a "Skip Navigation" button to help those using text readers

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article