The Complete Guide to Digital Accessibility
For years, website accessibility was treated as something organizations could address after a website was designed, developed, and launched. Build the site first, then run a scan, install a tool, or fix whatever accessibility issues surfaced later.
That thinking is changing.
A website is now a primary point of access to businesses, government services, healthcare providers, educational institutions, nonprofits, and community organizations. People use websites to make purchases, schedule appointments, complete applications, register for programs, pay bills, and access essential information. If someone cannot perform those tasks because of a disability, the problem isn’t simply technical. It’s a barrier to participation.
That’s why website ADA compliance needs to be understood as part of a broader discipline: digital accessibility.
The distinction matters. The Americans with Disabilities Act imposes legal obligations for equal access. The Web Content Accessibility Guidelines (WCAG) set technical standards for making digital content more accessible. But neither should reduce accessibility to a checklist.
The more useful principle is simpler:
Accessibility is a practice, not a product. No widget, plugin, scanner, certification badge, or artificial intelligence platform can replace the ongoing work of designing, developing, testing, and maintaining an accessible digital experience.
This guide explains what website accessibility means, how ADA and WCAG align, how accessibility issues are identified and remediated, where automated tools fit, and how organizations can embed accessibility into their long-term digital strategy.
- website.
- Accessibility is ongoing. Websites change constantly, which means testing, native remediation, content standards and monitoring need to become part of normal website management.
What Is Website Accessibility?
Website accessibility means designing and developing digital content so that people with disabilities can perceive, understand, navigate, and interact with it.
That can include people who are blind or have low vision, people who are deaf or hard of hearing, people with limited mobility, people with cognitive disabilities, and users who rely on assistive technologies.
Who Accessibility Serves
Blind or low vision
Screen readers, magnification, contrast adjustments
Deaf or hard of hearing
Captions for video, transcripts for audio
Limited mobility or dexterity
Keyboard navigation, voice commands alternative input
Cognitive disabilities
Clear instructions consistent navigation. understandable forms
Assistive technology users
Software and devices that rely on well-structured code
Someone may navigate your website using a keyboard instead of a mouse. Another visitor may use screen-reader software that converts website content into speech or braille. Someone with low vision may dramatically enlarge the page or adjust the contrast. A user with limited dexterity may rely on voice commands or another alternative input device
An inaccessible website can turn otherwise simple tasks into significant obstacles.
An image with important information but no useful text alternative may be meaningless to someone using a screen reader. A form that can be completed only with a mouse can block a keyboard user. A video without captions can exclude someone who cannot hear the audio. Poor color contrast can make content difficult or impossible to read.
Accessibility addresses these barriers.
It also tends to encourage better website design overall. Clear navigation, logical page structures, understandable forms, readable typography, and predictable interactions aren’t useful only to people with disabilities. They’re characteristics of a better digital experience for everyone.
That’s one reason to consider accessibility during the design process rather than as an afterthought. Our article on balancing form and function in website design explores this broader relationship between aesthetics, functionality, usability and accessibility.
How Does the ADA Apply to Websites?
The Americans with Disabilities Act (ADA) is a civil rights law enacted in 1990 that prohibits discrimination against people with disabilities.
The ADA predates the modern commercial web, which is one reason website accessibility law can seem confusing.
Two portions of the ADA are particularly relevant to digital accessibility.
Title II
Title II applies to state and local governments. The U.S. Department of Justice has established web and mobile accessibility requirements for public entities, using WCAG 2.1 Levels A and AA as the technical standard. Larger public entities faced a compliance deadline of April 24, 2026, while smaller public entities and special district governments generally have a deadline of April 26, 2027, subject to the rule’s provisions and exceptions.
Title III
Title II applies to state and local governments. The U.S. Department of Justice has established web and mobile accessibility requirements for public entities, using WCAG 2.1 Levels A and AA as the technical standard. Larger public entities faced a compliance deadline of April 24, 2026, while smaller public entities and special district governments generally have a deadline of April 26, 2027, subject to the rule’s provisions and exceptions.
The above makes an important distinction worth remembering:
The ADA is a law. WCAG is a technical accessibility standard.
They are closely connected in practice, but they aren’t the same thing.
Organizations shouldn’t wait for that distinction to be settled in a court before making their websites usable. Website accessibility lawsuits and demand letters have become a genuine operational concern for businesses of many sizes.
We’ve examined that risk in more detail in ADA Website Lawsuits Are Rising: Here’s How to Protect Your Business, as well as our firsthand experience described in A Wake-Up Call on ADA Website Compliance.
But legal exposure shouldn’t become the entire reason for accessibility.
The better question isn’t simply, “Could we get sued?”
Rather, it’s: Can people with disabilities use our website?
Accessibility Note: This guide covers website development and digital accessibility practices. It does not offer legal advice. Organizations with questions about their specific obligations under the ADA or other accessibility laws should consult qualified legal counsel.
Understanding WCAG
The Web Content Accessibility Guidelines, commonly known as WCAG, are developed by the World Wide Web Consortium’s Web Accessibility Initiative.
WCAG provides a common technical framework for making websites, applications and other digital content more accessible.
The current W3C recommendation is WCAG 2.2. It builds on earlier WCAG versions rather than discarding them. WCAG 2.2 adds success criteria to the framework established by WCAG 2.1, and W3C encourages organizations to use the latest version.
WCAG is organized around four principles often abbreviated as POUR.
Perceivable
Information must be presented in ways users can perceive.
For example, important images may need text alternatives. Videos may need captions. Text needs sufficient contrast with its background.
The goal is to avoid communicating essential information in only one way.
Operable
People must be able to operate the website.
A user who cannot use a mouse should still be able to navigate menus, activate buttons, complete forms, and interact with website functionality using a keyboard or appropriate assistive technology.
Understandable
Website content and functionality should be understandable and reasonably predictable.
Instructions should be clear. Navigation should behave consistently. Forms should identify errors in a meaningful way rather than simply informing the user that something went wrong.
Robust
Website content should be structured so it can be reliably interpreted by different browsers, devices, and assistive technologies.
This is where proper HTML structure and development practices are especially important.
WCAG success criteria are classified into three conformance levels:
Level A covers fundamental accessibility requirements.
Level AA includes Level A requirements plus additional criteria and is a common accessibility target for organizations.
Level AAA contains the most stringent criteria. W3C does not recommend requiring Level AAA conformance as a general policy for entire websites because some content cannot meet every AAA criterion.
The goal for a business owner or marketing manager isn’t to memorize WCAG. It’s to understand that accessibility can be evaluated against defined, testable criteria rather than subjective impressions.
What Makes a Website Accessible?
Accessibility touches almost every layer of a website.
Visual Accessibility
Text needs sufficient contrast against its background. Users should be able to resize text without breaking the layout. Color shouldn’t be the only way to communicate important information.
Images that convey information need appropriate text alternatives so users who cannot see them can understand the images’ purpose.
Visible keyboard focus is also important. Someone navigating without a mouse needs to know which link, button, or form control is active.
Navigation
Visitors should be able to navigate a website without depending entirely on a mouse.
That includes logical keyboard navigation, sensible tab order, consistent menus, and descriptive links.
A “Learn more” link may make perfect sense visually when surrounded by other content, but someone navigating a page by listening to a list of links may hear several identical “Learn more” links without knowing where any of them lead.
Context matters.
Content Structure
Headings aren’t merely a matter of visual styling.
A well-structured page uses headings to establish relationships among sections, helping both users and assistive technology understand how the information is organized.
Semantic HTML, descriptive page titles, properly structured lists, and accessible tables all contribute to that structure.
Forms and Interactive Elements
Forms are a common source of accessibility problems.
Fields need meaningful labels. Required information should be communicated clearly. Error messages need to explain what happened and how to correct it.
Interactive components such as menus, accordions, modal windows, and custom controls also need to be accessible to people using keyboards and assistive technology.
Multimedia
Video content may require captions. Audio-only material may require transcripts. In some cases, visual information in a video may need audio description.
Media controls themselves also need to be accessible.
Documents
Accessibility doesn’t stop when someone clicks a PDF.
PDFs, downloadable forms, reports, and other documents can contain their own accessibility barriers, including poor reading order, missing document structure, inaccessible form fields, and images without text alternatives.
This is an important point for municipalities, nonprofits, educational institutions, and organizations that maintain large collections of downloadable documents.
A website can have excellent HTML accessibility yet still create significant barriers through inaccessible documents.
How Do You Know if Your Website Is Accessible?
You test it.
But the quality of the answer depends heavily on how you test.
A useful accessibility assessment generally combines automated testing, manual evaluation, and, where appropriate, testing with assistive technology.

