Accessibility (WCAG 2.2) for SaaS
Products: 2026 Compliance Guide

A SaaS CTO we worked with in late 2025 had received procurement security questionnaire from a US enterprise customer (£120k ACV deal) and from a UK public sector customer (£85k ACV deal). Both procurement questionnaires included accessibility compliance requirements. US enterprise questionnaire required WCAG 2.1 Level AA minimum and Section 508 conformance documentation. UK public sector questionnaire required WCAG 2.2 Level AA conformance per Public Sector Bodies Accessibility Regulations 2018 and specific accessibility statement publication. The CTO's SaaS had informal accessibility practice but no formal WCAG conformance documentation. Three realistic options.

Option A: pursue WCAG 2.2 Level AA compliance (newest standard aligned with UK public sector requirement and future-proof against EU Accessibility Act requirement) with specific audit documentation for both customers; typically 4-9 months timeline. Option B: pursue WCAG 2.1 Level AA for immediate US enterprise customer plus WCAG 2.2 for UK customer; added complexity. Option C: pursue accessibility overlay widget (UserWay, accessiBe) as quick accessibility solution; typical overlay vendor sales pitch. The CTO's accessibility specialist adviser was emphatic on Option C: overlay widgets do not deliver true WCAG compliance per W3C and leading accessibility organisations, do not substitute for accessibility engineering, and carry documented legal risk from specific lawsuits against overlay customers.

The CTO chose Option A: pursue WCAG 2.2 Level AA compliance aligned with newest standard, future-proof against EU Accessibility Act 2025 requirement, and acceptable to US enterprise customer accepting WCAG 2.2 as superset of WCAG 2.1. Implementation: selected Deque Systems for comprehensive accessibility audit and remediation guidance plus axe DevTools for ongoing automated testing integrated into CI/CD. Scoped WCAG 2.2 Level AA conformance across SaaS covering specific pages, specific user flows, specific interactive components. Engineering remediation: addressed specific WCAG 2.2 Level AA findings across keyboard navigation (specific keyboard trap issues), focus visibility (specific focus indicator issues addressing new 2.2 Focus Not Obscured criterion), target size (addressing new 2.2 Target Size Minimum criterion), consistent help (addressing new 2.2 Consistent Help criterion), accessible authentication (addressing new 2.2 Accessible Authentication criterion by providing specific authentication alternative to cognitive function tests), semantic HTML (specific landmark and heading structure improvements), ARIA (specific ARIA implementation improvements), colour contrast (specific contrast ratio improvements for WCAG AA 4.5:1 for normal text, 3:1 for large text), form labels (specific label improvements), image alt text (specific alt text improvements), video captions (specific caption and transcript additions). Operational: accessibility statement published per UK Public Sector Bodies Accessibility Regulations 2018 requirement. Manual testing including specific screen reader testing (NVDA, JAWS, VoiceOver), keyboard-only navigation testing, specific other assistive technology testing. Ongoing: axe DevTools in CI/CD catching regressions; specific manual testing scheduled quarterly.

Timeline: WCAG 2.2 Level AA conformance achieved 7 months from accessibility programme start; conformance report delivered to US enterprise and UK public sector customers; both contracts signed on accessibility conformance evidence. Cost: Deque audit and remediation guidance £35k; axe DevTools £8k annual; engineering remediation estimated 420 hours across 7 months; accessibility statement publication specific effort; manual testing specific effort. Total year one cost including team time at opportunity cost: substantial but justified by £205k combined ACV customer unlock plus future-proofing against EU Accessibility Act 2025 and future UK public sector customers.

The CTO's reflection: "Accessibility is substantial engineering programme regardless of what overlay widget vendors promise. Overlay widgets do not deliver true WCAG compliance. We needed sustained engineering effort for 7 months plus ongoing automated and manual testing. The lesson I would give any SaaS CTO scoping accessibility compliance: pursue WCAG 2.2 Level AA (newest standard aligned with EU Accessibility Act 2025 and future-proof) with proper accessibility engineering programme; reject overlay widget quick-fix pitch; invest in automated testing in CI/CD plus manual testing with assistive technologies; realistic timeline is 4-9 months with proper engineering investment."

