Use this checklist when a live business website needs an accessibility pass before the next SEO, content, or conversion sprint. It is built for pages where visitors have to read the offer, open the menu, compare proof, complete a form, or contact the business.<\/p>\n\n\n\n\n\n\n\n
For most small-business audits, WCAG 2.2 Level AA is the practical target.[1]<\/sup> Treat Level A failures as blockers, Level AA failures as the normal acceptance bar, and Level AAA items as selective improvements for audiences that need them. Automated tools can help find patterns, but the real question is simpler: can a visitor finish the task without sight, a mouse, perfect dexterity, or perfect patience?<\/p>\n\n\n\n Before documenting every small issue, sort findings by the task they block. In real audits, the items teams most often under-prioritize are the same ones that stop leads: a pale call-to-action, a form with disappearing labels, a modal close button with no accessible name, or a chat widget that covers the focused field on mobile.<\/p>\n\n\n\n What to check:<\/strong> Start with text people must read before they can buy, book, call, or subscribe. That usually means the headline, offer copy, price note, testimonial, phone number, coupon code, form label, and button text.<\/p>\n\n\n\n How to test:<\/strong> WCAG 2.2 Contrast Minimum sets the Level AA contrast ratio at 4.5:1 for normal text and 3:1 for large-scale text.[1]<\/sup> Check the real design states, not just the default mockup. Hover text, disabled-looking buttons, form helper text, and sticky contact bars are common places where the contrast quietly falls below the bar.<\/p>\n\n\n\n Why it matters:<\/strong> Low contrast is not only a design preference. If the phone number, discount terms, or Book Now button fades into the background, the page is asking visitors to work harder before they can take the next step.<\/p>\n\n\n\n Do the same pass for non-text contrast. WCAG 2.2 uses a 3:1 contrast ratio for visual information such as button borders, input outlines, icons, and focus indicators.[1]<\/sup> A form can look clean and still fail if the active field outline disappears on a white background.<\/p>\n\n\n\n Mobile readability needs its own pass. Text should resize up to 200% without loss of content or function, pages should reflow at a width equivalent to 320 CSS pixels, and pointer targets should meet the 24 by 24 CSS pixel minimum unless an exception applies.[1]<\/sup> Check tap targets for phone numbers, calendar widgets, coupon close buttons, and sticky chat buttons.<\/p>\n\n\n\n What to check:<\/strong> Headings should describe the page in order, not just create big or small text. A service page usually needs one H1 for the main offer, H2 headings for major sections such as Services, Pricing, Reviews, and FAQ, and H3 headings only when they sit under an H2.<\/p>\n\n\n\n How to test:<\/strong> Scan the page without reading every paragraph. If the headings alone do not explain what the page offers and what comes next, the structure needs work. WCAG 2.2 says headings and labels should describe topic or purpose.[1]<\/sup><\/p>\n\n\n\n Links and buttons also need names that make sense out of context. Google Search Essentials points to descriptive words in prominent places such as the title, main heading, alt text, and link text.[2]<\/sup> For users, See commercial roof repair pricing<\/strong> is clearer than Click here<\/strong>.<\/p>\n\n\n\n Why it matters:<\/strong> Good structure helps people skim, screen-reader users jump between sections, and search systems understand the visible content. It is not a special trick for AI search or a substitute for helpful content; it is basic page clarity.[3]<\/sup>[8]<\/sup><\/p>\n\n\n\n Keyboard navigation is the fastest manual test in the audit. Press Tab from the browser address bar and confirm that the logo link, menu, search, main call-to-action, form fields, modal close buttons, and footer links can be reached in a logical order. The focus indicator should be visible, and it should not be hidden under sticky headers, cookie banners, or chat widgets.[1]<\/sup><\/p>\n\n\n\n If the broader audit also checks schema, keep it separate and tied to visible content. Structured data can help Google understand content and determine eligibility for search features, but it does not guarantee rankings and it cannot rescue a page whose visible offer, menu, or form is hard to use.[4]<\/sup><\/p>\n\n\n\n What to check:<\/strong> Meaningful images need useful text alternatives. A decorative divider can be ignored, but a before-and-after project photo, product image, staff headshot, chart, map, or coupon graphic needs alt text or nearby text that carries the same business meaning.<\/p>\n\n\n\n How to test:<\/strong> Ask what a visitor would miss if the image did not load or could not be seen. Google image guidance also recommends standard HTML image elements and alt text on the image element, not a CSS background image used as the only source of meaning.[5]<\/sup><\/p>\n\n\n\n Why it matters:<\/strong> An image can carry pricing proof, project quality, location context, or a limited-time offer. If that meaning is only visual, some visitors never receive it.<\/p>\n\n\n\n Forms deserve a slower pass because they sit at the bottom of many conversion paths. WCAG 2.2 requires labels or instructions when content needs user input, and expects useful suggestions when an input error is detected and a suggestion is known.[1]<\/sup> A placeholder alone is not a reliable label, and a red border without text is not a clear error.<\/p>\n\n\n\n The most common quote-form failures are predictable: phone fields that reject normal formatting without saying why, required fields marked only by color, error messages that say Invalid<\/strong> without naming the field, and success messages that appear after focus stays stranded near the submit button. Those are not small polish issues. They decide whether the visitor can complete the lead action at all.<\/p>\n\n\n\n A form that cannot be completed breaks more than accessibility. It breaks sales follow-up, local landing pages, paid traffic, and any measurement tied to the completed action because the visitor never reaches the point the business is trying to measure.<\/p>\n\n\n\n Prioritize accessibility findings by the task they block. A low-contrast footer copyright notice is different from a low-contrast Book Now<\/strong> button, and a missing decorative image alt attribute is different from a product comparison chart with no text equivalent.<\/p>\n\n\n\n Here is a concrete six-step workflow for a quote-request page, which is usually where accessibility and conversion problems meet.<\/p>\n\n\n\n The rule is simple: fix anything that blocks reading the offer, navigating the page, completing the form, or contacting the business before polishing visual details. If a finding affects every page template, schedule it ahead of one-off content edits.<\/p>\n\n\n\n WCAG 2.2 AA is a practical audit target, not a substitute for legal advice. W3C defines Level AA as satisfying all Level A and Level AA success criteria, which makes it a useful working bar for agencies, marketers, and site owners who need clear acceptance criteria.[1]<\/sup><\/p>\n\n\n\n No. PageSpeed Insights uses Lighthouse to provide lab diagnostics for categories including Accessibility, Performance, Best Practices, and SEO, but it cannot judge every real task.[6]<\/sup>[7]<\/sup> Keep the automated result, then manually test keyboard order, focus visibility, form errors, image meaning, and mobile readability.<\/p>\n\n\n\n Not when the problem blocks a key task. Link text, alt text, visible labels, error messages, contrast tokens, focus styles, and accessible button names can often be fixed before a full redesign. Template-level issues, such as inaccessible menus, sticky headers, or modals, should become design-system tickets.<\/p>\n\n\n\n Accessibility is not a magic ranking weight. The overlap is practical: descriptive titles, headings, alt text, and link text help search systems understand the page, and they help people do the same.[2]<\/sup> The safest SEO framing is still reader-first: make the useful content visible, specific, and easy to complete.[3]<\/sup><\/p>\n\n\n\nStart With The Blockers<\/h2>\n\n\n\n
Finding<\/th> Source<\/th> Business impact<\/th> Decision rule<\/th><\/tr><\/thead> Hero text or call-to-action text is below 4.5:1 contrast<\/td> WCAG 2.2 1.4.3[1]<\/sup><\/td> Visitors may miss the offer or next step<\/td> Fix before sending paid, email, or local traffic to the page<\/td><\/tr> Main button, menu, or form field cannot be reached with Tab<\/td> WCAG keyboard and focus criteria[1]<\/sup><\/td> Keyboard users cannot get to the task<\/td> Treat as a blocker for that template<\/td><\/tr> Focus is hidden under a sticky header, cookie banner, or chat widget<\/td> WCAG 2.2 focus criteria[1]<\/sup><\/td> Users can move through the page but cannot see where they are<\/td> Fix before polishing visual details<\/td><\/tr> Lead form uses placeholder text as the only label<\/td> WCAG 2.2 3.3.2[1]<\/sup><\/td> Users lose field meaning after typing<\/td> Fix before judging form conversion rate<\/td><\/tr> Icon-only menu, search, carousel, or modal button has no accessible name<\/td> WCAG name, role, and value criteria[1]<\/sup><\/td> Screen-reader users hear an unlabeled control<\/td> Fix anywhere the control appears<\/td><\/tr> Important image is a CSS background with no equivalent text<\/td> Image accessibility and image SEO guidance[5]<\/sup><\/td> Users and crawlers may miss the meaning<\/td> Replace with an HTML image or add an equivalent text path<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Check Readability And Contrast<\/h2>\n\n\n\n
Review Structure And Navigation<\/h2>\n\n\n\n
Audit Images And Forms<\/h2>\n\n\n\n
Prioritize Fixes By User Impact<\/h2>\n\n\n\n
FAQ<\/h2>\n\n\n\n
Is WCAG 2.2 AA required for every small business website?<\/h3>\n\n\n\n
Can Lighthouse prove that a page is accessible?<\/h3>\n\n\n\n
Should accessibility fixes wait for a redesign?<\/h3>\n\n\n\n
How does accessibility connect to SEO?<\/h3>\n\n\n\n
Optional Tool Check<\/h2>\n\n\n\n