A customer is ready to request a quote, register for a program, or pay an invoice. Then the keyboard focus disappears, a form error is announced only by color, or a button has no useful label. That is not a minor website issue. It is a barrier between your organization and someone who needs to do business with you. A website accessibility audit checklist gives your team a structured way to find those barriers before they cost trust, engagement, or opportunity.
For businesses and government organizations, accessibility work also improves everyday usability. Clear headings help busy visitors scan a page. Well-labeled forms reduce submission errors. Keyboard-friendly navigation supports people with motor disabilities, but it also helps power users move faster. The goal is not to check a box. It is to make your digital presence work for more people, in more situations.
Start With Scope, Ownership, and Standards
An effective audit begins before anyone tests a page. Decide what is included: your main website, customer portal, downloadable PDFs, online forms, embedded scheduling tools, payment flows, and campaign landing pages. A five-page marketing site can often be reviewed page by page. A larger website should be sampled by template and by critical user task, such as finding a service, completing an application, creating an account, or contacting support.
Identify who owns the fixes. Website accessibility commonly crosses departments. Marketing may manage content, a web developer may control templates, IT may oversee platforms, and a vendor may operate a third-party form or booking tool. Without clear ownership, an audit can become a list of findings that nobody is equipped to resolve.
Use the Web Content Accessibility Guidelines, commonly called WCAG, as a practical reference point. Many organizations use WCAG 2.1 or 2.2 Level AA as their working target, but the right standard can depend on your organization, contracts, industry, and applicable requirements. If legal obligations are a concern, discuss them with qualified counsel. An audit can identify technical barriers, but it is not legal advice or a guarantee of compliance.
Website Accessibility Audit Checklist: Core Tests
Automated scanners are a useful starting point, especially for finding missing image text, low-contrast color combinations, unlabeled form controls, and structural code issues. They do not tell the whole story. A scanner may report that an image has alternative text, for example, without determining whether that text is meaningful. Manual testing is where real user experience becomes visible.
Check page structure and navigation
Every page needs a logical heading structure. There should generally be one clear page topic at the top, followed by headings that organize the content in order. Headings should not be selected simply because they look bigger or bolder. They create a map for people using screen readers and improve content clarity for everyone.
Test every interactive element with a keyboard alone. Starting at the address bar, use the Tab, Shift + Tab, Enter, Spacebar, and arrow keys as needed. You should be able to reach navigation links, menus, buttons, form fields, pop-ups, and the footer in a sensible order. A visible focus indicator must show where the user is at all times. If a menu opens, dialog appears, or video starts, focus should behave predictably and never become trapped.
Also look for a skip link near the beginning of the page. It allows keyboard users to bypass repeated navigation and move directly to the main content. It may not be visually prominent until a user tabs to it, but it should work reliably.
Review color, text, and visual communication
Color should reinforce information, not carry it alone. A form field cannot rely only on a red outline to signal an error. Pair color with clear text, such as “Enter a valid email address,” and connect that message to the field that needs attention.
Check contrast for normal-size text, large text, icons, buttons, and charts. Brand colors can create tension here. A light accent color may look appealing in a style guide but fail when used for body text or an important call to action. The solution is not necessarily abandoning the brand palette. Often, a slightly darker shade, stronger text weight, or improved button treatment preserves the identity while improving readability.
Text should remain usable when visitors zoom in. At higher zoom levels, content should not overlap, disappear, require two-dimensional scrolling, or leave key controls unreachable. Avoid putting essential instructions only inside images, and do not use placeholder text as the sole label for a form field.
Evaluate images, links, and buttons
Alternative text should communicate the purpose of a meaningful image in its context. A photo beside a customer story may need a brief description. A chart may require a longer explanation in nearby text. Decorative images should be ignored by assistive technology so they do not create noise.
Review link text and button labels in isolation. “Learn more” appears harmless until a screen reader user encounters five of them in a row. Better labels explain the destination or action: “Learn more about payroll services” or “Download the event registration form.” Buttons should describe what happens when selected, not merely how they look.
Be especially careful with icons. A magnifying glass, social icon, or close button may be familiar visually, but it still needs an accessible name. Tooltips alone are not enough because they may not appear for keyboard or touch users.
Test forms and transactions from start to finish
Forms are often where accessibility problems become business problems. Each field needs a persistent, programmatic label. Required fields should be identified in more than one way, and instructions should appear before a user needs them. If formatting is required for dates, account numbers, or passwords, state the expectation clearly.
Submit forms with blank fields and intentional errors. Are messages specific? Do they identify the problem and offer a path to correct it? Does focus move to an error summary or first invalid field in a way that makes sense? For financial, legal, or data-submission steps, give users a meaningful chance to review, correct, and confirm information before final submission.
Review multimedia, documents, and embedded tools
Videos with spoken content need accurate captions. When visual details are essential but not stated aloud, audio description or a written alternative may be appropriate. Audio-only content needs a transcript. Avoid auto-playing media, particularly when users cannot easily pause or stop it.
Do not let PDFs become the forgotten corner of your website. If a document is necessary for an application, policy, agenda, or public notice, it should have a logical reading order, real headings, tagged content, accessible tables, and a meaningful document title. In some cases, publishing the information as an accessible web page is easier to maintain and more useful than relying on a PDF.
Finally, test third-party tools in the actual context where visitors use them. A website can have excellent navigation and still fail a visitor at the embedded appointment scheduler, map, chat widget, payment screen, or applicant portal. Vendor tools may have limitations, but they remain part of the experience your organization provides.
Use Assistive Technology and Realistic Tasks
A quick screen reader review can uncover issues that code scans miss. Use at least one common screen reader and listen for page titles, headings, landmarks, link labels, form prompts, errors, and status messages. You do not need to become an assistive technology specialist to learn a great deal from completing a simple task without looking at the screen.
Test representative tasks rather than isolated pages. Can someone find a location, compare services, submit a contact form, download a required document, or complete a purchase? A homepage might perform well while the path that matters most remains difficult or impossible.
When resources allow, involve people with disabilities in usability testing. Their feedback adds context that technical testing cannot fully provide. It can reveal whether a technically conforming experience is still confusing, slow, or unnecessarily demanding.
Turn Findings Into an Action Plan
A useful audit report does more than catalog issues. Record the page or component, the barrier, who is affected, the relevant success criterion or standard, a recommended fix, and the owner. Include screenshots or short reproduction steps so a developer or content manager can act without guessing.
Prioritize by impact and frequency. A keyboard trap in a checkout flow, inaccessible login form, or missing labels in a required application should rise to the top. Repeated template issues also deserve early attention because one component fix may improve dozens of pages. Minor visual refinements still matter, but they should not delay removal of barriers that prevent people from completing essential tasks.
Build accessibility into your regular workflow after the initial audit. Add checks to design reviews, content publishing, software updates, procurement decisions, and quality assurance. Automated testing can run routinely, while manual keyboard and form testing should be part of every significant release. This approach is more practical and less expensive than treating accessibility as a one-time cleanup project.
Accessibility is a service decision as much as a technical one. When your website respects how different people read, navigate, communicate, and complete tasks, it reflects the same care you want customers, residents, partners, and employees to experience everywhere else. Start with the highest-impact path, fix it well, and let that standard guide every new page that follows.