That is the wcag 2.2 for saas 2026 conversation across US and UK SaaS CTOs facing enterprise and public sector customer accessibility requirements. WCAG 2.2 Level AA is the 2026 standard compliance target. Overlay widgets do not substitute for accessibility engineering. Proper accessibility engineering programme (automated testing in CI/CD plus manual testing with assistive technologies plus specific remediation) delivers true WCAG conformance in 4-9 months timeline.

WhiteStone has shipped SaaS products with specific accessibility compliance for enterprise and public sector customers across our 50-plus product portfolio. SAGE US enterprise with specific accessibility requirements. UK B2B SaaS products with specific accessibility compliance for UK public sector and UK enterprise customers. The accessibility engineering patterns we have shipped across 50-plus products transfer directly to any SaaS scoping WCAG 2.2 compliance.

This article is a practitioner guide for SaaS CTOs, product leaders, engineering leads, and compliance leaders scoping wcag 2.2 for saas compliance in 2026. WCAG 2.2 structure. New success criteria over WCAG 2.1. 2026 regulatory landscape. Testing tools vendor landscape. Honest position on overlay widget controversy. Realistic cost and timeline bands. Common failure modes.

WCAG 2.2 Structure and New Success Criteria

WCAG 2.2 publication. W3C published WCAG 2.2 as W3C Recommendation in October 2023. WCAG 2.2 includes all WCAG 2.1 success criteria plus 9 new success criteria across Levels A, AA, AAA. WCAG 2.2 is current W3C accessibility standard.

WCAG 2.2 four principles POUR.

• Perceivable: information and user interface components must be presentable to users in ways they can perceive.

• Operable: user interface components and navigation must be operable.

• Understandable: information and operation of user interface must be understandable.

• Robust: content must work reliably when interpreted by various user agents including assistive technologies.

WCAG 2.2 success criteria levels.

• Level A: minimum conformance level with most basic accessibility features.

• Level AA: most commonly targeted conformance level including most accessibility requirements for general accessibility. 2026 standard compliance target for most SaaS. Required by EU Accessibility Act 2025, US Section 508, UK Public Sector Bodies Accessibility Regulations 2018.

• Level AAA: enhanced conformance level with specific advanced accessibility features. Not typically achievable site-wide; targeted for specific content types.

New WCAG 2.2 success criteria (over WCAG 2.1).

New Level AA criteria (most relevant for 2026 SaaS compliance):

• 2.4.11 Focus Not Obscured (Minimum): when user interface component receives keyboard focus, the component is not entirely hidden by author-created content.

• 2.5.8 Target Size (Minimum): interactive targets are at least 24 by 24 CSS pixels except for specific exceptions (inline, user agent control, essential, equivalent, specific other exceptions).

• 3.2.6 Consistent Help: help mechanisms (contact details, help desk, specific other) are consistently located relative to other content across pages.

• 3.3.7 Redundant Entry: previously entered information in a process is auto-populated or available for user selection, with specific exceptions.

• 3.3.8 Accessible Authentication (Minimum): cognitive function tests (e.g., remembering password, solving puzzle) not required for authentication unless alternative provided.

New Level A criteria:

• 3.2.6 Consistent Help (also at Level A for specific scope).

New Level AAA criteria:

• 2.4.12 Focus Not Obscured (Enhanced): when component receives keyboard focus, no part of component is hidden by author-created content.

• 2.4.13 Focus Appearance: specific focus indicator appearance requirements.

• 2.5.9 Target Size (Minimum, Enhanced): interactive targets are at least 44 by 44 CSS pixels except for specific exceptions.

• 3.3.9 Accessible Authentication (Enhanced): cognitive function tests not required for authentication under any circumstances.

WCAG 2.2 practical implications for SaaS 2026. New Level AA criteria require specific engineering attention: Focus Not Obscured requires review of fixed-position elements (sticky headers, modals, specific other) that may obscure focus; Target Size (Minimum) requires review of all interactive elements for 24 by 24 CSS pixel minimum; Consistent Help requires review of help mechanism location consistency; Redundant Entry requires review of multi-step process data persistence; Accessible Authentication requires review of authentication flows for cognitive function test alternatives.

