Accessibility requirements for SaaS / B2B Software websites

Regulations that apply

SaaS / B2B Software sits at the intersection of general digital-accessibility law and sector-specific obligations. The most relevant items to track:

• Section 508

  Procurement gate; ACR/VPAT required.

  US federal

• EN 301 549

  Required for tenders and many private buyers.

  EU public sector

• EAA (consumer-facing portions)

  If your product has any consumer-facing surface (e.g. customer support portal), it counts.

  EU

The accessibility risks specific to SaaS / B2B Software

Every industry has its own failure pattern. The combination below is what audits, complaints, and lawsuits in this sector keep returning to. Fixing them clears the most-cited issues without touching every page.

• Custom data tables and dashboards without semantics

  Drag-and-drop builders, virtualised tables, and chart libraries frequently fail 1.3.1 and 4.1.2.

  1.3.1, 4.1.2

• Modals nested in modals (focus chaos)

  Wizard flows that stack dialogs lose focus restoration on close.

  2.4.3

• No VPAT or out-of-date VPAT

  Procurement teams reject vendors without a current ACR.

  all

A short remediation checklist

Most SaaS / B2B Software teams do not need a 200-item audit before they fix anything. They need an ordered list of the highest-impact moves. Start with these and re-audit after each pass.

• Generate or update an ACR/VPAT — Certvo includes a free generator

• Audit the most-used 5 user journeys

• Verify every modal flow restores focus correctly

• Test charts and data tables with NVDA/JAWS

Frequently asked questions

Other industries