ADA Compliance Services

What Is ADA Compliance?

ADA Compliance makes your website more accessible to users with disabilities. We will update your website to meet core ADA Compliance requirements by adding features that make their user experience as smooth as possible!


If you are interested in our services to get your site more compatible with ADA requirements, here is a quick checklist of the main compliance items our developers will work on as they update your website.

Please contact us for a free review of your ADA exposure. Most ADA cleanup projects will cost between $1,000 and $2,000.

To be clear, we are not guaranteeing to be 100% ADA compliant at this lower budget. But if we can clear off all the items on the list below, you are definitely doing a much better job helping people with disabilities to access your website.

What’s Included in our ADA Cleanup Services?

  • Alt tags provide a text description for each image on your site. If a screen reader doesn’t see an alt tag in your html source code, then the person with a visual disability who cannot see the image will not be able to know what the graphic element on the screen is all about. For all photos and graphics that are part of the actual website content of a page, make sure to include an alt tag description.
  • Headings such as page titles, H1, H2 and H3 heading tags (used for headlines and subheadlines) need to be nested correctly. Page headings should follow a logical sequence: “h1” should hold “h1” and “h2” should be inside an “/h2” tag, and so on. If WAVE detects a skipped heading level, it might mean the code goes from an “h3” to an “h1” or an “h3” to a closing “h2” it could wreak havoc on the page reader. The fix is to ensure that heading numbers flow in order. Best practices: Use one top-level heading “h1”, and below that, you may choose to include multiple “h2” tags. If there are even smaller headings within the sub-sections, go to “h2” and “h3” tags. If no heading level is skipped, you beat the game.
  • ARIA landmarks should be set in your code for ARIA readers to be able to identify the header, footer, sidebar, and page content.
  • Navigation Menus should exist to allow people to easily access each page of your site. Use breadcrumbs on each page so visitors can figure out where they are inside your website and how to access other pages. Avoid having orphaned pages.
  • Skip to the main content is a way for people with a screen reader to jump right to the main content of the page (and thus skip the nav menus).
  • Plug-ins should be tested to make sure they are ADA compliant.
  • Links and Anchor Text should clearly indicate what the link is supposed to do. If the anchor text is clear, then you don’t need a description of the link. However, links such as Click Here can mean anything. Adding relevant anchor text is a good solution for ADA purposes.
  • Video Files should have captions and transcriptions.
  • Audio Files and audio clips should include links to related transcriptions.
  • Tabbing Through the Page ensures all elements can be accessed by using the tab key on a keyboard.
  • Text Size Controls enables a person with visual impairment (that could mean partial site) to have functionality to enlarge text. For example, if you have light colored text or smaller fonts that are hard to read, we advise using a plugin like Userway to enable screen manipulation (like enlarging fonts or changing colors on the screen).
  • Documents like PDF files should have HTML or text versions of the content inside those files. The native PDF files should also meet ADA requirements.
  • Add the Document Language HTML tag attribute in the header file to inform the screen reading software what language to read. If your website doesn’t identify its language, it is simply less accessible.
  • Missing Form Labels can impact the ability of a person with disabilities to enter information into a website. Each form should have a label associated with it to describe what information the user is being asked to fill in (First Name or Phone Number). Screen reading software treats these labels like alt text attributes. An example of a compliant form is having a