Accessibility audit checklist for marketing sites: a practical guide for B2B teams

An accessibility audit checklist gives marketing teams a practical way to find out whether prospects, customers, partners, analysts, and job candidates can actually use the site. Not theoretically. Actually. That includes people using different devices, input methods, browsers, and assistive technology. For B2B teams, the checklist has to connect WCAG requirements to the commercially sensitive pages: demo forms, pricing requests, gated content, procurement pages, plus the fixes someone has to ship.

Marketing sites get treated like the easy part of the digital estate. I get why. Nobody logs in, and the workflows look lighter than the product. But look at a normal B2B site for five minutes: product pages, pricing requests, gated reports, webinar forms, partner directories, comparison pages, customer stories, chat widgets, video, PDFs, cookie banners, and campaign landing pages. If those block keyboard users, screen reader users, low vision users, people with cognitive disabilities, or users with motor impairments, the site becomes harder to buy from. My take: that is not a “compliance issue” first. It is a buying-path issue. It can hurt pipeline, SEO, sales conversations, and procurement review.

The numbers are not flattering. WebAIM’s 2026 Million report found 56,114,377 detectable accessibility errors across one million home pages, an average of 56.1 errors per page. W3C published WCAG 2.2 as a W3C Recommendation on October 5, 2023, with nine success criteria added to WCAG 2.1. The U.S. Department of Justice’s ADA Title II rule names WCAG 2.1 Level AA as the technical standard for state and local government web content and mobile apps, with compliance dates of April 26, 2027 for larger public entities and April 26, 2028 for smaller public entities and special districts. The European Accessibility Act applies to covered products and services placed on the EU market after June 28, 2025. Even when a private B2B marketing site is not directly covered by one of these rules, buyers may still ask for accessibility evidence during vendor review. That last part gets underestimated.

What an accessibility audit must cover

A useful marketing site audit follows the customer journey. It does not stop at a home page scan. Test templates, components, content, media, forms, documents, outside tools, and conversion paths against WCAG Level AA expectations and real assistive technology behavior. Most guides say “scan the site and fix the errors.” That is only half right.

Start with the pages that affect revenue

Start where buying intent shows up. For most B2B companies, that means the home page, product overview pages, pricing or quote request pages, demo forms, contact forms, resource pages, event registration pages, case studies, comparison pages, and paid landing pages. Include at least one page from every reusable template. A five page brochure site may need every page reviewed. A 2,000 page enterprise site needs a representative sample, plus high traffic and high risk pages from analytics.

Do not let an automated score decide the scope. Scanners help, but they cannot reliably tell whether link text makes sense in context. They cannot judge whether alt text explains a product screenshot, whether a modal is understandable, or whether a webinar form works well with a keyboard. Use WAVE, axe, Lighthouse, or Accessibility Insights to catch repeatable failures. Then check the important parts by hand. Skip this step, and the audit gets shallow fast.

Map audit items to business outcomes

Executives need technical findings translated into business risk. A low contrast CTA on a demo page can hurt conversion. A PDF datasheet with no logical reading order can slow procurement. A keyboard trap in a chatbot can block a sales conversation. Missing captions in a product video affect deaf and hard of hearing buyers, and also people watching without audio in an office, airport, or shared workspace.

Give every issue a severity level. A blocked form submission is critical. A missing alt attribute on a decorative image is low. Repeated “learn more” links may be medium across a blog, but high on a product comparison page where users need to tell offers apart. Why does this matter? Because marketing, design, development, legal, and revenue operations will otherwise argue about priority using different yardsticks.

The core checklist for marketing pages

The page review should answer four blunt questions: can people perceive the content, move through the page, understand what is happening, and rely on the markup? For B2B sites, that means checking hero sections, forms, navigation, videos, resource gates, analytics tags, and embedded SaaS widgets. It sounds basic. It is not.

Content, headings, and page structure

• Use one clear H1 per page that matches the page purpose, such as “Cloud Security Platform” or “Request a Demo.”
• Keep headings in a logical order so assistive technology users can scan by section.
• Write page titles that distinguish similar pages, especially product, industry, and resource pages.
• Make link text specific. Replace repeated “Learn more” links with phrases such as “Learn more about endpoint detection” or “Download the SOC 2 checklist.”
• Use plain copy for forms, errors, and calls to action. High intent buyers should not have to decode clever labels.

Images, icons, and visual content

• Provide alt text for meaningful images, including charts, diagrams, product screenshots, customer logos, and event speaker photos.
• Use empty alt text for decorative images so screen reader users do not hear clutter.
• Do not communicate status, pricing tiers, errors, or plan differences by color alone.
• Check contrast for text over hero images, gradients, video backgrounds, and tinted overlays. WCAG Level AA generally requires 4.5:1 contrast for normal text and 3:1 for large text.
• Give icon buttons programmatic names. A magnifying glass search button needs an accessible name such as “Search.”