Automated Accessibility Testing
Automated testing tools can scan pages quickly and identify many repeatable technical problems.
They may identify issues such as color contrast, missing attributes, improper HTML relationships, form labels, and other machine-detectable conditions.
That makes automation especially valuable, particularly when monitoring a large website.
But automation has an important limitation:
A computer can more easily identify whether an image has alt text than determine whether that alt text is actually useful.
The same problem persists throughout accessibility testing. A scanner can identify certain technical conditions, but it doesn’t necessarily understand context or the user’s objective.
Manual Accessibility Testing
Human evaluation can identify problems automated tools miss.
Is the heading structure logical?
Does the link text make sense in context?
Can someone understand an error message?
Does keyboard navigation follow a sensible sequence?
Does the alternative text communicate what the image actually contributes to the page?
Those questions require judgment.
Assistive Technology and User Testing
Testing with keyboards, screen readers, magnification, and other assistive technologies provides another layer of insight.
Ultimately, accessibility isn’t about satisfying software. It’s about whether people can use the website successfully.
That’s why one of the most important principles in accessibility is:
Passing an automated accessibility scan is not the same as having an accessible website.
Passing an automated accessibility scan is not the same as having an accessible website.

What Is Website Accessibility Remediation?
An accessibility audit identifies barriers, and remediation is the process of fixing them.
That may involve changes to:
- HTML structure
- JavaScript
- Navigation
- Images and alternative text
- PDFs
- Third-party integrations
- CSS
- WordPress themes and templates
- Forms
- Plugins
- Video and audio
- Page content
Not every accessibility issue has the same impact.
A decorative image with imperfect markup and a checkout button that can’t be activated with a keyboard are both accessibility issues, but they don’t create equivalent barriers.
A practical remediation program therefore needs priorities.
At Visionary, we think about that process as a continuing cycle:
Assess → Prioritize → Remediate → Validate → Monitor → Maintain
First, identify where barriers exist. Then prioritize the problems that most seriously interfere with the user experience. Fix those problems, preferably in the underlying code or content. Retest the work. Continue monitoring as the website changes.
That approach also enables organizations with large or older websites to address accessibility systematically rather than assuming everything must be rebuilt overnight.
What About Accessibility Widgets and Overlays?
This is one of the most debated areas of website accessibility.
Accessibility widgets and overlays generally add a layer of technology to an existing website. Depending on the product, they may offer visitor controls for adjusting text, contrast, or spacing; detect certain accessibility problems; or modify the website at runtime.
Those capabilities can be useful.
The mistake is assuming the presence of a widget means accessibility has been solved.
Runtime technology may alter how a page is presented without resolving every accessibility issue in the website’s underlying source code. Automated systems also have difficulty evaluating context, meaning, and complex user interactions.
Documents, third-party applications, embedded services, and unusual functionality may require separate attention.
Visionary has firsthand experience of this evolution.
For several years, we recommended an accessibility overlay to clients as a practical way to address accessibility concerns on established websites. As the industry evolved and we gained more experience with the limitations of that model, our thinking changed.
We explain that experience candidly in Set It and Forget It Was Never the Whole Story: Our Honest Reckoning With Web Accessibility.
Our position today is straightforward:
Accessibility tools can be useful components of an accessibility strategy, but they should not be confused with the strategy itself.
Automation isn’t disappearing. In fact, artificial intelligence is likely to become even more useful for accessibility.
But the direction of the industry increasingly points toward using automation to find problems, assist developers, recommend fixes, and monitor accessibility, while correcting barriers at the source whenever practical.
That’s a very different proposition from installing a script and considering the job finished.
Accessibility Is a Practice, Not a Product
This may be the single most important idea in this guide.
A website isn’t accessible because it has an accessibility icon in the corner.
It isn’t accessible because someone purchased a particular software subscription.
It isn’t accessible because an automated scanner produced a good score.
And an accessibility statement doesn’t make an inaccessible website accessible.
Sustainable accessibility comes from a combination of:
Accessible Design + Accessible Development + Testing + Remediation + Accessible Content + Monitoring
Technology fits throughout that process.
Automated testing can uncover problems at scale. AI can help developers identify and potentially remediate code-level accessibility issues. Monitoring systems can alert teams when new barriers arise. User-facing accessibility tools can provide additional controls and personalization.
But the technology supports the practice. It doesn’t replace it.
That’s an important evolution in how the web industry thinks about accessibility.
Our earlier article, The Critical Need for Website ADA Compliance in Your Digital Strategy, looked at why accessibility belongs alongside SEO, UX and other core digital considerations. The next step is recognizing that accessibility must become part of a website’s normal lifecycle.
Accessibility Should Begin Before Development
The most efficient accessibility issue to remediate is often the one you never introduce.
That’s why accessibility should begin in website planning and design.
Designers can establish accessible color combinations and typography before a developer writes a line of code. Information architects can design clear navigation. Designers can plan focus states and interaction patterns. Developers can use semantic HTML and build reusable, accessible components.
Forms can be built correctly from the beginning rather than repaired later.
Content teams can establish standards for headings, alternative text, link text, PDFs, and multimedia before hundreds of pages are populated.
Accessibility can also become part of quality assurance before launch.
This doesn’t mean a newly built website will never have an accessibility issue. Websites are complex, and accessibility requires ongoing evaluation.
But building accessibility into the foundation is generally far more efficient than retrofitting it after inaccessible patterns have been duplicated across hundreds of pages.
It also produces better design.
As we discuss in The Balance Between Form and Function: A Web Designer’s Dilemma, good website design isn’t a choice between aesthetics and usability. Design succeeds when visual communication and functionality complement one another.
Accessibility belongs in that equation from the beginning.
If you’re planning a website redesign, don’t wait until the end of development to conduct your first accessibility review. Fixing one component early is much easier than repairing the same problem on 200 pages after launch.
Why Website Accessibility Requires Ongoing Maintenance
Suppose you launch a website that has been carefully designed, developed, and tested for accessibility.
Six months later, someone uploads a PDF that is inaccessible.
A marketing manager publishes an important infographic without a meaningful text alternative.
A new third-party scheduling application is embedded.
A plugin update changes how a form works.
Someone creates a new button style with insufficient contrast.
A video is published without captions.
The original website didn’t suddenly become poorly built. The digital environment simply changed.
That’s normal.
Modern websites are living systems. Content is added, software is updated, and integrations change continuously.
Accessibility therefore needs to become part of normal website governance.
That may include scheduled automated scans, periodic manual reviews, accessibility checks during major website changes, standards for content publishers and training for the people responsible for maintaining the site.
This is also why documentation (proof of effort) matters.
Maintaining records of audits, identified problems, remediation work, training, and monitoring builds institutional knowledge. It enables an organization to see what has been addressed and what still requires attention.
Our experience dealing with an actual accessibility demand letter reinforced the value of having a documented process. We discuss that experience in A Wake-Up Call on ADA Website Compliance.
The lesson isn’t that documentation replaces accessibility.
It doesn’t.
The lesson is that you should manage accessibility deliberately rather than reactively.
How Accessibility Relates to SEO and User Experience
Accessibility, search engine optimization, and user experience aren’t the same discipline, but they often reward similar website practices.
Consider semantic HTML.
Properly structured headings help screen-reader users understand a page. They also make the relationships between topics clearer to search engines and other systems interpreting the content.
Descriptive alternative text can convey important visual information to users who cannot see an image and also help search systems understand what the image represents.
Clear navigation helps people find information while making the website structure easier for crawlers and other automated systems to interpret.
Descriptive links, readable content, and logical information architecture share overlapping benefits.
But accessibility shouldn’t be pursued because someone hopes it will increase a Google ranking.
The primary purpose of accessibility is access.
Any SEO benefit is secondary.
This distinction matters even more as websites increasingly need to communicate not only with traditional search engines but also with AI systems that interpret content semantically. Well-structured information has value across many digital channels, but that doesn’t make accessibility an SEO tactic.
Accessibility is first and foremost about people.
For a broader look at the business case, listen to our Digital Horizons podcast, Turning ADA Compliance from Threat to Advantage.
Building a Sustainable Website Accessibility Program
If accessibility isn’t a one-time project, what should an organization do?
A practical accessibility program doesn’t need to begin with perfection. It needs to begin with a process.
1. Establish an Accessibility Standard
Determine which accessibility standard your organization will work toward.
For many organizations, WCAG Level AA serves as the practical benchmark, though applicable requirements should be determined based on the organization’s circumstances and legal obligations.
2. Audit the Website
Use automated tools to identify machine-detectable problems, then supplement them with manual evaluation.
For important services and user journeys, consider testing with relevant assistive technologies.
3. Prioritize Barriers
Don’t treat every issue as equally urgent.
Start with barriers that prevent users from accessing important information or completing essential tasks.
4. Remediate at the Source
Whenever practical, correct accessibility problems in the website’s underlying code, templates, components and content.
Fixing the source also helps prevent the same problem from appearing repeatedly.
5. Validate the Work
A fix isn’t complete simply because someone changed the code.
Retest it.
Confirm that the barrier has actually been removed and that the correction hasn’t created another problem.
6. Establish Accessible Content Standards
Develop straightforward rules for people publishing content.
How should headings be used?
Who writes image alt text?
How are PDFs reviewed?
Who ensures videos receive captions?
Accessibility becomes much easier to sustain when responsibilities are clear.
7. Train Website Contributors
Developers aren’t the only people who affect accessibility.
Designers, marketers, content editors, administrators, and outside vendors can all introduce or prevent accessibility problems.
Training doesn’t need to turn everyone into a WCAG expert. It should help each person understand the accessibility decisions relevant to their role.
8. Monitor the Website
Automated monitoring is particularly valuable here.
New content and website changes can introduce detectable accessibility problems. Regular scanning can help teams identify regressions before they accumulate.
9. Reassess Periodically
Standards evolve. Websites evolve. Technology evolves.
WCAG 2.2 added new success criteria beyond WCAG 2.1, and accessibility technologies continue to change rapidly.
Periodic accessibility reviews keep the program aligned with those changes.
The objective isn’t to reach a magical moment when accessibility work is permanently finished.
It’s to make accessibility part of responsible website management.
From Legal Risk to Better Digital Strategy
Many organizations first discover website accessibility because something goes wrong.
They receive a demand letter.
A customer complains.
A government procurement document suddenly requires WCAG compliance.
An accessibility scan produces hundreds of errors.
That can make accessibility feel like another compliance burden.
We’ve seen it differently over time.
The legal risk is real, and organizations shouldn’t ignore it. We’ve explored that side of the issue extensively in ADA Website Lawsuits Are Rising: Here’s How to Protect Your Business.
But fear is a poor foundation for digital strategy.
The more useful goal is to build websites that more people can actually use.
That means creating clear content, building intuitive navigation, making forms easier to complete, designing interfaces that don’t unnecessarily exclude people, and maintaining the website so those qualities don’t gradually erode.
Do those things consistently and accessibility stops looking like an isolated compliance project.
It becomes part of building a better website.
And that’s where our thinking has ultimately landed:
Accessibility is not a project with a finish line. It’s an ongoing part of responsible website management.
Frequently Asked Questions About Website ADA Compliance
Does the ADA require websites to be accessible?
The ADA prohibits discrimination against people with disabilities, and digital accessibility is an important part of ADA compliance. The specific legal framework varies by organization type. State and local governments have explicit federal web accessibility requirements under Title II. The application of Title III to private-sector websites has evolved through enforcement actions and court decisions and can vary by jurisdiction. Organizations should seek legal advice regarding their specific obligations.
What is WCAG?
WCAG stands for Web Content Accessibility Guidelines. Developed by the World Wide Web Consortium (W3C), WCAG provides technical criteria to make websites and other digital content more accessible to people with disabilities. WCAG is organized around four principles: content should be perceivable, operable, understandable, and robust.
What is WCAG 2.2 Level AA?
WCAG 2.2 is the latest version of the W3C Web Content Accessibility Guidelines. WCAG includes three conformance levels: A, AA, and AAA. Level AA includes all applicable Level A and Level AA success criteria and is commonly used as an organizational accessibility target. W3C encourages the use of the latest WCAG version.
What’s the difference between ADA compliance and WCAG compliance?
The ADA is a U.S. civil rights law that prohibits discrimination based on disability. WCAG is a technical accessibility standard developed by W3C. WCAG is often used as a framework for evaluating whether digital content is accessible, but the terms “ADA compliant” and “WCAG conformant” don’t mean exactly the same thing.
How do I know if my website is accessible?
Start with an accessibility assessment that combines automated scanning with manual review. Important website functions should also be tested for keyboard accessibility and, where appropriate, for compatibility with assistive technologies such as screen readers. Automated testing alone cannot identify every accessibility barrier.
Can an accessibility widget make my website ADA compliant?
Accessibility widgets can offer useful features and may address some accessibility barriers, but installing a widget alone should not be taken as proof that a website meets all applicable accessibility requirements. Accessibility also involves underlying code, content, documents, third-party integrations, and user interactions, which may require human evaluation and native remediation.
For more background on how our own thinking about overlays changed, read Set It and Forget It Was Never the Whole Story.
What is website accessibility remediation?
Accessibility remediation is the process of correcting barriers identified during accessibility testing. Remediation can involve HTML, CSS, JavaScript, templates, navigation, forms, images, documents, multimedia, and content. Native remediation addresses issues in the underlying website or content rather than relying exclusively on a runtime layer.
How much does website ADA remediation cost?
There is no standard cost because remediation depends on the website’s size, age, technology, complexity, and existing accessibility problems. A relatively small, modern website may require only limited corrections, while an older site with hundreds of pages, custom functionality, and large document libraries may require a phased remediation program. An accessibility assessment is usually the best starting point for determining scope.
Does website accessibility require ongoing monitoring?
Yes. New content, software updates, plugins, documents, and third-party integrations can introduce accessibility barriers even after an existing site has been remediated. Regular automated monitoring, combined with periodic manual review, helps identify accessibility regressions as the website evolves.
Do PDFs need to be accessible?
PDFs can create accessibility barriers independently of the website that links to them. Accessible documents may require appropriate headings, reading order, alternative text, table structure, and properly labeled form fields. Organizations that publish large numbers of downloadable documents should include document accessibility in their broader accessibility program.
Is WordPress automatically ADA compliant?
No. WordPress can be used to build accessible websites, but accessibility depends on the theme, templates, plugins, custom development, design choices, and content entered into the system. An accessible CMS foundation does not guarantee that every website built with it, or every page subsequently published, will remain accessible.
Can automated accessibility testing find every problem?
No. Automated tools are excellent at quickly and consistently identifying certain technical accessibility issues, but they cannot reliably evaluate issues involving meaning, context, and usability. Automated testing should be combined with manual evaluation and appropriate assistive-technology testing.
Making Accessibility Part of Your Website Strategy
Website accessibility encompasses design, development, content, documents, third-party applications, and ongoing website management. That complexity is exactly why accessibility shouldn’t be reduced to a product purchase or a once-a-year scan.
Start by understanding where your website stands.
Identify the barriers that matter most. Correct them. Validate the work. Establish standards that reduce the likelihood of reintroducing the same problems. Then continue monitoring as your digital presence evolves.
The tools will continue to evolve. Artificial intelligence will improve. Testing will become more sophisticated. Development platforms will become better at identifying accessibility problems before they reach production.
Those advances are welcome.
But the principle underneath them isn’t likely to change:
Accessibility is a practice, not a product.
Is Your Website Accessible?
Visionary helps organizations evaluate website accessibility, identify barriers, remediate accessibility issues and establish practical processes for maintaining accessibility over time.