A B2B website can score 100 in an automated accessibility check and still block a keyboard-only buyer before the first form field. The complication is that compliance is neither a single score nor a substitute for a persuasive offer. B2B website accessibility pays when it is built into a specialist redesign programme that removes friction from valuable journeys; a cosmetic audit can consume budget while leaving those journeys broken.
WCAG basics for B2B website accessibility
Treat WCAG 2.2 Level AA as a delivery baseline for a commercial site, not as a badge. AA requires every applicable Level A and AA success criterion; it is not an average score. Level AAA is useful selectively, but it is an unrealistic blanket promise for every page and format.
WCAG 2.2 uses four principles:
- Perceivable: Content has alternatives where sight, hearing or presentation would otherwise create a barrier.
- Operable: Navigation, controls and forms work without requiring one particular input method.
- Understandable: Labels, instructions, behaviour and error messages are predictable.
- Robust: Browsers and assistive technologies can determine each element’s name, role and state.
Conformance applies to complete pages and complete processes. One labelled field does not rescue a demo-booking route containing a keyboard trap.
WCAG is a technical standard, not a universal legal certificate. Contracts, procurement requirements, sectors and jurisdictions can impose additional duties. Legal advice is appropriate when material contractual or regulatory exposure exists.
Four release rules make the standard operational:
- Normal text below 4.5:1 contrast versus large text below 3:1 → change the shared colour token before release.
- Text works at 100% sizing but loses content or functionality at 200% → block release and repair the layout.
- Any required action fails using Tab, Shift+Tab, Enter, Space or Escape → treat the journey as incomplete.
- A new pointer target falls below 24×24 CSS pixels without qualifying spacing or an exception → enlarge it; WCAG’s AA minimum is 24×24 versus the AAA enhanced target of 44×44.
AA is the sensible baseline; completed journeys are the real test.
The commercial case starts with blocked value
The expensive failure is not an audit warning. It is a qualified visitor who cannot compare services, filter an event catalogue, download decision material or submit an enquiry.
That affects reach, paid-media efficiency and procurement confidence. Accessibility cannot repair weak positioning, but it can stop the interface wasting demand that already exists.
Take an illustrative UK consultancy spending on Google Ads. These are assumptions, not Actualyse client data. Nine labelled inputs drive the example:
- Monthly Google Ads spend: £8,000
- Average cost per click: £10
- Landing-page form-start rate: 5%
- Form starts exposed to the blocker: 10 of 40
- Current completion-rate assumption: 50%
- Accessible-build completion assumption: 80%
- Qualified-enquiry assumption: 40%
- Average qualified opportunity value: £20,000
- Quoted remediation cost: £2,400
The six calculation lines are:
£8,000 ÷ £10 = 800 paid visits
800 × 5% = 40 form starts
10 × (80% − 50%) = 3 additional enquiries
3 × 40% = 1.2 expected qualified opportunities
1.2 × £20,000 = £24,000 illustrative pipeline
£24,000 ÷ £2,400 = a 10:1 pipeline-to-fix-cost ratio
The comparison is £24,000 of illustrative pipeline versus a £2,400 fix, not £24,000 of promised revenue.
The honest limit here is that visitor intent, assistive setup, repeat attempts and sales qualification confound the model. What the calculation cannot tell you is whether three additional enquiries will materialise.
Use three priority bands: at least 3:1 → validate and fix this sprint; 1:1–2.99:1 → queue behind journey blockers; below 1:1 → improve the evidence before spending.
Commercial priority follows blocked value, not warning volume.
B2B website accessibility and rankings
Do not sell accessibility with an SEO promise. Semantic HTML and descriptive text can clarify page structure for people and Google’s crawlers, but that overlap does not prove a direct ranking reward for WCAG conformance.
A technically accessible page can still answer the wrong query, lack authority or bury its useful answer. Conversely, a ranking page can remain frustrating or impossible for some buyers to use.
Use Search Console to compare the 28 days after remediation versus the preceding 28 days. Annotate content, link and indexing changes so accessibility work is not credited for somebody else’s intervention.
If a priority page remains in positions 11–20 with consistent impressions for 28 days, rewrite the title and opening around search intent before commissioning more accessibility work for rankings.
The claim here is falsifiable: accessibility remediation alone will not move an intent-mismatched page from positions 11–20 to positions 1–10; movement with content, links and competition unchanged would prove the claim wrong.
During a rebuild, follow a separate plan to protect organic visibility through a redesign. Redirects, canonicals and content mapping solve a different problem from keyboard operation and form labelling.
Accessible structure supports discovery, but relevance still earns rankings.
The six-check afternoon audit
Set aside 90 minutes before commissioning a broad audit. Choose three pages: the highest-spend landing page, the highest-organic entrance page and the shortest route to an enquiry.
Run six checks:
- Keyboard completion. Finish the primary task without a mouse. One required control that cannot be reached or activated → stop sending paid traffic to the affected journey until repaired.
- Focus visibility and order. Watch the indicator through every control. Focus disappearing on two consecutive elements → repair the shared focus style rather than patching individual pages.
- Forms and errors. Submit blank and invalid values. An error communicated only by colour, or a placeholder used instead of a persistent label → fail the component.
- Contrast and resizing. Check text, meaningful interface graphics and the page at 200% text sizing. The same failing colour token appearing on three or more components → change the token globally.
- Headings and link names. Read only the heading outline and links. If the offer and next action remain unclear after 60 seconds, rewrite the semantic hierarchy; more than two identical “Learn more” links → replace them with named destinations.
- Dynamic controls. Operate menus, tabs, accordions and filters with a keyboard and screen reader. An unannounced state change or trapped focus → block release.
Run an automated scanner afterwards. The same defect across three or more templates belongs in the source component; a clean scan followed by a failed manual journey means the manual result wins.
Manual journey completion outranks automated neatness.
If this analysis exposes wider gaps in your site, we can turn the evidence into a focused redesign brief — book a call
What does not improve accessibility outcomes
Overlay widgets are the most visible shortcut and the weakest substitute for repairing the underlying interface.
Five popular responses create activity without clearing buyer barriers:
- Installing an accessibility overlay. A layer above the site does not reliably repair source semantics, reading order, form relationships or custom keyboard behaviour.
- Polishing an automated score from 95 to 100. Scanners can identify rule-based defects, but they cannot decide whether link wording makes sense, focus order follows the task or an error message helps recovery.
- Publishing an accessibility statement without a backlog owner. The statement documents intent. It does not assign the broken form, release date or acceptance test to anyone.
- Running an indiscriminate alt-text sprint. Descriptive alternatives help meaningful images, but verbose text on decorative assets adds noise and leaves navigation or submission blockers untouched.
- Approving a colour-led rebrand before testing components. A documented brand personality system should guide distinctive, accessible tokens. Treating chosen colour values as untouchable merely distributes the same contrast failure across the site.
Accessibility theatre leaves buyer barriers intact.
Build accessibility into the architecture
Late remediation multiplies decisions because the same unclear label, colour token or control pattern has already spread through templates.
Four architecture patterns from our work show where accessibility obligations begin:
- Lanteria’s multi-stakeholder capability structure routed a broad Microsoft 365 HR offer for different audiences. That architecture depends on headings and destination names carrying meaning without visual context.
- AfriCap Hub’s event catalogue and registration journey made filtering and progression central to the experience. Filters, changing results and form states therefore belong in the interaction model from the start.
- Savgen’s technical multi-industry structure organised a complex industrial offer across products and applications. Clear taxonomy reduces reliance on repeated, ambiguous links.
- Lake Erie Shores’ stay and ownership pathways served two distinct audiences under one site. Those choices need explicit wording rather than differentiation through imagery or colour alone.
Teams using a conversion-led redesign plan should add accessible acceptance criteria to every priority journey before visual approval.
Accessibility is also distinct from segment-level website personalisation. Accessibility makes a route usable; personalisation decides which relevant route or message to present.
Whether a company commissions specialist website design and redesign support or a defined-scope website build, the brief should name the WCAG target, tested journeys, exceptions, owner and release threshold.
Accessible systems are designed once and reused everywhere.
FAQ
Four procurement and governance decisions prevent accessibility ownership disappearing after launch.
How often should a B2B website be retested?
Rerun the three priority journeys within one working day of any release that changes a shared component. Add a broader manual sample every quarter; an annual automated scan is too slow for an actively edited site.
Do archived PDFs need immediate remediation?
If a PDF influenced a sale, onboarding task or support request within the previous 12 months, remediate it or publish equivalent HTML. If recorded use is zero, provide an accessible version on request and prioritise current customer-facing documents.
What if a third-party booking or chat tool is inaccessible?
Treat a blocked embedded journey as your defect, not merely the supplier’s caveat. Give the supplier 10 working days to repair it or provide an accessible alternative; replace the tool if neither happens.
What accessibility evidence should a website supplier hand over?
Require three artefacts: a WCAG 2.2 AA test report by template and journey, manual keyboard and screen-reader evidence for priority flows, and a dated exception backlog with named owners.
Accessibility governance works when evidence, ownership and deadlines are explicit.
Summary
Five rules should govern the next website release:
- Adopt WCAG 2.2 AA as the delivery baseline and record every exception.
- Block release when any priority journey cannot be completed by keyboard alone.
- Fix the shared component when one defect appears across three or more templates.
- Judge rankings over 28 days versus the previous 28 days without promising uplift.
- Every shared-component release requires retesting three priority journeys.
Actualyse designs and rebuilds B2B websites that turn research visits into qualified pipeline. Book a call to talk through where yours stands.