Per W3C 2026 WCAG 2.2 guidance and European Commission 2026 Accessibility Act guidance, WCAG 2.2 Level AA has become the 2026 standard accessibility compliance target for SaaS with EU Accessibility Act 2025 private sector scope, UK Public Sector Bodies Accessibility Regulations 2018 continuing public sector requirement, US Section 508 and ADA Title III, driving 2026 SaaS compliance scope.

2026 Regulatory Landscape for SaaS Accessibility

EU Accessibility Act (EAA) 2025. European Accessibility Act (Directive (EU) 2019/882) applies from 28 June 2025 to specific private sector products and services including ecommerce, banking services, electronic communications, audiovisual media services, air/bus/rail/waterborne passenger transport, consumer banking services, ebooks and dedicated software, hardware systems with general purpose computing (computers, specific smartphones), payment terminals, consumer banking terminals, ticketing and check-in self-service terminals, specific interactive self-service terminals. SaaS products providing in-scope services or used by in-scope service providers must conform to accessibility requirements aligned with EN 301 549 standard which incorporates WCAG 2.1 Level AA (with EN 301 549 2026 updates potentially aligning to WCAG 2.2). Compliance deadline was 28 June 2025 with specific transitional arrangements for existing products.

UK accessibility regulations. Equality Act 2010 general duty for service providers (including SaaS as service providers) to make reasonable adjustments including accessibility. Public Sector Bodies Accessibility Regulations 2018 (SI 2018/952) apply specifically to UK public sector websites and apps including SaaS used by UK public sector; require WCAG 2.1 Level AA minimum with WCAG 2.2 increasingly expected; require accessibility statement publication. UK public procurement generally references WCAG conformance expectations.

