Where do people encounter barriers on a website?
People report barriers in navigation, forms and interactive controls. Accessibility checks should cover real tasks and assistive technology.
Read the key findingsTL;DR
Make headings and controls useful. In WebAIM’s 2026 survey, 67.8% of screen-reader respondents said they first navigate a long page using headings.
Screen-reader navigation preferencesCheck real barriers and choices. In an AFB survey, 43.7% of 355 respondents answering a website question said they had done business elsewhere after encountering an inaccessible site.
Reported website barriersCheck forms for common accessibility problems. WebAIM’s 2026 audit found missing form labels on 51% of the homepages it tested. Give each field a clear label and try submitting it with a keyboard and screen reader.
The million-homepage accessibility audit
- Screen-reader survey respondents67.8%
In WebAIM’s 2026 survey, headings were the most common first step when screen-reader users wanted to find something on a long page.
See how it was measuredAccessibility is part of whether customers can complete a task
People use headings, links, buttons, forms and menus to understand a page and reach the service they need. If a control has no useful label, cannot be reached by keyboard, or changes unexpectedly, the customer may not be able to complete an enquiry or booking.
The evidence here comes from a screen-reader user survey and a disability survey about website and app barriers. It describes respondents’ experiences and preferences, not the percentage of all sites that fail or the direct revenue impact of a fix.
Screen-reader user survey
Headings are an important way respondents navigate long pages
67.8% of respondents said they first navigate a long page using its headings. 88.3% found heading levels very or somewhat useful.
- Screen-reader survey respondents67.8%
WebAIM surveyed screen-reader users in July and August 2026 and received 1,780 valid responses. The online survey was uncontrolled and the total respondents for individual questions varied.
The survey records screen-reader users’ preferences and experiences. Its self-selected sample does not represent all users with disabilities, and it does not audit sites or measure business conversions.
Use headings in a logical order so visitors can scan by section. Give links and buttons clear names, ensure keyboard focus is visible, and announce form errors in a way screen readers can detect. Test with a screen reader as well as visual and keyboard checks.
WebAIM, Screen Reader User Survey #11 Results (2026). Read the survey results
Disability survey
Some respondents said website barriers changed where they did business
Among the 355 respondents answering the website coping question, 43.7% reported doing business elsewhere.
The page also records frequent mentions of unlabeled buttons or links, screen-reader navigation problems and poor contrast. These are counts of mentions, not audited failure rates. The reported choice is a survey response among people with disabilities, not a general-population conversion estimate.
For an enquiry path, check that labels remain available to assistive technology, the form works by keyboard, errors identify what to correct and confirmation is announced. Keep website and mobile-app issues separate when recording findings.
American Foundation for the Blind, Digital Inclusion Survey series. Report date not stated on the page. Read the survey findings
Automated audit of one million homepages
Missing form labels and low contrast were common
WebAIM’s 2026 scan found missing form labels on 51% of homepages. Low-contrast text and images without alternative text were also common.
- Low-contrast text83.9%
- Images with missing alternative text53.1%
- Missing form input labels51%
WebAIM used its WAVE tool to find accessibility issues it could detect automatically. The percentages refer to homepages with at least one issue of each kind. A manual test can reveal additional barriers, such as a booking calendar that a customer cannot use with the keyboard.
Start by checking the form customers use to request work. Confirm every field is named, the keyboard moves in a sensible order and errors explain how to finish the request. Then test the same journey with a screen reader.
WebAIM, The WebAIM Million 2026. Read the 2026 accessibility audit
Check whether people can complete the journey.
Accessible pages let more people read information, navigate controls and submit a request using the tools that work for them.
- Choose a core task such as finding a service area, calling, requesting a quote or booking a time.
- Run a measured audit with keyboard navigation, a screen reader and phone zoom. Write down the pages, setup, barriers and task outcomes.
- Fix the barriers, repeat the same checks and separately monitor completed enquiries or bookings over comparable periods.
A repeatable check shows whether the barrier was removed. Customer outcomes can then be tracked without claiming more than the evidence supports.
Explore web design and development