Web Accessibility Compliance: Standards, Obligations, and Practice

Accessibility stopped being optional some time ago: disability laws, procurement rules, and sector regulations require it, complaints and litigation enforce it, and a meaningful share of users depend on it. The standard is well defined, and organizations still fail it because accessibility is treated as an audit before launch rather than a property of the design system and the pipeline. AI interfaces add streaming output and review controls that need their own patterns. This guide covers obligations, conformance, engineering practice, testing, AI patterns, and documentation, drawing on FISTA Solutions' web and mobile practice. Design system integration is in design system implementation and the designer roles in hire ui ux designers. This article is general guidance, not legal advice; obligations vary by jurisdiction and sector.

Where do obligations come from, and what standard applies?

Source	Typical requirement
Disability and accessibility laws	Accessible public-facing sites and services; complaints and litigation
Public-sector procurement	Conformance to a specified standard level for vendors
Sector regulations	Accessibility in finance, healthcare, education, and government services
Customer contracts	Vendors meet the customer's obligations
Standards	The Web Content Accessibility Guidelines at a specified version and level

Confirm the version and level that applies to your organization and markets, because regulations reference specific ones.

What does conformance require in practice?

Content that is perceivable: text alternatives, captions and transcripts, sufficient contrast, and adaptable structure. Operable: keyboard access to everything, visible focus, no keyboard traps, enough time, and no seizure-inducing content. Understandable: readable text, predictable behavior, labeled forms with error identification and guidance. Robust: valid markup and compatibility with assistive technology. Each is testable, and conformance is verified rather than claimed.

How do design systems make accessibility the default?

Components implement keyboard navigation, focus management, semantic roles, labels, and announcements once; token pairs meet contrast requirements; motion respects reduced-motion preferences; and documentation shows accessible usage. Products that compose from the system inherit accessibility, and audits become verification rather than remediation. The system approach is in design system implementation.

How do pipelines prevent regression?

Automated accessibility checks in CI on components and pages; linting for missing alternatives and labels; visual regression tests that include focus states; accessibility acceptance criteria in definitions of done; and periodic assistive-technology testing scheduled like security testing. Regression is the normal state of accessibility without pipeline enforcement. Performance and accessibility verification steps are in the nextjs performance checklist.

How should testing be done?

Automated tools catch a fraction of issues, mostly structural; manual testing with keyboard only, screen readers on desktop and mobile, magnification, and voice control catches the rest; and testing with users who rely on assistive technology reveals what neither finds. Test critical flows on every release and the full site on a schedule. Mobile-specific practice is in mobile app testing strategy.

How are AI interfaces made accessible?

Streaming output announced through live regions with sensible batching so screen readers are not flooded; citations, confidence, and provenance exposed as accessible text and controls; review and approval actions fully keyboard-operable with evidence readable; progress and cancellation reachable; conversation history navigable; and generated content checked for heading structure, alternatives, and readability. AI features shipped without these exclude the users who might benefit most. Interface patterns are in hire frontend developers and approval interactions in what is a human approval gate.

What about content and media?

Alternatives for images written for meaning, captions and transcripts for video and audio, readable language and structure in copy, accessible documents rather than scanned images, and localized content that stays accessible in every language. Content pipelines, including AI-assisted ones, must produce these by default. Content operations are in how to build an ai content pipeline and localization in the nextjs internationalization guide.

How do you demonstrate compliance?

Audit records against the standard with dates and scope; remediation logs; an accessibility statement describing conformance level, known gaps, and a contact for issues; testing evidence including assistive-technology sessions; and design system documentation. These show good faith and progress when complaints arrive. Record practice parallels ai record-keeping requirements.

What mistakes are common?

Accessibility as a pre-launch audit; automated tools treated as sufficient; custom components that bypass the design system; AI streaming that floods screen readers; PDFs and media without alternatives; and no accessibility statement, so the first contact is a complaint.

What does sound practice look like?

A financial services company builds its site and app on a design system with accessible components and contrast-compliant tokens, runs automated checks in CI, tests critical flows with screen readers each release, tests its AI assistant's streaming and review controls with assistive-technology users, maintains an accessibility statement with a contact, and keeps audit and remediation records. A regulator's inquiry is answered with the records, and the assistant is usable by customers who rely on screen readers. Sector context is in ai in regulated industries.

How FISTA Solutions delivers accessible web and AI interfaces

FISTA Solutions builds design systems with accessibility built in, enforces checks in delivery pipelines, tests with assistive technology, designs AI streaming, citation, and review patterns accessibly, and produces the statements and records that demonstrate conformance. The web and mobile practice delivers the platforms, AI enablement supplies the AI interface patterns, and forward deployed engineers embed with client product teams. The record behind the approach is 150+ projects with 99.9% uptime.

To meet accessibility obligations as a property of your product rather than a pre-launch scramble, message FISTA on WhatsApp, or read design system implementation for the foundation that makes it the default.