Forms and lead generation

• Connect every input to a visible label, including name, email, company, phone, country, job title, and consent fields.
• Use clear required field indicators and explain them before the form.
• Place error messages near the relevant fields and expose them to assistive technology.
• Preserve user input after errors. Nobody should have to retype a long message because one field failed.
• Test forms with keyboard only. Tab through every field, checkbox, dropdown, submit button, privacy link, and CAPTCHA alternative.
• Avoid inaccessible CAPTCHA patterns. If you need bot protection, do not make prospects solve visual or audio puzzles as the main path.

Navigation, menus, and conversion components

• Make the main navigation, mega menu, footer links, search, cookie banner, chat widget, and modal dialogs usable with a keyboard.
• Keep the focus indicator visible. Sticky headers and popups should not cover it.
• Provide a working skip link that moves keyboard users past repeated navigation.
• Do not trap focus inside a closed or irrelevant component.
• For carousels, rotating testimonials, and announcement bars, provide pause controls and avoid surprise movement.

WebAIM’s 2026 data found that 82.7 percent of home pages used ARIA outside landmark roles, and pages with ARIA had more detected errors on average than pages without ARIA. ARIA is useful when it is done well. It is also easy to get wrong. Counter to the usual advice, “add ARIA” is often the wrong first move. A native button, label, heading, or list is usually more dependable than a custom element patched with a pile of attributes.

How to test beyond automated tools

Automated testing is the first pass. It is not the audit. A serious accessibility audit includes keyboard testing, screen reader checks, browser zoom, mobile behavior, form validation, media review, and a person asking the obvious question: does this page make sense? I’ll be honest: that last question catches more than teams expect.

Run a practical manual test set

Start with keyboard only. Use Tab, Shift+Tab, Enter, Space, Escape, and arrow keys where they apply. Check that every interactive element receives focus in a sensible order. Check that every focused item is visible. Dropdowns should open and close, modals should return focus after closing, and the user should be able to submit or abandon a form without a mouse.

Then test with at least one screen reader setup. For North American B2B teams, common combinations include NVDA with Chrome or Firefox on Windows, JAWS with Chrome or Edge in enterprise environments, VoiceOver with Safari on macOS and iOS, and TalkBack with Chrome on Android. You are not trying to test every possible device. You are trying to catch what scanners miss: unlabeled buttons, confusing reading order, duplicate landmarks, hidden headings, and modal messages that never reach the user.

Check responsive and zoom behavior

Marketing sites often look polished at standard desktop width and then break at 200 percent zoom, small laptop widths, or mobile breakpoints. Check whether navigation still works, sticky headers do not cover content, form fields do not overlap, and ordinary text does not require horizontal scrolling. Is this overkill? For a 50-page site, no. Buyers compare vendors while traveling, on tablets, on phones, through remote desktops, and with browser zoom because they need it. The conversion path has to survive those situations.

Review media, PDFs, and downloads

B2B marketing teams publish more than web pages. Audit video captions, transcripts, podcast pages, webinar recordings, slide decks, white papers, one pagers, security documents, and ROI calculators. Captions need to handle technical terms, product names, acronyms, and speaker changes. PDFs need tagged structure, readable order, document language, meaningful links, alt text for meaningful visuals, and tables that work with assistive technology.

Gated content needs extra attention because it combines forms, privacy notices, downloads, emails, and CRM automation. If a buyer cannot complete a resource form, they may never enter the pipeline. If a screen reader user downloads an untagged PDF, they may reasonably wonder whether the product team is just as careless. That is a harsh read. It is also a fair one.

Prioritizing fixes for B2B teams

A practical remediation plan fixes blockers first, then repeatable component defects, then content quality at scale. Rank work by customer impact, legal and procurement exposure, traffic, conversion value, and reuse across the design system. Yes, this contradicts the instinct to fix the easiest tickets first. Bear with me.

Use a severity model

Sort issues into four groups. Critical issues block an important task, such as submitting a demo request, opening navigation, accepting required consent, or reading pricing information. High issues create serious friction on important pages, such as low contrast primary CTAs, missing labels on lead forms, inaccessible cookie banners, or videos without captions. Medium issues reduce usability but may not block completion, such as vague links, uneven heading levels, or alt text that exists but says almost nothing. Low issues include minor content cleanup and decorative markup problems with limited user impact.

Estimate effort separately from severity. A critical issue may take one hour if it is a missing form label. A medium issue may take several days if it requires rebuilding a shared carousel. This distinction matters. It helps leaders approve quick fixes without pretending the larger platform work disappeared.

Fix shared components before one off pages

