Most businesses don’t find out they have an accessibility problem from an audit. They find out from a lawyer.
That’s one of the clearest takeaways from our recent webinar, Web Accessibility in California: The Risks, Reality, and Your Response, hosted by attorney Kelley Simoneaux, Esq. and Tanya Singer, accessiBe’s Litigation Support Specialist. The session drew a wide audience — business owners, designers, marketers, developers, and legal teams — and the questions reflected exactly the kind of uncertainty that makes California’s accessibility environment so challenging to navigate.
Below, we’ve expanded on the questions asked most often during the session.
Missed the live session? You can access the on-demand recording here.
Why California, specifically?
Q: Why does serving California customers increase accessibility lawsuit exposure?
California’s Unruh Civil Rights Act is one of the most powerful enforcement tools for digital accessibility in the country. It allows plaintiffs to seek statutory damages starting at $4,000 per violation — and those damages can multiply across multiple barriers. If emotional distress is established, they can triple.
The Unruh Act also incorporates the federal Americans with Disabilities Act (ADA) by reference, which means an ADA violation is automatically treated as an Unruh violation. Organizations face compounding exposure under both frameworks at once.
Critically, the law applies based on who you serve, not where you’re located. If your website is accessible to California residents, California law may apply to it.
Q: How can accessibility-related costs escalate so quickly?
The cost is rarely just the lawsuit. Organizations dealing with accessibility claims often face multiple layers of impact simultaneously: statutory penalties, legal fees, remediation costs, and operational disruption while teams coordinate a response under pressure. Reputational consequences can follow, particularly if a situation becomes public.
The longer known issues remain unaddressed, the more complex and expensive the outcome becomes. A manageable remediation project looks very different once legal pressure is involved.
Where risk actually comes from
Q: Where do accessibility risks really originate?
Most accessibility risk doesn’t come from bad intentions. It comes from unclear ownership, inconsistent implementation, and treating accessibility as a one-time project rather than an ongoing operational practice.
When no one is clearly responsible for accessibility, work falls through the cracks. New features ship without accessibility testing. Updates introduce barriers that weren’t there before. The website drifts out of alignment with WCAG without anyone catching it — because no one is watching.
Accessibility risk is, at its core, a governance problem.
Q: What are the most common accessibility barriers found on websites?
The barriers that create the most legal exposure are usually the ones that prevent users from completing critical tasks entirely. The most frequently cited issues include:
- Navigation and menu accessibility failures
- Keyboard navigation that breaks without a mouse
- Missing alternative text for meaningful images
- Poorly labeled or unlabeled form fields
- Inaccessible user flows — login, checkout, account management
- Low color contrast
- Screen reader incompatibility
A useful self-test: navigate your website using only a keyboard. No mouse, no touchpad. If you can’t get through the core experience that way, users who rely on keyboard access can’t either — and that’s the kind of barrier that shows up in complaints.
What a defensible approach looks like
Q: What creates a defensible accessibility approach?
Defensibility is built through process and documentation, not through a single point-in-time fix. Organizations that are better positioned when complaints arise are those that can demonstrate ongoing, structured effort. That typically includes:
- Regular accessibility audits across key user journeys
- Clear internal ownership of accessibility work
- Ongoing testing and monitoring
- Documented remediation activity with timelines
- Evidence of continuous improvement over time
Courts often evaluate whether a business made a reasonable effort to improve accessibility. Good-faith, documented effort — even when the work isn’t complete — carries weight. Inaction, particularly when issues are known, does not.
Q: Who should own accessibility within an organization?
Accessibility doesn’t belong to a single department. It spans several functions: legal is concerned with risk and compliance; product and engineering are responsible for implementation; marketing manages content and user experience. When those teams aren’t aligned, accessibility work becomes reactive and inconsistent.
Organizations that manage accessibility most effectively are those where ownership is shared, clearly defined, and supported by leadership.
Testing, audits, and ongoing monitoring
Q: Why are accessibility audits important?
Audits give organizations a current, accurate picture of where barriers exist — before those barriers appear in a complaint. Websites evolve constantly: new pages, new content, new features, new integrations. Without regular website accessibility testing, it’s genuinely difficult to know what your accessibility posture looks like at any given time.
Audits should cover the full site, with particular focus on the high-traffic user journeys where barriers have the greatest real-world impact.
Q: Why is manual testing so important — isn’t automated testing enough?
Automated tools are valuable for efficiently identifying a wide range of issues. But they don’t catch everything. Manual testing — navigating with a keyboard, using a screen reader, moving through a site the way a user with a disability would — surfaces real-world usability barriers that automation misses.
It also creates accountability. When a team has actually experienced what a screen reader user encounters on their site, accessibility decisions tend to carry more weight internally.
Q: How should organizations test accessibility user journeys?
Focus on the flows that matter most: logging in, submitting a form, completing a purchase, accessing a key service. Test those journeys with keyboard-only navigation and with screen readers. Look for the points where a user without a mouse or without vision would get stuck or fail entirely.
Those are your highest-priority remediation targets — and the areas that carry the most legal exposure if left unaddressed.
Demand letters and legal escalation
Q: How do accessibility issues escalate into lawsuits?
It usually starts when a user encounters a barrier that prevents equal access to a digital service. Without clear governance, documentation, or any visible commitment to improvement, there’s little to discourage escalation. The absence of documented remediation effort is often what moves a situation from complaint to legal claim.
Q: What happens when an organization receives a demand letter?
Organizations that aren’t prepared tend to experience immediate disruption. Teams across legal, product, marketing, and engineering need to coordinate quickly — often without processes in place for doing so. Remediation that could have happened on a reasonable timeline suddenly has to happen under legal pressure.
Preparation changes that equation. Organizations with accessibility documentation, audit records, and remediation logs are far better positioned to respond calmly, accurately, and quickly.
Q: As a freelance designer or agency, am I financially exposed if a client declines to implement my accessibility recommendations?
Document everything. Include accessibility recommendations as explicit line items in your proposals and contracts. If a client chooses not to implement those recommendations, have them acknowledge that decision in writing. Keep records.
That documentation creates meaningful separation between your advice and the client’s decision. It demonstrates that accessibility services were offered and deliberately declined — which matters if questions about liability ever arise.
Q: As someone currently using accessWidget, is automation alone sufficient, or does it need to be paired with manual remediation?
No single solution addresses every dimension of accessibility on its own. accessWidget helps automate many accessibility improvements — AI-powered remediations for screen reader compatibility, keyboard navigation, and interface-level adjustments — and supports alignment with WCAG 2.2 AA guidelines. But accessibility programs that hold up over time also include manual testing, ongoing monitoring, and documented remediation workflows.
The strongest accessibility programs combine technology, governance, and operational processes. Each element reinforces the others.
Q: How does accessWidget help with ADA compliance, and how would a court view a site using it if issues still exist?
Courts often look at whether a business made a reasonable effort to improve accessibility. accessWidget contributes to that record — it demonstrates active, ongoing remediation and provides documentation that accessibility work is being done.
accessiBe also provides accessibility scans, manual testing services, customer remediation support, and litigation support resources for eligible customers. That documented history doesn’t guarantee any particular outcome, but it positions organizations considerably better than if no effort had been made.
The key consideration is reasonableness. Organizations that are aware of accessibility gaps and take no steps to address them are in a far weaker position than those actively working to improve.
Q: What PDF audits are conducted by expert services?
PDFs are frequently created without accessibility in mind — especially older documentation or downloadable website resources. And they’re often where the biggest gaps hide.
Accessible PDFs require proper tagging, logical reading order, meaningful alternative text for images, sufficient color contrast, readable font sizing, and keyboard-navigable structure throughout. When those elements are missing, a user relying on a screen reader may not be able to use the document at all.
If critical services or processes depend on PDF documents, and those PDFs aren’t accessible, the entire service experience can become inaccessible — regardless of how well the website itself performs.
Where to go from here
Accessibility in California is an ongoing obligation, not a one-time project. The organizations that handle it well treat it as a continuous practice — auditing regularly, documenting their work, distributing ownership across teams, and improving incrementally rather than waiting for a perfect plan.
If you’re evaluating where your organization stands, a good starting point is an honest look at your highest-traffic user journeys and whether they can be completed without a mouse and with a screen reader. From there, the path forward gets clearer.
Want to talk through your current accessibility program? Press here to speak with an accessibility expert.
