Study: AudioEye detects up to 2.5x more issues than other tools
Get ReportInsurance Website Accessibility: Where P&C and Health Plan Risk Actually Sits
Insurance companies in the U.S. must make their websites and member portals accessible under ADA Title III, and health plans receiving federal financial assistance are also subject to Section 1557 of the Affordable Care Act. Discover what the highest workflows are and how to make them accessible.
Author: Jeff Curtis, Sr. Content Manager
Published: 08/27/2026
)
A policyholder tries to file a claim after a storm damages their roof. A health plan member logs in to find an explanation of benefits (EOB) document. Neither task happens on the marketing site. Both occur within a member portal, and that’s where the insurance accessibility risk actually lies.
Insurance companies in the U.S. are required to make their websites and their member portals accessible under the Americans with Disabilities Act (ADA) Title III. That obligation covers both property and casualty (P&C) insurance and health plans, and it concentrates on the login screens, forms, and documents a member portal runs on.
What follows breaks down the five workflows that fail most often, explains how exposure differs between P&C and health lines, and outlines where to start testing.
Why Insurance Member Portals Concentrate Accessibility Risk
Insurance member portals carry a higher accessibility risk because they concentrate authentication, multi-step forms, dynamic tables, and document downloads, the four patterns that produce a significant amount of Web Content Accessibility Guidelines (WCAG) issues.
Each pattern fails in a predictable way.
Authentication and Session Management
Login flows introduce timeouts, and a session that expires without an accessible warning leaves users who navigate more slowly, such as screen reader and switch device users, stranded. This is a WCAG 2.1 Level AA timing requirement, and it is one of the most commonly missed criteria in authenticated environments because automated scans rarely reach the login screen to assess it.
Multi-Step Forms with Validation
Claim filing and quote flows are wizards. When a wizard advances without moving focus or announcing the step change, a screen reader user has no way to know the page has changed. Error handling compounds it: validation messages that appear visually but are not programmatically associated with the field they describe, leaving the user knowing something is wrong but no idea on what or how to fix it.
Dynamic Data Tables
Claim history, benefit summaries, and provider results are tables with sorting and filtering. Sort controls implemented as unlabeled buttons, or tables missing proper heading associations, make the data unreadable in any order.
Document Delivery
Policy documents and EOBs are usually PDFs, and an untagged PDF is functionally a picture of a document. No reading order, no table headers, no headings to navigate by.
AudioEye's 2023 Digital Accessibility Index insurance industry report found that 39% of insurance pages with a form had at least one unlabeled field. Expert testers reviewing top insurance sites found an average of 7 additional barriers across the pages tested, including 4 consistent problems that specifically affected account creation and management. Testers could not operate the login buttons with the keyboard alone, and clicking the buttons produced no announcement or focus change for screen reader users. Those findings describe exactly the workflows a member portal runs on: logging in, filling out a form, and managing an account.
The Five Member Portal Workflows that Fail Most Often
The five insurance member portal workflows that most often fail accessibility testing are claim filing, policy management, document and explanation of benefits (EOB) delivery, the find-a-provider directory or agent finder, and quote and bind. Each one fails in a specific, reproducible way.
Claim Filing
Filing a claim is the highest-stakes transaction in the portal and typically the most complex form on the site: multiple steps, conditional logic, file uploads for photos or documentation, and a review screen. The failures cluster in three places. Wizards move focus without announcing the step change. File upload controls are custom-built and lack an accessible name, so a screen reader announces a button with no indication of what it does. And error summaries at the top of a step are not linked to the fields they reference, forcing the user to hunt.
Policy Management
Viewing and changing coverage means dynamic tables and modal dialogs. Modals that do not trap focus allow keyboard users to tab into the page behind the dialog while it is still open, which is disorienting and often leaves the user unable to return. Coverage comparison tables often use visual layout alone to convey which column belongs to which plan, with no programmatic header association.
Document and EOB Delivery
EOB documents delivered as PDFs are subject to accessibility requirements, and untagged PDFs are among the most common unresolved failures in health plan member portals. The fix is not cosmetic. A PDF needs a tag structure, a correct reading order, and real table headers. Most carriers generate these documents from a template system, which means one template fix resolves thousands of documents. That is the highest-leverage fix available in a portal, and it is routinely deferred because the documents are generated rather than authored.
Find-a-Provider Directory and Agent Finder
Health plans call it a find-a-provider directory. P&C carriers call it an agent or adjuster finder. Structurally, they are the same thing: a filterable, sortable result set, often paired with a map. Two failures recur. Filter and sort controls are built as custom widgets without accessible names or state, so the user cannot tell what is applied. And map-based locators offer no keyboard path and no text alternative for the pins, which makes the map decorative at best and the primary interface at worst.
Quote and Bind
Quote flows collect a large volume of input under time pressure, and they are the flow most likely to be embedded from a third-party rating engine. Embedded iframes inherit whatever accessibility the vendor built, which is often nothing, and they frequently break the page’s focus order at the boundary. A quote flow that cannot be completed with a keyboard is a denial of the carrier’s main service.
)
P&C Insurance: Where the Exposure Sits
A P&C insurance carrier can be sued over an inaccessible website under ADA Title III, and quote, bind, and claim-filing flows are the workflows most often named in these claims.
Overall, website accessibility litigation is active and growing: federal filings rose 27% in 2025(opens in a new tab) to 3,117 cases. Quote and bind and claim filing draw the most attention because a failure there is a denial of service, not an inconvenience. A prospective policyholder who can’t complete a quote form is someone who can’t buy a policy. A policyholder who can’t file a claim can’t access a benefit they’re already paying for.
Agent and adjuster finders follow the same pattern from a different angle. Many carriers still route a meaningful share of their business through agents, making the finder a genuine service entry point rather than a convenience feature. When a map lacks keyboard access, the carrier has effectively closed one of its own distribution channels to a portion of the public.
This was one of the four recurring barriers AudioEye's expert testers encountered across top insurance sites: "Find an Agent" buttons that led to pages with no agent information, leaving no path to reach a prospective agent or start a quote.
Where Health Plans are Most Exposed
Health plans that receive federal financial assistance are subject to Section 1557 of the Affordable Care Act in addition to ADA Title III, which extends accessibility obligations to member portals, explanation of EOB documents, and find-a-provider directories.
That second layer is what separates a health plan’s obligations from those of a P&C carrier. Section 1557 of the Affordable Care Act prohibits disability discrimination in health programs and activities that receive federal financial assistance, thereby bringing a large share of the commercial and managed care markets into scope alongside the ADA.
Three patterns carry the most exposure for a health plan:
Member portal: The member portal itself, for the reasons covered above, with the added weight that a member using it is often trying to resolve a medical bill or confirm care coverage.
EOB documents: These are high-volume documents generated from templates and almost always in PDF format. A member who cannot read an EOB cannot verify what was billed or dispute it.
Find-a-provider directory: These are the most consequential of the three patterns. A member selecting an in-network provider is deciding with direct financial consequences. A directory whose filters cannot be operated via keyboard not only inconveniences the member but also puts them at risk of going out of network.
One thing worth calling out for those unsure which framework applies: commercial carriers and health plans are covered under the ADA Title III. Plans and health systems operated by state or local governments fall under ADA Title II, which carries its own compliance deadlines. If that describes your organization, see ADA Title II web accessibility requirements for healthcare. And if you’re on the provider side rather than the payer side, our guide on digital accessibility in healthcare covers patient-facing content and clinical workflows.
The Insurance Regulatory Overlay
Insurance carriers answer to more than one authority on accessibility, and the stack varies by line of business. Three frameworks matter: ADA Title III as the floor for everyone, Section 1557 of the Affordable Care Act for health plans receiving federal financial assistance, and state insurance regulators whose authority over market conduct is easy to overlook.
ADA Title III
ADA Title III is the baseline for both lines of business. WCAG 2.1 Level AA is the standard U.S. regulators and courts reference for web accessibility, and it is the benchmark against which insurance carriers and health plans should test their member portals. It applies to authenticated portal pages, not only to public marketing pages, which is the point most carriers miss when scoping an audit.
Section 1557 of the Affordable Care Act
The health-plan-only layer, covered above. The practical effect is that a health plan has two independent obligations rather than one, and satisfying the ADA does not negate the need to comply with Section 1557(opens in a new tab).
State Insurance Commissioners and the NAIC
State insurance commissioners regulate insurer conduct, including digital communications. While the National Association of Insurance Commissioners(opens in a new tab) (NAIC) has issued no binding web accessibility standard, market conduct authority gives state regulators a path to act on inaccessible member portals.
One thing worth knowing: there is no NAIC accessibility rule. But insurance is regulated state by state, and commissioners already have broad authority over how carriers communicate with policyholders and handle claims. For example, if a market conduct exam finds members cannot access claim or coverage information in the carrier's own portal, that is something commissioners can act on.
)
What to Test First
Start accessibility testing with the authenticated member portal rather than the public marketing site as portal workflows carry both the highest failure rate and the clearest legal exposure.
Test these five workflows first, in this order:
Authenticated claim filing, keyboard only. Complete the entire flow, including file upload, without a mouse. A failure here usually shows up as a loss of focus or a control that the keyboard cannot reach.
EOB or policy document download, with a screen reader. Open the document and read it start to finish. A failure here usually shows up as content that reads out of order or a table with no headers.
Find-a-provider or agent finder, filter and sort. Narrow results by a filter and change the sort order using only the keyboard. A failure here usually shows up as a control with no label or no keyboard path at all.
Quote and bind, error handling. Submit the form with a missing or invalid field and confirm that the error is announced and tied to that field. A failure here usually shows up as a color-only error indicator or a disabled button with no explanation.
Session timeout warning. Let a session sit idle and confirm that the user gets a clear, adjustable warning before being logged out. A failure here usually shows up as a timeout with no warning.
As you’re testing elements, be sure to use a combination of automated and expert testing. Automated scanning can find 30-50% of issues, but it cannot detect accessibility issues that require judgment, which is why you need a platform that can do both. AudioEye, for example, pairs automation with expert testing for these flows so the authenticated processes that carry the most legal exposure get evaluated by a person rather than by a scan.
How AudioEye Supports Insurance Carriers and Health Plans
The uncomfortable thing about the list above is that most carriers cannot answer it. The portal was built by a vendor, the EOB templates were built by a different vendor, the rating engine is embedded from a third, and no single person owns whether any of it works together. That is not negligence. It is what happens when accessibility is scoped as just a website problem, and the portal never enters the audit.
AudioEye works with insurance carriers and health plans on exactly the surfaces described above: authenticated member portals, generated document templates, and the transactional flows that carry the most risk. Our powerful automation covers the portal continuously at scale. Certified experts, including users with disabilities, work the claim, quote, and directory flows that automation alone can’t reach.
The result is an accessible, compliant portal that works for everyone. Ready to see how AudioEye supports insurance carriers and healthcare providers? Talk to an expert now.
Frequently Asked Questions
Share Article
)
)
)