NEW: AudioEye launches Agentic Audits and SDK MCP
Read more20 Common Website Accessibility Issues (and How to Fix Them)
The most common website accessibility issues are low contrast text, missing alt text, missing form labels, empty links, empty buttons, and missing document language, which account for 96% of errors. Most are quick to fix, but issues like keyboard access and focus order often take expert testing to find. Below, we'll cover all 20 issues and how to fix each one.
Author: Jeff Curtis, Sr. Content Manager
Published: 10/07/2026
)
The accessibility issues on your website probably aren’t the ones you can see. They’re in the code behind the page: missing alt text, unlabeled form fields, and buttons that a screen reader can’t name. And they’re far more common than most site owners realize. When WebAIM analyzed the top one million homepages, it found detectable failures on 95.9% of them(opens in a new tab).
For the more than 70 million Americans living with a disability, those errors add up to barriers on most of the sites they visit. The good news is that most of them come from the same short list of problems.
The most common website accessibility issues are low contrast text, missing alt text, missing form labels, empty links, empty buttons, and missing document language, which together account for 96% of all errors WebAIM detected. Most are simple oversights rather than bad intentions, which makes them easy to fix once you know where to look.
Below, we’ll break down 20 common accessibility issues, why each one matters, and how to fix them.
The Most Common Accessibility Issues in 2026
Six types of errors account for 96% of all accessibility issues detected in the WebAIM Million 2026 report(opens in a new tab), which tests the home pages of the top one million websites each year:
The picture is getting worse, not better. The average homepage had 56.1 errors in 2026, up 10.1% from 2025, reversing several years of slow improvement, and WebAIM points to growing page complexity as a likely driver.
Identifying Accessibility Issues
Accessibility issues are any issues or barriers that prevent people with disabilities from using a website easily or effectively. These can range from missing image descriptions for screen reader users to interactive elements that can’t be accessed with a keyboard. And while some issues are obvious, many are subtle, hidden in the structure or behavior of a site that seems functional on the surface.
The Role of Accessibility Tools and People
Automated accessibility testing tools, like the free AudioEye Website Accessibility Checker, are a strong starting point because they flag common Web Content Accessibility Guidelines (WCAG) violations, such as missing form labels and non-descriptive link text.
But technology can only get you so far. An automated tool can tell you whether an image has alt text. Still, it can’t judge whether that alt text is actually helpful, whether a screen reader experience is intuitive, or whether information is presented in a logical order. Those questions take human judgment, which is why accessibility audits and testing by real users matter.
When Good Intentions Go Wrong
Many accessibility issues stem from well-meaning efforts to be accessible without the right knowledge. Describing every decorative image in detail clutters the experience for assistive technologies, and ARIA (Accessible Rich Internet Applications), which is meant to improve accessibility, can create new problems for assistive technology when it’s misused. Getting the details right matters as much as adding accessibility features in the first place.
Top 20 Accessibility Issues
Top 6 Most Common Accessibility Issues
These six issues show up on more websites than any others, according to the 2026 WebAIM report(opens in a new tab). They’re also the ones automated testing catches most reliably, so they’re the best place to start.
1. Low Contrast Text
Low contrast text is the most common accessibility issue on the web, found on 83% of homepages. Success Criterion 1.4.3 (Level AA)(opens in a new tab) requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, so people with low vision or color blindness can read it.
How to fix it: Test your color combinations with a color contrast checker before going live. If you’re unsure, err on the side of clarity since your content should be easy to read in any context.
2. Missing or Unhelpful Alt Text
Missing alt text is the second most common accessibility issue, affecting 53.1% of homepages. Success Criterion 1.1.1 (Level A)(opens in a new tab) requires a text alternative for all non-text content, including images, charts, and graphics. Alt text only helps screen reader users when it’s meaningful, not a vague label like “graphic.”
How to fix it: Write concise descriptions that explain each image’s purpose. If an image is purely decorative, use an empty alt attribute (alt=””) so screen readers skip it.
3. Missing Form Labels
Missing form labels affect 51.0% of homepages. Success Criteria 1.3.1(opens in a new tab) and 3.3.2(opens in a new tab) (Level A) require labels that assistive technology can read, and a visible label that isn't programmatically connected to its field still leaves screen reader users guessing.
How to fix it: Wrap every input in a label element or connect it with aria-labelledby, and write clear, accessible error messages. For checkout forms, see our guide to cart and checkout accessibility.
4. Empty or Vague Links
Empty links appear on 46.3% of homepages, and vague link text like “click here” causes similar problems. Success Criterion 2.4.4 (Level A)(opens in a new tab) requires each link’s purpose to be clear, which matters because many screen reader users jump from link to link out of context.
How to fix it: use link text that describes the destination, like “download the accessible design guide,” and give icon-only links an accessible name.
5. Empty Buttons
Empty buttons appear on 30.6% of homepages, usually icon-only buttons like search or close. Success Criterion 4.1.2 (Level A)(opens in a new tab) requires that every interactive element has a name; without one, a screen reader announces it only as “button.”
How to fix it: Give every button a text label, or add visually hidden text or an aria-label such as “Close menu.”
6. Missing Document Language
Missing document language affects 13.5% of homepages, violating Success Criterion 3.1.1 (Level A)(opens in a new tab), which requires each page’s language to be set in the code since screen readers use it to choose the right pronunciation.
How to fix it: Add a lang attribute to the HTML element, such as lang="en", and mark passages in other languages with their own lang attribute.
Accessibility Issues Automated Scans Often Miss
The issues in this section are harder to catch automatically because they depend on how a page behaves, not just how it's coded. Each one includes a quick way to test it yourself.
7. No Keyboard Access
A website isn't accessible if it can't be used without a mouse, and Success Criterion 2.1.1 (Level A)(opens in a new tab) requires all functionality to work with a keyboard. Many people with vision or motor disabilities rely on keyboard navigation, and sliders, dropdowns, and modals are common trouble spots.
How to fix it: Use native HTML elements so interactive features work with a keyboard by default.
How to test it: Set your mouse aside and press Tab through the page. You should be able to reach and use everything.
8. Illogical Focus Order and Reading Sequence
When the focus or reading order doesn't match the visual layout, keyboard and screen reader users lose their place. Success Criteria 2.4.3(opens in a new tab) and 1.3.2(opens in a new tab) (Level A) require an order that preserves meaning, which often breaks when CSS rearranges content visually.
How to fix it: Match the Document Object Model (DOM) order to the visual order by adjusting the HTML rather than relying on CSS.
How to test it: Tab through the page and listen with a screen reader. Both should follow the layout.
9. Missing Focus Indicators
Keyboard users need to see which element is selected, and Success Criterion 2.4.7 (Level AA)(opens in a new tab) requires a visible focus indicator. Many sites remove the browser's default outline for visual reasons and never replace it.
How to fix it: Style a clear, high-contrast focus state with CSS instead of removing it.
How to test it: Press Tab and watch for a visible highlight on every element.
10. Inaccessible Navigation Menus
Inaccessible navigation stops users from reaching the rest of your site. Success Criteria 2.1.1(opens in a new tab) and 4.1.2(opens in a new tab) (Level A) require menus to work with a keyboard and be identified correctly, which fails when menu items use div or span elements instead of proper links.
How to fix it: Use semantic link elements for navigation. ARIA roles can help, but they don't replace correct HTML.
How to test it: Open every menu with only a keyboard, and check that a screen reader announces each item as a link.
11. Misused ARIA
Misused ARIA often causes more problems than it solves: pages using ARIA averaged 59.1 errors in the WebAIM Million 2026 report, compared to 42 on pages without it. Success Criterion 4.1.2 (Level A)(opens in a new tab) requires accurate names and roles, and redundant ARIA attributes, such as role="button" on a button, can create confusing announcements for screen readers.
How to fix it: Use semantic HTML first and add ARIA only when native elements can’t do the job.
How to test it: Navigate custom components with a screen reader and listen for repeated or misleading announcements.
12. Missing Semantic Structure and Headings
When a page's structure is only visual, screen reader users can't navigate it efficiently. Success Criteria 1.3.1 (Level A)(opens in a new tab) and 2.4.6 (Level AA)(opens in a new tab) require that structure be conveyed in the code and that headings describe their content; semantic HTML headings (h1 through h6) let users jump between sections.
How to fix it: Use real headings in order, without skipping levels, and make each one describe its section.
How to test it: Check the page’s heading outline with a screen reader or browser extension. It should read like a table of contents.
13. Inaccessible Tables and Infographics
Data tables, charts, and infographics leave out information for screen reader users when they aren't built accessibly. Success Criterion 1.3.1 (Level A)(opens in a new tab) requires table relationships to be conveyed in the code, and charts need a text equivalent when their message is purely visual.
How to fix it: Mark up data tables with the elements and scope attributes, and provide text summaries for charts and infographics.
How to test it: Read a table with a screen reader and check that each cell is announced with its header.
14. Text That Can’t Be Resized
People with low vision often enlarge text, and Success Criterion 1.4.4 (Level AA)(opens in a new tab) requires text to resize to 200% without losing content or functionality. Fixed-size layouts cause enlarged text to overlap or get cut off.
How to fix it: Use relative units like rem or em, and build layouts that reflow as text grows.
How to test it: Zoom your browser to 200% and check that everything is readable and usable.
15. Missing Captions
Videos without captions exclude people who are deaf or hard of hearing, and Success Criterion 1.2.2 (Level A)(opens in a new tab) requires captions for prerecorded videos with audio. Good captions also identify speakers and meaningful sounds.
How to fix it: Add accurate captions and a transcript, and review auto-generated captions before relying on them.
How to test it: Play each video with the sound off and confirm you can follow it.
16. Inaccessible PDFs and Documents
Accessibility requirements apply to documents, too, and PDFs like reports and forms often lack headings, tags, alt text, and a logical reading order. Because many checkers focus on web pages, these issues often go undetected.
How to fix it: Fix documents to meet PDF/UA and WCAG standards, or publish the content as an accessible web page.
How to test it: Run documents through a PDF accessibility checker and read them with a screen reader.
17. Unnecessary Navigation Instructions
Instructions like "Use the Tab key to navigate this page" usually add clutter for assistive technology users, who already know how to use their tools, and can be confusing if they don't match how those tools work.
How to fix it: Follow accessibility best practices so the interface doesn't need extra guidance.
How to test it: Navigate with a screen reader and note instructions that repeat what the tool already announces.
Newer WCAG 2.2 Accessibility Issues
Three common WCAG 2.2 issues are touch targets that are too small, forcing users to re-enter information, and help that moves from page to page. While WCAG 2.2 is the newer standard, it's worth checking that your digital content meets these standards to enhance accessibility and stay ahead of compliance.
18. Touch Targets that are too Small
Small buttons and links are hard to activate for people with motor disabilities, and Success Criterion 2.5.8 (Level AA)(opens in a new tab) requires targets of at least 24 by 24 CSS pixels or enough spacing to avoid accidental taps. Mobile layouts and crowded link lists are common trouble spots.
How to fix it: Size every control to at least 24 by 24 CSS pixels and add space between adjacent targets.
19. Making Users Re-Enter Information
Asking for the same information twice adds effort and errors, especially for people with cognitive disabilities. Success Criterion 3.3.7 (Level A)(opens in a new tab) requires that previously entered information be filled in or available for selection, which rules out a checkout that asks for the same address twice.
How to fix it: Carry information forward between steps or offer an option such as "Same as shipping address." Re-entering a password for security is an exception.
20. Inconsistent or Missing Help
Users who need support should find it in the same place on every page. Success Criterion 3.2.6 (Level A)(opens in a new tab) requires that help mechanisms, such as contact details or chat, appear in a consistent location, since users who are struggling may never find help that moves.
How to fix it: Keep help options in the same relative spot on every page, such as the header or footer.
Watch: The Most Common Accessibility Issues
How to Find Accessibility Issues on Your Website
Automated testing reliably finds issues like low contrast and missing labels, but problems like a confusing focus order or unhelpful alt text need expert testing to catch. Finding everything on this list takes both, especially since every content update can introduce new issues.
That’s the approach AudioEye takes, combining automated testing and fixes with Expert Audits from certified accessibility experts and members of the disability community, so automation handles scale and people handle the issues that require judgment. The result is 2.5x more accessibility issues detected (according to a 2026 Adience study), about 97% of issues resolved, and 400% more legal protection than automation-only solutions.
Curious which of these 20 issues are on your site? Run a free scan with AudioEye’s Website Accessibility Checker to find out. Then talk to an expert about the issues scans can’t catch.
Frequently Asked Questions
Share Article
)
)
)