Marketing sites usually run on a CMS, static site generator, or component library. A faulty CTA component can create hundreds of identical issues. A flawed modal pattern can affect newsletter signup, webinar registration, exit intent offers, and region selectors. Fix shared components first when you can. The payoff is bigger, and regressions are easier to control.

Common useful fixes include accessible navigation markup, visible focus styles, reusable form fields with labels and error states, accessible modal behavior, standard video embeds with captions, and CMS fields for meaningful alt text. Give content authors guardrails: required alt text prompts for meaningful images, heading level guidance, accessible table patterns, and warnings for vague link text. My bias: make the right thing easier in the CMS, not just documented in a wiki nobody opens.

Make accessibility part of campaign operations

Accessibility cannot sit in an annual audit folder. Paid landing pages, product launches, acquisitions, rebrands, event microsites, and analyst report campaigns move too fast. Add accessibility checks to the campaign launch process: keyboard test the page, verify form labels and errors, confirm color contrast, test the cookie banner, check the thank you state, review email and PDF assets, and make sure analytics scripts did not break interaction.

Assign owners. Marketing owns content quality and campaign acceptance. Design owns contrast, states, layout, and interaction patterns. Engineering owns semantic implementation, testing, and component behavior. Legal and procurement teams weigh in on risk. Revenue operations confirms that accessible forms still capture required CRM data. Without names attached, accessibility becomes an emergency every quarter instead of normal quality control.

Audit deliverables, metrics, and executive reporting

An executive ready audit should produce a prioritized issue list, evidence, owners, timelines, and measurable progress. The report needs to be clear enough for leadership to fund and specific enough for teams to fix without rediscovering every problem from scratch. We tried vague reporting. It stalls.

What the report should include

Include the tested scope, standards used, tools used, assistive technology combinations, pages reviewed, limitations, and a severity summary. For each issue, provide the page URL, affected component, WCAG reference, user impact, reproduction steps, screenshot or short note, recommended fix, owner, and priority. Avoid vague findings such as “site is not accessible.” A better finding is: “The demo request form email field has no programmatic label, so screen reader users hear only ‘edit text’ and may not know what information is required.”

Use a simple executive dashboard: count of critical, high, medium, and low issues; percentage of main conversion paths tested; number of reusable component defects; number of blocked forms; number of inaccessible PDFs; and remediation status by owner. Track these numbers monthly. For a more mature program, add automated test coverage in the component library and pre release checks in CI for obvious regressions. Why monthly? Because campaign pages can undo last month’s progress in a single release cycle.

Use standards without overclaiming compliance

WCAG Level AA is the practical benchmark for most commercial web programs, but an audit is not permanent compliance. A site can pass a scoped review and regress the next week when someone ships a campaign page, outside script, or CMS entry. State the exact scope and audit date. If legal claims matter, have counsel review public language before saying the site is “ADA compliant” or “fully accessible.”

Use reliable source references in the report. Current primary references include W3C’s WCAG 2.2 documentation at w3.org, the U.S. Department of Justice ADA web rule resources at ada.gov, the WebAIM Million 2026 report at webaim.org, and EU accessibility guidance at europa.eu. These sources help executives separate stable requirements from vendor sales copy.

FAQ

These are the executive questions that usually sit behind an accessibility checklist for marketing sites. Answer them before work starts so leadership, marketing, design, development, and legal teams are not arguing from different assumptions halfway through the audit. Boring? Maybe. Useful? Absolutely.

How often should a B2B marketing site be audited for accessibility?

Run a full audit at least once a year and after major redesigns, CMS migrations, rebrands, or navigation changes. Run lighter checks before every major campaign, product launch, webinar series, or paid landing page release.

Can automated tools prove that our marketing site is accessible?

No. Automated tools catch many code level defects, but they cannot fully judge usability, reading order, link purpose, form clarity, caption quality, or whether a real conversion path works with assistive technology.

Which WCAG version should marketing teams use?

WCAG 2.1 Level AA remains a common legal and procurement benchmark. WCAG 2.2 is the newer W3C Recommendation and adds useful criteria for modern interfaces, so many teams use WCAG 2.2 Level AA as their internal target.

What are the most common accessibility issues on marketing sites?

The usual problems are low contrast, missing form labels, vague links, poor heading structure, inaccessible menus, keyboard traps, missing captions, weak alt text, and inaccessible PDFs. Third party widgets cause plenty of damage too.

Who should own accessibility fixes?

Ownership should be shared but explicit. Marketing owns content and campaign quality. Design owns visual and interaction standards. Engineering owns implementation. Leadership owns priority, budget, and accountability.

Does accessibility improve SEO?

Accessibility and SEO are not the same thing, but they overlap. Clear structure, meaningful links, readable content, captions, and usable pages help people first. Search performance can benefit from that work too.