US accessibility regulations. ADA Title III (Americans with Disabilities Act Title III) applies to public accommodation accessibility; extended to specific websites and digital services through case law (Robles v Domino's Pizza 2019 and specific other cases) with specific interpretation varying by circuit. Section 508 of the Rehabilitation Act applies to US federal government procurement effectively requiring accessibility from vendors selling to US federal government; aligned with WCAG 2.0 Level AA with WCAG 2.1 and 2.2 increasingly expected. Specific state regulations (specific California, specific other state) adding specific requirements.

Canada regulations. Accessible Canada Act (ACA) 2019 applies to federally regulated entities including specific private sector. Specific provincial accessibility regulations.

Australia regulations. Disability Discrimination Act (DDA) 1992 applies to services including specific digital services.

Other national regulations. Specific other national accessibility regulations varying by country. Pattern: 2026 regulatory landscape substantially broader than 2020 landscape with EU Accessibility Act 2025 significantly expanding private sector scope globally for SaaS serving EU markets.

SaaS compliance scoping implications. SaaS products serving EU customers (even indirectly through enterprise customers with EU operations) in scope for EU Accessibility Act 2025. SaaS products selling to US federal government or state and local government in scope for Section 508. SaaS products serving UK public sector customers in scope for Public Sector Bodies Accessibility Regulations 2018. SaaS products with US ADA Title III exposure through specific public accommodation case law. Pattern: 2026 SaaS accessibility compliance scope increasingly broad; proactive WCAG 2.2 Level AA compliance substantially de-risks across regulatory landscape.

2026 Accessibility Testing Tools Landscape

axe DevTools by Deque Systems. Dominant developer-focused automated accessibility testing. Specific browser extension plus library versions for CI/CD integration (axe-core). Specific framework integrations (React, Angular, Vue, specific others). Strong accuracy for automated-testable WCAG criteria. Industry standard for developer workflow accessibility testing.

WAVE by WebAIM. Web-based accessibility evaluation tool. Browser extension plus web interface. Suitable for quick accessibility checks on specific pages. Open and widely used.

Siteimprove. Enterprise accessibility monitoring platform with specific website-wide monitoring, specific reporting, specific policy management. Suitable for enterprise accessibility programme management.

Pope Tech. Accessibility monitoring platform using WAVE engine with specific enterprise reporting.

Level Access. Accessibility services firm plus platform. Comprehensive accessibility services including audit, training, platform.

Stark. Figma accessibility plugin for design-stage accessibility checking. Addresses accessibility earlier in product development lifecycle during design. Specific plugin capability for colour contrast, text size, specific other design accessibility.

Lighthouse. Chrome DevTools accessibility audit using axe-core. Suitable for quick accessibility checks during development.

Specific other tools. Pa11y (open command-line accessibility testing), ARC Toolkit (TPGi), specific other tools.

Automated vs manual testing. Automated accessibility testing (axe DevTools, WAVE, Siteimprove, specific others) catches typically 30-50 percent of accessibility issues (specific technical issues like missing alt text, specific keyboard trap, specific contrast issues). Remaining 50-70 percent of accessibility issues require manual testing including testing with assistive technologies (screen readers NVDA, JAWS, VoiceOver, specific other), keyboard-only navigation testing, specific other assistive technology testing. Pattern: automated testing in CI/CD plus manual testing with assistive technologies both required for comprehensive WCAG conformance.

Honest Position on Accessibility Overlay Widgets

Accessibility overlay widgets. UserWay, accessiBe, Equally AI, specific other overlay widgets claim to deliver WCAG compliance through JavaScript widget overlay on existing website without engineering changes.

W3C and accessibility community position. W3C and leading accessibility organisations position: overlay widgets do not deliver true WCAG compliance. Overlays interfere with assistive technologies users actually use (screen readers, specific other). Overlays do not fix underlying accessibility issues; they add layer that frequently makes accessibility worse for assistive technology users.

Legal risk documented. Specific documented lawsuits against overlay widget customers claiming overlays did not deliver accessibility and customers remained liable under ADA Title III and specific other regulations. Specific documented position by US National Federation of the Blind and specific other disability advocacy organisations against overlay widgets.

Pattern. Overlay widgets are not accessibility substitute. SaaS teams should engineer accessibility properly rather than rely on overlays. Overlay widget marketing frequently positions overlay as quick WCAG compliance solution; this positioning is misleading and carries documented legal risk.

What proper accessibility engineering looks like. Automated testing in CI/CD (axe DevTools or equivalent). Manual testing with assistive technologies (screen readers NVDA, JAWS, VoiceOver, keyboard-only navigation, specific other). Specific remediation of identified issues across semantic HTML, ARIA, keyboard navigation, focus management, colour contrast, form labels, image alt text, video captions, specific other accessibility requirements. Accessibility statement publication where required. Ongoing accessibility maintenance including CI/CD testing and scheduled manual testing.

Honest 2026 WCAG 2.2 Compliance Cost and Timeline Bands

Cost breakdown year one WCAG 2.2 Level AA for mid-sized SaaS.

• Accessibility audit and remediation guidance (Deque, Level Access, specific other specialist): £15k-£60k.

• Automated testing tool (axe DevTools, Siteimprove, Pope Tech): £5k-£25k year one.

• Design-stage accessibility (Stark, specific other): £2k-£10k.

• Engineering remediation: substantial internal team time (typically 300-800 hours depending on scope and existing accessibility baseline).

• Manual testing with assistive technologies: £5k-£20k.

• Accessibility statement publication and specific documentation: specific effort.

• Ongoing: automated testing tool subscription plus scheduled manual testing plus specific maintenance.

Timeline realism. Mid-sized SaaS WCAG 2.2 Level AA: 4-9 months typical from accessibility programme start to conformance. Enterprise SaaS: 6-18 months typical. Compliance platform or overlay vendor pitches promising faster timelines (weeks) are not realistic for true WCAG conformance. Shorter timelines possible with substantial team dedication and existing accessibility baseline; longer timelines common when team competes with product development or baseline accessibility is weak.

Common Failure Modes

Relying on accessibility overlay widgets. SaaS adopts UserWay, accessiBe, or similar overlay as accessibility solution. Does not deliver true WCAG compliance; carries documented legal risk. Fix: proper accessibility engineering programme replacing overlay.

Automated testing only. SaaS relies on axe DevTools or WAVE automated testing without manual testing. Catches 30-50 percent of accessibility issues; remaining 50-70 percent uncaught. Fix: automated testing in CI/CD plus manual testing with assistive technologies.

Accessibility as late-stage checklist. Accessibility treated as late-stage pre-launch checklist rather than engineered throughout development lifecycle. Expensive remediation. Fix: accessibility engineered from design (Stark or equivalent in Figma) through development (axe DevTools in CI/CD) through pre-launch (manual testing with assistive technologies).

Not addressing new WCAG 2.2 success criteria. SaaS pursues WCAG 2.1 compliance in 2026 without addressing new WCAG 2.2 criteria (Focus Not Obscured, Target Size Minimum, Consistent Help, Redundant Entry, Accessible Authentication). Not future-proof against emerging regulatory expectations. Fix: WCAG 2.2 Level AA target including new criteria.

Not understanding EU Accessibility Act 2025 scope. SaaS serving EU customers assumes EU Accessibility Act does not apply. In-scope products and services increasingly broad; indirect EU customer exposure through enterprise customers with EU operations possible. Fix: EU Accessibility Act scope assessment.

Missing accessibility statement. UK Public Sector Bodies Accessibility Regulations 2018 require accessibility statement publication. SaaS serving UK public sector without accessibility statement non-compliant. Fix: accessibility statement published per regulatory requirements.

Treating accessibility as one-time project. Accessibility compliance requires ongoing operational discipline; regressions common. Fix: accessibility as ongoing operational practice with CI/CD automated testing plus scheduled manual testing.

Vendor claims WCAG compliance without specific audit. Vendor marketing claims WCAG compliance without specific audit documentation. Not sufficient for enterprise customer due diligence. Fix: specific WCAG conformance audit documentation.

Keyboard navigation gaps. Focus visibility, keyboard trap, focus order gaps common. Fix: comprehensive keyboard-only navigation testing.

Screen reader incompatibility. Semantic HTML, ARIA, specific other screen reader compatibility gaps common. Fix: screen reader testing with NVDA, JAWS, VoiceOver as standard.

Colour contrast violations. WCAG AA requires 4.5:1 contrast for normal text, 3:1 for large text. Design-stage violations common. Fix: Stark or equivalent design-stage contrast checking plus automated contrast testing in CI/CD.

What We Have Learned Shipping SaaS Products With Accessibility Compliance

WhiteStone has shipped SaaS products with specific accessibility compliance for enterprise and public sector customers across our 50-plus product portfolio. SAGE US enterprise with specific accessibility requirements per our SOC 2 for early-stage SaaS 2026 founders guide. UK B2B SaaS products with specific accessibility compliance for UK public sector and UK enterprise customers. Three lessons transfer to any SaaS scoping WCAG 2.2 compliance.

SaaS CTO case: WCAG 2.2 Level AA conformance plus Deque audit plus axe DevTools CI/CD plus manual testing unlocked £205k combined ACV customer deals. SaaS CTO case referenced above. WCAG 2.2 Level AA conformance programme with Deque audit plus axe DevTools in CI/CD plus manual testing with assistive technologies at 7-month timeline unlocked £120k US enterprise plus £85k UK public sector customer deals. Investment: £35k Deque plus £8k axe DevTools plus substantial team time (420 hours across 7 months). ROI clear from customer deal unlock plus future-proofing against EU Accessibility Act 2025 and future enterprise customers.

Accessibility engineered from design stage with Stark delivers substantially better outcomes than remediation. Across SaaS products we have shipped, pattern is clear: accessibility engineered from design stage (Stark in Figma for colour contrast, text size, specific other design accessibility) delivers substantially better outcomes than late-stage remediation. Design-stage accessibility prevents specific issues from entering code; remediation addresses issues after they entered code at substantially higher cost. Pattern: accessibility shift-left to design stage delivers best outcomes.

Overlay widget quick-fix pitch frequently appears in SaaS accessibility conversations; proper accessibility engineering is only true solution. Across SaaS CTO engagements, overlay widget pitch (UserWay, accessiBe, Equally AI) frequently appears as accessibility quick-fix solution. Pattern we observe: overlay widgets do not deliver true WCAG compliance per W3C and accessibility community position; overlays interfere with assistive technologies; legal risk documented. Pattern: overlay widget quick-fix pitch must be rejected; proper accessibility engineering programme is only true solution for SaaS WCAG compliance.

See our portfolio of shipped work for SaaS products shipped with specific accessibility compliance. For a scoped wcag 2.2 for saas compliance readiness assessment, book a SaaS accessibility advisory call with WhiteStone.

Frequently Asked Questions

What is WCAG 2.2 and when did it become the compliance standard for SaaS?

WCAG 2.2 (Web Content Accessibility Guidelines version 2.2) was published by W3C as W3C Recommendation in October 2023. WCAG 2.2 includes all WCAG 2.1 success criteria plus 9 new success criteria across Levels A, AA, AAA. 2026 compliance target for most SaaS is WCAG 2.2 Level AA covering four principles POUR (Perceivable, Operable, Understandable, Robust). WCAG 2.2 is current W3C accessibility standard increasingly referenced by 2026 regulatory requirements.

What are the new WCAG 2.2 success criteria that SaaS products must address?

New Level AA criteria (most relevant for 2026 SaaS compliance): 2.4.11 Focus Not Obscured (Minimum) requiring focus indicator not entirely hidden by author-created content; 2.5.8 Target Size (Minimum) requiring interactive targets at least 24 by 24 CSS pixels with specific exceptions; 3.2.6 Consistent Help requiring help mechanisms consistently located across pages; 3.3.7 Redundant Entry requiring previously entered information not re-entered; 3.3.8 Accessible Authentication (Minimum) requiring cognitive function tests not required for authentication unless alternative provided. New Level AAA criteria include Focus Not Obscured (Enhanced), Focus Appearance, Target Size (Enhanced) at 44 by 44 CSS pixels, Accessible Authentication (Enhanced).

What is the EU Accessibility Act 2025 and does it apply to SaaS?

EU Accessibility Act (Directive (EU) 2019/882) applies from 28 June 2025 to specific private sector products and services including ecommerce, banking services, electronic communications, audiovisual media services, passenger transport, consumer banking services, ebooks and dedicated software, hardware with general purpose computing, payment terminals, ticketing and check-in terminals, specific interactive self-service terminals. SaaS products providing in-scope services or used by in-scope service providers must conform to accessibility requirements aligned with EN 301 549 standard which incorporates WCAG 2.1 Level AA. SaaS serving EU customers (including indirectly through enterprise customers with EU operations) in scope.

What UK accessibility regulations apply to SaaS products in 2026?

UK Equality Act 2010 general duty for service providers (including SaaS as service providers) to make reasonable adjustments including accessibility. UK Public Sector Bodies Accessibility Regulations 2018 (SI 2018/952) apply specifically to UK public sector websites and apps including SaaS used by UK public sector; require WCAG 2.1 Level AA minimum with WCAG 2.2 increasingly expected; require accessibility statement publication. UK public procurement generally references WCAG conformance expectations.

How does US ADA Title III and Section 508 apply to SaaS vendors?

US ADA Title III (Americans with Disabilities Act Title III) applies to public accommodation accessibility; extended to specific websites and digital services through case law (Robles v Domino's Pizza 2019 and specific other cases) with specific interpretation varying by circuit. US Section 508 of the Rehabilitation Act applies to US federal government procurement effectively requiring accessibility from vendors selling to US federal government; aligned with WCAG 2.0 Level AA with WCAG 2.1 and 2.2 increasingly expected. Specific state regulations (California specific, specific other state) adding specific requirements.

Which accessibility testing tools should SaaS teams evaluate in 2026?

axe DevTools by Deque Systems (dominant developer-focused automated accessibility testing with specific CI/CD integration; axe-core library for framework integration). WAVE by WebAIM (web-based accessibility evaluation). Siteimprove (enterprise accessibility monitoring). Pope Tech (accessibility monitoring with WAVE engine). Level Access (accessibility services plus platform). Stark (Figma accessibility plugin for design-stage checking). Lighthouse (Chrome DevTools accessibility audit using axe-core). Automated testing catches typically 30-50 percent of accessibility issues; manual testing with assistive technologies (screen readers NVDA, JAWS, VoiceOver, keyboard-only navigation) catches remaining issues. Both required for comprehensive WCAG conformance.

Why are accessibility overlay widgets (UserWay, accessiBe) controversial?

Overlay widgets (UserWay, accessiBe, Equally AI, specific others) claim WCAG compliance through JavaScript widget overlay without engineering changes. W3C and leading accessibility organisations position: overlays do not deliver true WCAG compliance; overlays interfere with assistive technologies users actually use (screen readers, specific other); overlays do not fix underlying accessibility issues. Legal risk documented through specific lawsuits against overlay customers claiming overlays did not deliver accessibility and customers remained liable. US National Federation of the Blind and specific other disability advocacy organisations position against overlay widgets. Pattern: overlay widgets are not accessibility substitute; proper accessibility engineering is only true solution.

How much does WCAG 2.2 compliance cost for SaaS in 2026?

Mid-sized SaaS WCAG 2.2 Level AA conformance year one: £30k-£120k. Breakdown: accessibility audit and remediation guidance £15k-£60k; automated testing tool (axe DevTools, Siteimprove, Pope Tech) £5k-£25k year one; design-stage accessibility (Stark) £2k-£10k; substantial engineering remediation time (typically 300-800 hours); manual testing with assistive technologies £5k-£20k; accessibility statement publication specific effort. Timeline 4-9 months typical. Enterprise SaaS WCAG 2.2 Level AA: £100k-£500k+ year one, 6-18 months timeline. Ongoing: £15k-£200k annually depending on scope.

Why choose WhiteStone Infotech for wcag 2.2 for saas compliance advisory?

WhiteStone has shipped SaaS products with specific accessibility compliance for enterprise and public sector customers across our 50-plus product portfolio. SAGE US enterprise with specific accessibility requirements. UK B2B SaaS products with specific accessibility compliance for UK public sector and UK enterprise customers. SaaS CTO case: WCAG 2.2 Level AA conformance programme with Deque audit plus axe DevTools in CI/CD plus manual testing with assistive technologies at 7-month timeline unlocked £120k US enterprise plus £85k UK public sector customer deals (£205k combined ACV). Investment £35k audit plus £8k axe DevTools plus substantial team time with ROI from customer deal unlock plus future-proofing against EU Accessibility Act 2025. Accessibility engineered from design stage with Stark delivers substantially better outcomes than late-stage remediation. Overlay widget quick-fix pitch must be rejected; proper accessibility engineering programme is only true solution. Contact WhiteStone Infotech at whitestoneinfotech.com/contact.

The One Thing to Remember

Wcag 2.2 for saas in 2026 is the dominant accessibility standard following W3C publication of WCAG 2.2 as W3C Recommendation in October 2023. WCAG 2.2 includes all WCAG 2.1 success criteria plus 9 new success criteria including new Level AA criteria (Focus Not Obscured, Target Size Minimum at 24 by 24 CSS pixels, Consistent Help, Redundant Entry, Accessible Authentication). 2026 regulatory landscape substantially broader than 2020: EU Accessibility Act 2025 from June 2025 applies to specific private sector including ecommerce, banking, telecoms, specific other services; UK Equality Act 2010 general duty plus Public Sector Bodies Accessibility Regulations 2018 for public sector; US ADA Title III extended to specific websites through case law plus Section 508 for federal government procurement. 2026 testing tools: axe DevTools by Deque (dominant developer-focused automated), WAVE by WebAIM, Siteimprove, Pope Tech, Level Access, Stark (Figma design-stage), Lighthouse. Automated testing catches 30-50 percent of issues; manual testing with assistive technologies (screen readers NVDA, JAWS, VoiceOver, keyboard-only navigation) catches remaining. Honest position on overlay widgets (UserWay, accessiBe, Equally AI): do not deliver true WCAG compliance per W3C and accessibility community; legal risk documented; proper accessibility engineering programme is only true solution. SaaS CTO case: WCAG 2.2 Level AA conformance programme with Deque audit plus axe DevTools in CI/CD plus manual testing with assistive technologies at 7-month timeline unlocked £205k combined ACV US enterprise and UK public sector customer deals. The single decision that determines SaaS accessibility compliance ROI: WCAG 2.2 Level AA target with proper accessibility engineering programme (automated testing in CI/CD plus manual testing plus design-stage accessibility with Stark), or overlay widget quick-fix pitch with no true WCAG compliance and documented legal risk? WCAG 2.2 Level AA with proper engineering delivers true accessibility plus enterprise customer unlock plus regulatory future-proofing.