Web Accessibility Remediation Archives/Category

WCAG 1.4.10 Reflow: How to Avoid Two-Direction Scrolling
Have you ever visited a page that looks fine at first, but when you zoom in, you have to scroll sideways just to read the content? Or maybe you’ve had to zoom in and out to see everything? We still see this during reviews, even on sites that claim to be “responsive.”

WCAG 2.1 Success Criterion 1.4.10 (Reflow) is the WCAG requirement meant to prevent that. It says digital content needs to adapt to different screen sizes, eliminating the need for horizontal scrolling—even at 400% zoom—without losing functionality or readability.

But because a desktop screen size is defined as 1280×1024 pixels, the criterion effectively requires your site to adjust to fit within a 320×256-pixel frame. That just happens to match older phone widths, so we get sites that work on small mobile devices without requiring two-dimensional scrolling to view content on a page.

It helps to treat this as a zoom issue first. Breakpoints matter, but zooming makes the viewport smaller while users still expect everything to work the same. Kind of nice, right? So don’t write off older phone widths—test across screen sizes.

What WCAG 1.4.10 Reflow Requires

1.4.10 Reflow is about layout adaptability under constraints. When the viewport gets narrow, whether from device size, split-screen, or browser zoom, the page should reorganize so standard content fits within the visible area. Users should not have to scroll in both directions to read or interact with the site’s content.

WCAG points to a width equivalent to 320 CSS pixels for vertically scrolling pages. Testing at 400% zoom is common because the viewport width shrinks as zoom increases. Zoom itself is not the requirement. The requirement is the experience at an equivalent small viewport.

For content designed to scroll horizontally, WCAG uses a height equivalent to 256 CSS pixels. In practice, zoom scales width and height together, so we test at a small width and a small height together when possible, then validate with zoom on real devices when issues show up.

What’s the Difference Between 1.4.4 Resize Text and 1.4.10 Reflow?

Both help users with visual impairments, but they solve different problems. One is about text size. The other is about layout under zoom.

WCAG 1.4.4 Resize Text focuses specifically on making text larger. It requires that users can zoom text up to 200% without needing assistive tools like screen magnifiers, and without the page layout breaking. If you need that extra boost in text size to read comfortably, this criterion keeps content readable and functional at that scale.

WCAG 1.4.10 Reflow, on the other hand, is about layout behavior. This criterion requires that content can be zoomed up to 400% without needing horizontal scrolling. It ensures everything—text, images, buttons—fits within the screen’s width, especially when the effective viewport becomes narrow. The goal is to keep scrolling in one direction (usually up and down), so users aren’t stuck scrolling side to side to follow content.

In short, 1.4.4 scales text, while 1.4.10 makes sure the page layout adapts at high zoom without breaking use.

Why Horizontal Scrolling Hurts Users

When content does not reflow, reading turns into a repetitive pattern: scroll right to finish a line, then scroll left to find the start of the next. We’ve watched users lose their place after each line break because the viewport moved more than the text. The page still “worked,” but reading became the task.

Dr. Wayne Dick’s research on horizontal scrolling links it to increased reading effort and reduced comprehension. In testing, we see the same behavior. Time to complete a task climbs. Errors climb. People abandon the page sooner.

Reflow also reduces physical effort. Horizontal scrolling often requires more precise movement than vertical scrolling. Trackpads, touch gestures, and wheel setups all behave differently. Under magnification, the precision demands go up fast.

Who Gets Blocked When Reflow Fails
- Low vision: You zoom in to read. Your layout should stay readable without side-scrolling.
- Small screens (mobile or split-screen): You have limited width. Your content should reflow so that reading and controls stay in one direction.
- Keyboard or switch controls: You move focus step by step. The focus should remain visible, and controls should not slide off-screen at high zoom levels.
- Cognitive or attention-related disabilities: You follow structure and spacing. Your experience improves when content doesn’t shift sideways or break into hard-to-track fragments.
CSS Fixes That Help Content Reflow

Reflow issues often come from overflow. Fixes tend to work best when you address the cause, rather than hiding the symptom. The work almost always sits at the component level.
- Use Flexbox and Grid with restraint. Start by removing explicit widths. Let items grow and shrink. Add flex-wrap so rows can stack when space is tight. Media queries still matter, but they should not block zoom behavior.
- Keep media inside its container. Set images and video to max-width: 100% (and typically height: auto). Without this, one fixed-width asset can force horizontal scroll at high zoom.
- Let UI expand when text wraps. Test long labels, buttons, and badges. If a label wraps to two lines, the component should grow vertically. Avoid height constraints that clip text.
- Remove shrink blockers in flex layouts. If a flex child refuses to shrink and pushes the page wide, check for min-width (including defaults). Adjust or override when needed so the layout can reflow.
- Handle long strings at the right container. Apply wrapping rules where the overflow originates (not globally). Use options like overflow-wrap: anywhere; or word-break deliberately for URLs, IDs, and unbroken strings.
- Contain exempt content instead of the whole page. For tables, use a scrollable container with overflow: auto. Keep the table’s width intact inside that container. This respects the exception while protecting the rest of the page.
- For exempt sections, isolate scrolling to the section itself. Tables, code blocks, and specialized regions should scroll inside their own containers so the page does not inherit page-level horizontal scrolling.
- Sticky UI needs narrow-viewport rules. Switch fixed positioning to static positioning, collapse UI into a toggle pattern, or reduce footprint so content and focus remain visible.
Reflow Exceptions: Tables, Maps, and More

Some content needs a two-dimensional layout to keep its meaning or function. Data tables with multiple columns are the most common example. Maps, diagrams, video, games, presentations, and interfaces that require persistent toolbars can fall into this category, too.

The exception is limited. If a table qualifies for a two-dimensional layout, the exception applies to the table area. It does not grant permission for the rest of the page to overflow. We have reviewed pages where a wide table forced page-level horizontal scrolling, and then a paragraph below the table also extended off-screen. The table sits under the exception. The paragraph does not. That pattern fails 1.4.10 Reflow.

How to Test WCAG 1.4.10 Reflow

We use two passes. The steps stay the same. Recreate an equivalent small viewport, then try to use the page.

1. Test Reflow in Chrome DevTools

We start in Chrome DevTools and set a custom device size close to 320 by 256. WCAG lists width and height separately, but zoom scales both dimensions together, so testing them together catches common failures.
1. Open DevTools and toggle the device toolbar.
2. Add a custom device near 320×256 and load the page.
3. Look for loss of content, loss of function, overlap, clipping, and page-level two-direction scrolling.
4. Do a quick task run: read a paragraph, open main navigation, tab through a form, trigger an error state, then recover.
2. Validate With 400% Zoom on Real Devices

When we see issues, we confirm with browser zoom at 400% on one or two laptops. The usable viewport changes with browser chrome, OS scaling, scrollbars, and docked windows. We’ve seen pages look fine in an emulated viewport, then fail at 400% because sticky UI took most of the remaining height.

Find the Element Causing Horizontal Scroll
- Set zoom to 400% and get the viewport down to an equivalent narrow width by resizing the window or using responsive mode.
- Watch for page-level horizontal scroll. If it appears, inspect which element is pushing past the viewport. Often, one container causes the full issue.
- Read standard content. If a paragraph requires side-scrolling, that section fails 1.4.10 Reflow.
- Tab through navigation, forms, and core controls. If focus moves off-screen horizontally or ends up behind fixed UI, treat it as a failure pattern tied to reflow behavior.
- Check high-risk components. Tables, carousels, media embeds, code blocks, and long strings. Confirm that the exempt content is contained, and that the surrounding content still reflows.
When the Viewport Shows 318 Instead of 320

If you see 318 in DevTools at 400% zoom, that’s common. Scrollbars and browser chrome reduce available space. Focus on the requirement. Standard content reads and works without two-direction scrolling, at an equivalent small viewport.

Make Reflow Part of Your Release Checks

Start with your highest-traffic templates: article pages, account pages, and form flows. Test them at 400 percent zoom and an equivalent narrow viewport. Fix overflow at the component level, not by forcing page-wide scrolling.

Avoid fixed-width wrappers in core layout. Contain exempt content inside its own scroll region. Constrain media to its container width. Adjust sticky UI rules at narrow widths so content and focus remain visible. Test with real strings and real error states.

At 216digital, we treat 1.4.10 Reflow as part of front-end quality. If you want help validating complex UI patterns and fixing root overflow issues without destabilizing your design system, schedule a complimentary ADA Strategy Briefing.
Greg McNeil

February 20, 2026

WCAG Compliance

1.4.10 Reflow, Accessibility, How-to, WCAG, WCAG Compliance, web developers, web development, Website Accessibility
Web Accessibility for Neurodivergent Users
The internet shapes how you shop, learn, work, and connect. Yet a lot of websites are built around one default way of processing information. Motion draws the eye. Bright banners compete for focus. Alerts slide in. Videos start playing. For some visitors, that feels engaging. For many neurodivergent users, it can feel overwhelming, and it can lead to friction, stress, or early abandonment.

About 15–20% of the population identifies somewhere on the neurodiversity spectrum. That includes people with autism, ADHD, dyslexia, dyspraxia, Tourette syndrome, and other cognitive differences. These are customers, students, employees, and community members. When digital environments are cluttered or unpredictable, getting through a task can take more effort than it should.

Web accessibility must account for this variation. Cognitive accessibility expands the conversation beyond screen readers and keyboard access. It asks whether your interface supports different attention styles, reading patterns, and sensory thresholds. When we design for neurodivergent users, we improve clarity and usability for everyone.

Neurodiversity and Web Accessibility: What It Means Online

Neurodiversity is both a concept and a social movement. It frames neurological differences as part of human diversity rather than defects to correct. The focus shifts from “fixing” individuals to adjusting environments so people can participate on their own terms.

On the web, those differences often show up in how people handle sensory input, interpret meaning, and move through multi-step tasks. When an interface is packed with movement, unclear labels, or high-pressure forms, users spend more energy figuring out the interface than completing their goal. Web accessibility and cognitive accessibility help cut that extra work.

Designing for neurodiversity is also a practical choice for digital teams. When checkout, account creation, or search feels calmer and more predictable, more people finish without restarting, backtracking, or opening support chat. You can see it in fewer abandoned forms, fewer missed steps, and fewer “I can’t find where to click” messages. It also lowers accessibility-related legal risk when your website works in real checkout, account, and form flows the way users expect.

How Neurodivergent Users Experience Websites

Neurodivergence is a spectrum. There is no single profile or single set of needs. Still, certain patterns show up often, and they map closely to practical design and development decisions.

Autism Spectrum Disorder (ASD)

Many autistic users are more sensitive to sensory input and sudden change. Cluttered layouts, rotating banners, unexpected animation, and audio that starts on its own can create overload fast. Clear structure helps: stable navigation, consistent page patterns, and direct labels reduce the effort required to understand what is happening and what comes next.

For web accessibility, the goal is not only to remove barriers but also to keep interactions predictable and reduce sensory strain.

ADHD

For users with ADHD, attention can be pulled away easily by competing elements. Pop-ups, autoplay media, carousels, and dense pages can make it hard to stay on task. Strong visual hierarchy helps: clear headings, short sections, and fewer competing calls to action. Interfaces that break tasks into steps can also support follow-through.

Cognitive accessibility here is about supporting focus and lowering the effort of finding your place again after interruptions.

Dyslexia

Dyslexia can affect decoding and reading flow, especially on text-heavy pages. Long paragraphs, tight spacing, and complex typography increase strain. Readable fonts, generous line height, moderate line length, and clear headings that support scanning can make a major difference. Captions, diagrams, and short summaries can also reduce reliance on continuous reading.

These improvements strengthen web accessibility while making content easier to take in for many readers.

Sensory Integration Differences

Some users experience discomfort from bright colors, flashing UI, or intense visual contrast combinations. Others are impacted by constant movement in the periphery. Giving control matters: respect reduced motion settings, avoid autoplay, and offer options that simplify the interface during focused tasks.

For neurodivergent users, control is often the difference between staying engaged and backing out.

Motor Differences and Interaction Variability

Some neurodivergent users also experience motor planning or coordination challenges. Small click targets, precise drag-and-drop interactions, and time-limited gestures can become barriers. Strong web accessibility basics support this group: keyboard support, visible focus states, logical tab order, and controls that do not require fine motor precision.

These patterns point to a shared goal: reduce overload, remove guesswork, and keep interactions stable.

Neurodiversity in Web Design and Development

Design and development for neurodiversity is the practice of building digital experiences that work across a wider range of attention, reading, and sensory processing styles. It combines web accessibility foundations with cognitive accessibility patterns that reduce mental effort and increase user control.

In practice, this means four things.

1. Reduce Cognitive Load in Web Interfaces

Users should not have to sift through clutter to find the main task. Clear hierarchy, stable layouts, and simple interactions reduce how much a person must hold in working memory. This supports neurodivergent users who can burn out faster under heavy interface demand.

2. Make Labels and Actions Explicit

Labels beat guessing. Buttons, links, icons, and instructions should say what they do. Pages should avoid surprise behaviors like auto-submits or sudden context changes. Predictability supports cognitive accessibility and aligns with consistent behavior in the Web Content Accessibility Guidelines (WCAG).

3. Provide Clear Feedback in Forms and Flows

Neurodivergent users often benefit from small signals that confirm progress. A button state change, a clear success message, or an inline confirmation after a save helps users stay oriented. Feedback should be visible, specific, and calm. The goal is clarity, not noise.

4. Add User Controls for Motion and Distractions

If a product uses animation, dense information, or interactive UI, provide ways to dial it down. Respect reduced motion preferences. Allow users to pause moving elements. Offer a simplified mode for focused tasks when your interface is naturally busy.

This is not about creating a separate “neurodivergent version” of a site. It is about building flexible interfaces that work for more processing styles without creating a separate experience, while still meeting modern web accessibility expectations.

Cognitive Accessibility: Content, Navigation, and Forms

Many of the most effective patterns are not complicated. The value comes from using them consistently and putting them where users feel the most friction.

Use Clear Language That Reduces Rework

Language shapes understanding. Neurodivergent users often benefit from concise, literal communication.
- Avoid jargon and unexplained terms that force people to stop and decode what you mean.
- Replace vague phrases with specific instructions so users do not guess and backtrack.
- Break complex processes into short, ordered steps so users do not lose their place mid-task.
When describing a form field, state what belongs there. When labeling a button, use a clear verb. “Download report” communicates more than an icon alone, and it reduces wrong clicks in task flows.

Create Content Hierarchy for Scanning and Comprehension

Information overload is a common barrier. A structured layout supports scanning and comprehension.
- Headings should describe what the section covers so users can find what they need without rereading.
- Group related ideas under subheadings so pages do not feel like one long block.
- Use bullet lists for sets of instructions so steps do not get buried in paragraphs.
- Keep paragraphs short and focused so users do not abandon the page halfway through reading.
A visible hierarchy guides attention and reduces decision fatigue, which helps users stay oriented on longer pages and during multi-step tasks.

Keep Consistent Navigation and Consistent Labels

Consistency lowers mental effort.
- Keep primary navigation in the same location on every page so users do not have to hunt for it.
- Avoid shifting core elements between templates so users do not have to relearn the site on each page.
- Use consistent labels for actions that do the same thing so users do not second-guess what will happen.
This is a key overlap between cognitive accessibility and WCAG principles like consistent navigation and identification.

Prevent Surprise Submits and Unexpected Page Changes

Selecting a checkbox should not trigger an unexpected submission. Changing a dropdown should not cause a sudden redirect. Users should be able to choose when a step is final.

Buttons such as “Apply,” “Continue,” and “Submit” create clear control points. That control helps prevent accidental submissions, lost progress, and repeated attempts when users are working through forms.

Accessible Error Messages Users Can Fix

Many users abandon tasks when errors feel confusing or punitive.
- Explain what went wrong in direct terms so users do not have to guess.
- Point to the exact field that needs attention so users do not scan the whole page.
- Provide an example when format matters so users can correct it on the next try.
- Keep the message neutral and focused on resolution so it does not add stress to the moment.
This approach supports web accessibility and reduces the restart loop that happens when error states are vague.

Interaction Patterns That Reduce Misclicks

Cognitive accessibility and motor accessibility often overlap in the same UI choices.
- Use larger tap targets for key actions so users do not mis-tap and lose their place.
- Keep spacing between controls so accidental clicks do not trigger the wrong step.
- Support keyboard shortcuts where they make sense, especially in tools and dashboards where users repeat actions.
- Avoid interactions that require precise dragging unless there is a keyboard alternative, since drag-only patterns often cause stalled tasks and drop-off.
Reduce Motion, Autoplay, and Visual Noise in Web Design

Sensory ergonomics should not be treated as an optional layer. It is part of usability, and it directly supports neurodivergent users.

Stop Autoplay Audio and Video

Audio that starts without permission can be distressing. Disable autoplay. If media is essential, require an intentional click to start playback. This aligns with web accessibility expectations and respects user control.

Respect Prefers-Reduced-Motion

Honor prefers-reduced-motion and limit decorative animation. If your site relies on animation for polish, ensure reduced-motion states preserve meaning and do not hide content.

You can also provide a visible “Reduce motion” option for users who want immediate control at the site level.

Contrast Without Glare: Readable Surfaces

Contrast must remain compliant, but extreme combinations can be fatiguing for some readers. Use near-black text on an off-white background when possible. Avoid high-intensity patterns behind text. Keep the reading surface stable.

This supports cognitive accessibility by lowering visual strain without weakening readability.

Typography for Cognitive Accessibility

Readable typography supports scanning and sustained reading.
- Use familiar fonts for body copy.
- Increase line height.
- Keep line length moderate.
- Avoid decorative typefaces for long content blocks.
These choices can help neurodivergent readers, including those with dyslexia, stay oriented while reading.

Focus Mode for Checkout, Portals, and Dashboards

Some interfaces are naturally dense: dashboards, catalogs, learning portals, checkout flows. A simplified mode can reduce distractions by hiding non-essential panels, limiting decorative motion, and calming color intensity while keeping contrast intact.

If you already have personalization features, consider exposing them in one place: text preferences, motion preferences, and distraction controls. Bundling those options makes them easier to find and easier to use.

How to Maintain and Test for Neurodivergent Web Accessibility

Strong intentions do not scale without process. To make this durable, build it into how you design, build, and ship.

Neuro-Inclusive Standards in Components

Define standards for:
- Motion limits and reduced-motion behavior
- Icon labeling and button naming
- Banner and modal rules (when allowed, how dismissed, how often shown)
- Content layout constraints (line length, spacing, hierarchy)
- Feedback patterns (success, error, in-progress states)
When these rules live in components, you stop re-solving the same problem.

Cognitive Accessibility QA Checklist

Alongside your web accessibility testing, include checks that reflect neurodivergent friction points:
- Distraction scan: movement, overlays, competing calls to action
- Predictability scan: does any input trigger surprise changes
- Reading scan: headings, spacing, paragraph density, link clarity
- Task scan: forms, timers, multi-step flows, recovery paths
- Feedback scan: are confirmations visible and clear without being disruptive
These checks catch problems that automated tools usually miss.

Usability Testing With Neurodivergent Participants

Run usability tests with neurodivergent participants when possible. Focus on goal-based tasks: find a product, complete a form, recover from an error, compare options. Watch where people hesitate, restart, or abandon.

Even small rounds of testing can reveal repeat patterns that improve your roadmap.

Moving Toward More Inclusive Digital Environments

Many practices that support neurodivergent users also improve usability for everyone. When you reduce distractions, keep navigation consistent, and design predictable task flows, you lower the effort required to use your site.

Universal design principles account for both common and high-friction scenarios, not only the average user path. With neurodivergence estimates often cited between 15 and 20 percent of the population, these adjustments likely support a larger portion of your audience than you assume, without creating a separate experience.

At 216digital, we treat web accessibility as a practical discipline. That includes evaluating cognitive load, sensory strain, predictability, and clarity alongside WCAG conformance. When you account for neurodivergent needs early, you tend to reduce drop-off in multi-step forms and keep navigation predictable.

If you want a clear next step, schedule an ADA briefing. We’ll review the flows that matter most on your site, flag the patterns that tend to trip people up, and map out fixes. If you want us to handle remediation, we can take that on and stay with you through testing and release.
Greg McNeil

February 19, 2026

Uncategorized, WCAG Compliance

Accessibility, cognitive disabilities, Neurodivergent users, WCAG, Web Accessibility, Website Accessibility
How to Revive Web Accessibility After a Plateau
Most accessibility programs don’t fail suddenly. They stall.

At first, you see progress you can point to. But slowly, fewer people get trained, bug fixing slows down, and the accessibility dashboard plateaus once leadership stops looking at it. In some organizations, accessibility slips from a program back into a short-term project. Then it gets treated as “done” until a customer complaint or a legal demand letter forces attention again.

A plateau isn’t a sign your accessibility program is doomed. It usually means it has outgrown its original structure, leadership model, or how you measure progress. If you want to revive web accessibility, treat it as a system problem. You’re probably seeing repeat issues across templates and shared components, accessibility showing up late in the sprint, and audits that keep flagging the same patterns. Momentum comes back when accessibility is built into planning, design, development, and QA so fixes land as defaults, not one-offs.

Signs Your Web Accessibility Program Has Plateaued

A plateau is easy to miss because work is still getting done. You may be shipping fixes and still seeing the same issues return in the next sprint.

Fix Repeat Accessibility Bugs in Templates and Components

The same patterns show up again and again:
- New components repeat old contrast failures.
- Heading structures get skipped in content work.
- QA logs the same missing label bugs repeatedly.
This points to a reactive approach. You fix what you find after it ships, but the workflow still allows the issue to enter the system again. If you want to revive web accessibility, start with the defect classes you keep re-fixing. That is where your workflow is leaking.

Set Accessibility Goals That Teams Can Execute

If people across your organization cannot name a single accessibility objective for the current quarter, you have likely plateaued. “Meeting the Web Content Accessibility Guidelines (WCAG)” is not a quarterly objective. It’s a baseline. Without specific objectives, your teams lose direction and drift into backlog work.

To make goals usable, connect each one to a habit your teams can repeat. If your goal is time-to-fix, your habit might be weekly triage with agreed severity definitions and named owners. If your goal is component coverage, your habit might be “no new component ships without an accessible pattern and documentation.”

Leadership Visibility: Metrics That Keep Accessibility Funded

Executive enthusiasm is often strongest at launch. Over time, as things “seem fine,” attention fades and influence goes with it.

Quarterly updates that connect accessibility to metrics leadership already cares about can keep it on the agenda. The ones that usually land are customer retention, legal risk, and developer velocity. If you can, include feedback from disabled customers in your research and route that feedback to product owners. It can change decisions because it ties defects to blocked tasks, not a checklist.

Build Accessibility Capability Across Teams

When most accessibility knowledge sits with a small group, demand will eventually exceed capacity. Teams stop asking for help, or they guess. Both paths lead to inconsistent solutions and recurring defects.

If you see one team shipping solid fixes while another team repeats basic failures, that gap is a capability issue. It usually means people don’t have shared patterns, a clear path for questions, or enough training tied to the work they ship.

Metrics That Predict Regressions

If your reporting is limited to only WCAG violations, you are measuring the minimum, not whether your teams are preventing regressions. Compliance tracking matters, but it can hide repeat failure.

Add a few prevention signals so you can tell whether the system is improving, not just whether a scan score moved. Net new accessibility bugs per release, regressions per release, and average time-to-fix are often more useful than raw violation totals.

If you want to revive web accessibility, you need metrics that show prevention and capability, not only defect volume.

Why Accessibility Programs Stall Under Delivery Pressure

Strong programs usually have five basics: a named owner, a real budget, a written accessibility policy, leadership support, and training that people complete.

Those help, but they don’t prevent a stall by themselves. Accessibility often slips when delivery pressure hits, and responsibility spreads out. When everyone can approve, no one is accountable. When everything funnels to one person, you’ve built a bottleneck.

Sustained progress shows up when accessibility is treated like any other release requirement. It has clear checkpoints, assigned decision-makers, and an escalation path when something blocks release. It is part of the workflow, not a separate process.

If you’re trying to revive web accessibility, look for approvals that happen without an accessibility check. That is where regressions enter. It might be a design review that signs off on a new pattern without keyboard behavior defined. It might be a PR review that skips accessible name checks for icon buttons.

The Five Pillars of a Sustainable Accessibility Program

The five elements also need to exist inside each team involved in accessibility, including content, development, QA, support, procurement, and HR. This is where many programs stall: the pillars exist “in theory,” but they do not show up in how teams plan, ship, and support work.

Accountable Owner and Scope

Name an accessibility lead per function or product area, with a clear scope. That may include triage ownership, review responsibilities, pattern decisions, and escalation authority when requirements are not met. If the lead can’t pause a release for a critical blocker, the role is mostly advisory.

Budget for Prevention, Not Only Audits

Budgets should cover more than audits and remediation sprints. Plan for:
- Tooling and test coverage to catch regressions
- Training and onboarding by role
- Time allocation inside the normal delivery capacity
- User testing that includes people with disabilities
- Expert review at high-risk points, such as major releases and design system changes
If you only budget for audits, you are budgeting for detection, not prevention. If you want to revive web accessibility, budget for the work that stops repeats.

Policy as Workflow Gates and Definition of Done

Policies should translate into workflow gates, not just statements. Examples:
- Accessibility acceptance criteria in tickets
- A definition of done that includes accessible names, keyboard behavior, and focus management
- Review checklists for code and QA.
- Vendor requirements and procurement gates
- Support routing and response expectations
Leadership support

Leadership support needs a cadence and a format that stays relevant. Use metrics tied to risk, retention, and delivery efficiency. Share changes over time, not one-time status. Include customer feedback from disabled users where possible.

Training That Sticks: Patterns and Reinforcement

Training should be role-based and reinforced. Pair training with patterns and examples that teams can reuse. Build a way to ask questions that does not depend on one person being available.

Revive Web Accessibility Outside the SDLC

Plateaus can also be reinforced outside delivery.

Procurement Standards for Accessible Vendors

If your SaaS vendors or third-party tools are not accessible, you are creating barriers. Strengthen procurement by:
- Requiring and evaluating VPATs
- Validating claims with hands-on testing
- Adding accessibility language to RFPs and contracts
- Treating procurement as a gatekeeper, not a workaround
If you have frequent accommodation requests tied to internal tools, procurement can reduce friction and reduce churn caused by barriers.

Support Ticket Tagging for Accessibility Issues

Users who hit barriers often contact support. If support cannot identify accessibility concerns or route them correctly, you lose trust and lose useful feedback.

Practical steps:
- Train support to recognize accessibility concerns and gather useful details
- Add tags in your CRM to track patterns by feature and assistive tech.
- Route issues to the right owners with clear SLAs
- Follow up with users when fixes ship.
Using Accommodation Trends to Drive Fixes

Accessibility and accommodations should reinforce one another. When they do not, people fall through the cracks. Connect the accessibility team with the accommodations program, track trends, review SLAs, and use accommodations data to drive upstream fixes, often in procurement.

If your accommodation process is inconsistent, people may have to repeat their needs and justification. That slows response time and increases risk. Document the process, clarify timelines, and reduce repeated burden.

To revive web accessibility, treat internal experience as part of the system. Workplace barriers affect delivery quality and retention.

Build a WCAG 2.1 Plan Your Teams Can Maintain

Programs move forward when they combine shared ownership across roles, training that sticks, and measurable outcomes. When accessibility is embedded into planning, reporting cycles, and daily review habits, it scales with the work instead of fighting the backlog.

That kind of progress is easier to sustain when WCAG 2.1 compliance work is tied directly to your development roadmap, with clear priorities, owners, and release checkpoints. If you want support building that strategy, 216digital can help you do it on your terms. Schedule a complimentary ADA Strategy Briefing so we can review the flows that matter most, confirm what is driving repeat defects, and map a plan that supports your business goals and your users’ needs.
Greg McNeil

February 18, 2026

How-to Guides, Testing & Remediation

Accessibility, How-to, Maintaining Web Accessibility, revive web accessibility, WCAG, Website Accessibility
Google Lighthouse 100? Automated Testing Still Falls Short
A 100 score from automated testing feels good. Your dashboard turns green. The report says you passed every check. It looks complete. On paper, everything looks compliant. It is the kind of result that gets shared in Slack, checked off in a ticket, and filed away as “resolved.”

But that score does not mean people can use your site.

Most automated testing tools are helpful. They catch real barriers and save time. The problem is what they cannot measure. In practice, automated checks tend to cover only a slice of accessibility—roughly 30 percent—because they are limited to what can be evaluated programmatically. The remaining work involves interaction, context, and human judgment. As standards evolve and legal expectations keep tightening, you have to be honest about whether the metrics you rely on still tell the truth—for your business and for your users.

Here is where automated testing leaves gaps that can turn into barriers for users and real exposure for your team.

What Google Lighthouse Checks (and What It Doesn’t)

Google Lighthouse is an open-source tool that audits a web page and reports on several quality signals—most commonly performance, SEO, and accessibility. It is widely used because it is easy to run, easy to share, and it produces a single score that feels objective.

As an accessibility tool, though, Lighthouse is limited.

How Lighthouse Calculates Your Accessibility Score

Like all automated accessibility tests, Lighthouse can miss barriers that affect users (false negatives). It can also flag patterns that are not actually barriers in context (false positives). That is not a knock on Lighthouse. It is a reminder that the tool is only as reliable as what can be measured from code alone.

When Google Lighthouse scores accessibility, it runs a set of pass-or-fail checks and assigns weights to each one. Your final score is a weighted average, which means some failures carry much more impact than others.

A clear example is severe ARIA misuse. Putting aria-hidden=”true” on the body element is heavily weighted because it removes page content from the accessibility tree. When that happens, a screen reader user may not be able to perceive the page at all. Lighthouse penalizes this hard, and it should.

Where Lighthouse Scores Stop and User Experience Starts

Notice what that scoring model reinforces. Lighthouse is evaluating machine-detectable code patterns. It is not validating the full user experience—whether a flow makes sense, whether focus order matches intent, whether labels hold up in context, or whether an interaction is usable with assistive technology.

Google’s own guidance is clear: only a subset of accessibility issues can be detected automatically, and manual testing is encouraged. That is not a minor disclaimer. It defines the boundary of what the score means.

If you use the score as a proxy for accessibility, you are using it outside its intended purpose.

How Automated Accessibility Testing Evaluates Your Site

Automated testing is built for consistency and repeatability. It excels at spotting structural issues that follow well-defined rules. In practice, that usually means it flags things like:
- Missing alt attributes on images
- Low color contrast ratios based on numeric values
- Form fields with no programmatic label
- Empty buttons or links with no text alternative
- Missing language attributes on the html element
- Obvious ARIA errors that break the accessibility tree
Why “Pass” Does Not Mean “Helpful”

Color contrast is another great example. A tool can measure foreground and background values, calculate the ratio, and report whether it meets the Web Content Accessibility Guidelines (WCAG) requirements. For example, SC 1.4.3 Contrast Minimum requires a 4.5:1 ratio for normal text. That matters for users with low vision and color vision differences.

Contrast is another place where automated tools fall short. They can measure color contrast ratios, but they cannot evaluate readability in context. They cannot tell whether your font size and weight work well with that contrast choice, whether visual styling creates confusing groupings in navigation, or whether users can scan the page and understand it easily.

That pattern shows up across most automated checks. Tools confirm that something is present in code; they do not confirm how well it works in context. The scan focuses on individual elements rather than the interactions between them, on static states rather than the workflows people have to move through.

That coverage is useful, but it is thin. It reaches only a narrow slice of accessibility. The rest sits in the gap that automation cannot reach.

The Limits of Automated Accessibility Testing

The issues that stop people usually sit outside what automation can prove. They show up in behavior and context, not in markup alone. That is how a site can “pass” and still fail users.

Keyboard Navigation and Focus Visibility

A tool can confirm that an element is focusable and that a label exists. It cannot verify what using the page with a keyboard actually feels like.

You still need to know:
- All interactive elements can be reached by pressing Tab.
- Focus indicators stay visible and easy to follow.
- Complex widgets like date pickers, autocomplete fields, and modal dialogs work correctly with keyboard-only navigation.
Those answers do not come from scanning markup. Keyboard testing requires human interaction and someone who understands how keyboard users move through web pages.

Screen Reader Output and Meaning

Automation can confirm that text alternatives and labels are present. It cannot confirm what a screen reader announces, in what order, and whether that output is useful in context.

This is where “passes” hide confusion. A tool cannot tell whether the alt text says “image123” or “Yum yum” for a product photo. Both satisfy the requirement. Only one helps a user.

A label can exist but be announced in a way that does not match the visible interface. Alt text can be technically present and still add noise instead of clarity. Errors can appear visually and never be announced at all. The code can look correct while the experience still breaks.

Screen readers also differ. NVDA, JAWS, VoiceOver on macOS, VoiceOver on iOS, and TalkBack all interpret markup in slightly different ways. Automated testing does not account for those differences. It assumes a static model of accessibility, while users operate in dynamic environments.

Understanding, Language, and Cognitive Load

Tools do not measure whether your interface is understandable. They do not know when instructions are dense. They do not notice when terminology shifts from one step to the next or when navigation labels do not match what the page is actually doing.

Key questions stay unanswered:
- When someone scans the page, can they tell what to do next, or is it buried in jargon and extra complexity?
- If they make a mistake, do they have a clear way to recover, or are they forced to start over?
- As users change text size or zoom, does the layout hold together, or does it fall apart?
- For people with cognitive disabilities, do your interface patterns feel consistent and understandable?
Why Manual Accessibility Testing Still Sets the Standard

Automated checks can tell you whether patterns exist in your code. They cannot tell you whether those patterns work when a person tries to complete a task with assistive technology.

Manual testing is where you find the failures that stay invisible in a report. It is also where you verify that “accessible” holds up across the tools people actually use.

In audits, we test with NVDA and JAWS on Windows, VoiceOver on macOS, VoiceOver on iOS, and TalkBack on Android. These tools do not behave the same way, even when the markup looks clean. We also test keyboard-only navigation, voice control, and zoom. Each component is evaluated against a checklist of over 260 items for full WCAG 2.2 coverage.

This is often where perfect automated scores stop feeling meaningful. Forms can look correct on paper, yet labels that technically announce still fail voice control because the spoken target is unclear. Mobile layouts may meet target size rules, while the placement makes taps unreliable. Dynamic regions can update with no announcement at all, so screen reader users lose the thread. Navigation might be valid in markup and still be hard to use when landmarks are noisy, vague, or missing where people expect them.

Manual testing connects those details back to the actual job a user is trying to do.

The Cost of Relying Only on Automated Accessibility Tests

Teams that stop at automated testing tend to learn about the remaining issues the hard way. A user hits a blocker, reports it, and now the problem is public. That carries reputational risk, can become legal risk, and often lands on your team as an urgent disruption instead of planned work.

It is also avoidable.

The cost curve is clear. A full audit that includes manual testing is typically cheaper than defending a claim, rebuilding components that shipped without assistive technology constraints in mind, or patching accessibility after customers have already churned. Teams sometimes rebuild the same feature more than once because the first pass did not account for how screen readers announce changes or how voice control targets labels.

Automated testing is a starting point. A perfect score is baseline hygiene worth maintaining. It is necessary, and still nowhere near enough.

Combining Automated and Manual Accessibility Testing

Lighthouse scores and perfect automated testing results create false confidence. Genuine accessibility depends on both automated and manual testing. Automated checks belong in your everyday development pipeline, catching structural issues early and guarding against regressions. But don’t stop there. Manual testing with assistive technology then fills in the rest of the picture, showing whether people can actually complete tasks.

A better approach is to treat automation as the first pass, but manual testing as the standard of proof. Run automated tests early and often, then make space for keyboard checks, screen reader passes, and voice control scenarios before you sign off on a release.

If you want help putting that kind of testing strategy in place, 216digital can work alongside your team. Schedule an ADA Strategy Briefing with our experts to review your current workflow, understand your risk, and design an accessibility testing plan that pairs automated coverage with focused manual testing where it counts most.
Greg McNeil

February 17, 2026

Testing & Remediation

Accessibility, Accessibility testing, automated scans, automated testing, How-to, Website Accessibility
Accessible Marketing: Design Principles and Tips
Digital marketing teams are usually measured on traffic, conversions, lead quality, open rates, click-through rates, and engagement. Accessibility is rarely the metric people ask about first. But when it gets missed, it can affect all of those numbers — along with brand trust and legal risk.

The upside is that accessible marketing often improves the same things your team already cares about. In fact, you’re probably making accessibility decisions all the time without labeling them that way: how you structure headings, what your links say, whether images have useful alt text, how strong your color contrast is, whether forms are labeled clearly, and whether videos and emails are easy to use.

This checklist is here to help you tighten up the basics across the channels your team already manages. You do not need to fix everything at once. Start with the places people depend on most, build a process your team can repeat, and keep improving from there.

Layouts and Templates

Layouts and templates are a core part of accessible marketing because they shape how people move through your content. When they’re built with accessibility in mind, they make it easier for people to find information, understand hierarchy, and interact with key elements across devices.
Use a clear page structure.

Apply consistent heading hierarchies (H1, H2, etc.) so content sections are meaningful and navigable for screen readers and search engines.

Group related elements logically (headlines, body text, media, CTAs) so users can scan and understand content quickly.
Design templates for accessibility and branding

Include semantic elements and landmarks in your core templates so navigation, main content, and footers are clearly defined across campaigns.

TBuild templates with responsive layouts that work for desktop and mobile, ensuring important information and CTAs remain accessible on all devices.
Balance clarity with visual appeal.

Use whitespace and visual hierarchy to draw attention to key content and CTAs without overwhelming users.

Check color contrast ratios in templates to make sure text and buttons are readable for users with low vision.

Break long content into sections, lists, and short paragraphs for easier reading.
Headings

Headings give your content structure, turning long blocks of text into clear, navigable sections. For many users — especially those using screen readers or keyboard navigation — they are the primary way to move quickly through a page.
Support easy navigation with clear, descriptive headings.

Write meaningful headings (opens in a new tab) that provide insight into the content.

If your website content is longer than three paragraphs, use headings to make it scannable for all users. This is especially helpful in articles, landing pages, and long promotional emails.
Use headings to provide structure.

Ensure that information, structure, and relationships conveyed visually — such as large, bold font for headings — can also be programmatically determined.
Follow the proper heading order.

Use a single H1 for each page or major asset.

Follow heading order in sequence: H1, then H2, then H3.

Don’t skip heading ranks (e.g., jumping from an to an ), which can create confusion for screen reader users.
Don’t use headings for purely visual reasons.

Avoid using headings solely for their size. Decorative headers place random emphasis on content and can confuse screen reader users.

Don’t use bolded text instead of a heading; screen readers will not read it as a heading.
Content

In accessible marketing, the way you write is as important as what you write. Clear, well-structured content reduces cognitive load, supports comprehension, and helps more people follow your message without getting lost or fatigued.
Typography

Use simple typefaces to help avoid guesswork.

Stay close to 16 to 18 pixels for body text, using rem or em units so everything scales cleanly.

Keep spacing between lines and paragraphs consistent to help people keep their place on small screens.
Aim for clarity and understanding.

Use short sentences with one idea per sentence.

Use active voice rather than passive voice, e.g., “Press the button” instead of “The button should be pressed.”

Avoid double negatives, e.g., “Time is not unlimited.”
Make accessible language choices.

Use people-first language (e.g., “people who have visual impairments”) rather than identity-first language (e.g., “blind people”).

Avoid using a disability as a metaphor with negative connotations, e.g., “Uncover blind spots in your reporting.”
Color and Contrast

Color and contrast choices influence whether text, buttons, and key visuals are actually readable. Good contrast supports people with low vision or color blindness and improves legibility for everyone, especially on small screens or in bright environments.
Identify current accessibility gaps.

Use a color contrast checker to test text, icons, and key UI elements.

Pay extra attention to text placed on top of gradients, photos, or video.

Follow at least a 4.5:1 ratio for body text and a 3:1 ratio for larger text.
Be careful about too much contrast.

Avoid pure black text on pure white backgrounds when you can, since very sharp contrast can cause eye strain for some people.

Aim for a color contrast of at least 4.5:1 between foreground and background elements, such as text on a web page.
Don’t rely on color alone.

Do not use color alone to signal errors, required fields, or sale prices.

Pair color with a clear icon, label, or short message.

For charts and graphs, add patterns or textures so users can distinguish items even if they cannot see color well.
Images

Alt text helps translate visual content into usable information for people who rely on screen readers. Focus on the purpose of the image and what the user needs to understand, not a word-for-word visual inventory.
Write descriptive alt text.

Keep descriptions concise but informative.

Lead with the most important information in your alt text description.

If you’re writing alt text for a product image, include key information about style, design, material, or features.

If your image has text (e.g., labels that explain product features), make sure it appears in the alt text or is described nearby on the page.
Write alt text for screen reader users.

Don’t start alt text descriptions with “Image of” or “Picture of,” which will already be announced to screen reader users by the preceding HTML tag.

Avoid stuffing SEO keywords into alt text. Search engines can identify efforts like this, and it can negatively impact the experience for screen reader users.
Links

Clear link text is a small but important part of accessible marketing, especially for screen reader and keyboard users. This is especially important for screen reader and keyboard users who often navigate by jumping through links out of context.
Write descriptive link text.

Don’t use the same wording (e.g., “Learn More” or “Click Here”) for multiple CTAs that trigger different actions or lead to different locations.

If you have multiple CTAs pointing to the same location, use the same wording for each one.

Avoid using “click here” in link and button copy, which implies that a user has a device to click with (e.g., a mouse).
Create links that work with assistive technology.

Provide a link description for any clickable link or image that screen readers will read aloud.

Avoid redundant ARIA roles, which will cause screen readers to announce the element twice, e.g., “Link Link.”
Ensure links make sense on their own

Screen reader users often use keyboard shortcuts to jump between links on a page, so your hyperlinked text should clearly describe what users will get — or where they will be taken — if they activate the link.

Avoid using vague or generic terms like “click here” or “learn more.”
Carousels and Sliders

Carousels and sliders can compress a lot of content into a small space, but they often introduce motion, timing, and focus issues. Making them accessible means giving users control, keeping interactions predictable, and avoiding hidden surprises.
Ensure users can control movement.

Provide visible Pause, Previous, and Next controls that work with both mouse and keyboard.

Avoid auto-advancing slides. If movement is required, ensure users can pause, stop, or hide the carousel at any time.

Keep motion subtle to reduce issues for people with vestibular disorders.
Make carousel content accessible to assistive technology.

Ensure controls are properly labeled with accessible names such as “Next Slide” or “Pause Carousel.”

Use correct roles and semantics. For example, avoid custom div-based controls that lack button semantics unless they are appropriately coded.
Support predictable keyboard navigation.

Make sure the tab order follows a logical flow: carousel → controls → next content.

Avoid trapping focus inside the carousel. Users should be able to move past it without interacting.

Use visible focus indicators on all interactive elements, including arrows, buttons, and pagination dots.
Video Captions and Transcripts

Video and audio content should be understandable whether or not someone can hear, see, or process all of the media at once. Captions, transcripts, and audio descriptions turn time-based content into something more flexible and inclusive.
Provide clear, accessible captions.

Sync your captions to appear on-screen as close as possible to sound effects or dialogue.

Place captions so they don’t interfere with important visual elements on the screen.

Ensure that the controls to turn captions on/off are clearly labeled and easy to see.
Provide audio descriptions

Include audio descriptions of what’s happening on screen, from speaker introductions to descriptions of key visuals or actions.
Turn off autoplay

Autoplay doesn’t give viewers time to set up assistive technology.

If your video has flashing elements, it can trigger seizures.

People who are hard of hearing often turn up the volume on their devices, which can be embarrassing if your video starts playing automatically.
Forms, Lead Flows, and Conversion Points

Accessible marketing shows up clearly in forms and lead flows, where small barriers can block conversions. Forms can make it clear what’s required, support error recovery, and work smoothly for mouse, touch, and keyboard users alike.
Label each field programmatically.

Provide clear labels for all form controls, including text fields, checkboxes, radio buttons, and drop-down menus.
Eliminate keyboard traps

Check that keyboard-only users can tab between input fields using keyboard commands alone.

Use logical tab order so users can move from top to bottom without skipping around.
Provide accessible alternatives

If you use color to indicate missing or required information (opens in a new tab), combine it with another element (such as an error message or icon) for people who cannot see color.

Include an accessible CAPTCHA alternative for people who cannot perceive images visually or distinguish between similar-looking letters.
PDFs & Digital Documents

PDFs and digital documents are often shared as “finished” assets, but they can easily become dead ends for people using assistive technology. Structuring them for accessibility helps ensure reports, guides, and one-pagers remain usable beyond the web page.
Support easy navigation

Set the reading order of each page to ensure that screen readers and other assistive technologies read multi-column content correctly.

Add descriptive text for each link that tells users exactly what will happen — or where they’ll be redirected — if they click the link.

Ensure links are easily distinguishable for sighted users by changing the color and adding an underline.
Avoid tables whenever possible.

Unless carefully constructed, tables can be difficult for screen readers. If you must use a table, be sure to use headers, set the reading order, and clarify all content inside the table.
Provide accessible images

Add descriptive alt text for each image, graphic, and chart.

Add textures and patterns to charts and graphs to help each item stand out as unique and easily identifiable.
Email Campaigns

Email campaigns are often the first touchpoint in a customer journey, so accessibility issues here can stop engagement before it starts. Accessible emails balance design with readable text, meaningful links, and content that holds up across clients and devices.
Add alt text to every image.

Every image in your email should include alt text that describes the image for people who cannot perceive it visually.
Don’t use images as the entire email.

Some brands use image-only emails to achieve more complex designs; however, this can be inaccessible to screen reader users, especially when brands neglect to add descriptive alt text.

Avoid embedding important content like promotional codes or CTAs solely within images — screen reader users will miss this completely.
Email links

Your inline link style should have an underline — color is not enough for people with visual impairments.

For screen reader users, every hyperlink should have anchor text that describes the destination.
Build responsive templates

Maintain readability when zoomed up to 200%. Test your layout at multiple zoom levels to ensure content doesn’t break or require horizontal scrolling.

Structure logical navigation paths through your content with proper heading hierarchy (H1, H2, H3) and a consistent tab order that guides keyboard users naturally to your CTAs.

For maximum inclusivity, always provide plain-text alternatives alongside HTML versions — many users with visual impairments prefer or require this simpler format.
Social Media Content

Social posts reach people in fast-scrolling, noisy environments where clarity really matters. Small accessibility practices — like alt text, captioned videos, and thoughtful hashtag use — make it easier for more people to engage with your content on any platform.
Hashtags

Capitalizing the first letter in each word of a hashtag helps screen readers identify separate words, enabling them to pronounce the hashtag correctly, such as #SummerSale instead of #summersale.

Place hashtags and mentions at the end of the caption when possible.
Add alt text to every image.

Every image in your post — including GIFs — should include alt text. Apps like Instagram and X provide a section for alt text. If there is no dedicated section for alt text, include it in the caption.
Use special formatting in moderation.

Try to avoid special formatting (e.g., ALL CAPS, bold, or underlined text) in captions.

ALL CAPS text can be difficult for people with dyslexia to read.

Bold, italicized, and underlined text are often used to emphasize words — but they aren’t always announced by screen readers, which means screen reader users can miss key information.
Make sure videos are accessible in any environment.

Adding captions to your videos not only makes it so that Deaf and hard-of-hearing viewers can fully enjoy and understand your content, but it also improves the viewer experience for:

People in a noisy environment.

Viewers with learning disabilities or attention challenges.

Those who primarily speak another language.
Place emojis at the end of posts.

When placed within a string of text, screen readers announce emojis with their alt text, disrupting the flow for screen reader users. Placing them at the end helps keep the reading experience smoother.
Testing Your Work With Assistive Technology

Testing is the only way to see how well your accessible marketing holds up. Automated tools can catch common issues like missing labels or low contrast, but they won’t catch everything. Manual testing with assistive technology fills the gaps and shows you how the experience actually feels.
Conduct a Website Audit

Regularly audit your website for accessibility issues using both tools and human feedback. Automated scans can flag missing alt text, poor color contrast, and other structural problems, while real users uncover usability and conversion barriers that tools miss. Use a strategic mix of testing:

Run automated scans like Google Lighthouse or WAVE on key pages to check against the Web Content Accessibility Guidelines (WCAG).

Use color contrast analyzers on visual elements.

Test with a screen reader such as VoiceOver or NVDA across pages, emails, and forms.

Gather direct feedback from people with disabilities to identify critical issues and friction points.

Document each improvement to track progress, share wins with stakeholders, and demonstrate ROI over time.
Want to go deeper? Explore our full accessibility testing guide.
Implement Ongoing Training

Many accessible marketing gaps come down to knowledge gaps. Equip your team with training designed specifically for marketers, with a focus on practical implementation, common pitfalls, and real-world examples rather than just theoretical standards.
Stay Informed and Up-to-Date

Accessibility laws, WCAG updates, and court decisions change over time. When requirements shift, a fresh audit helps confirm your site still meets current expectations and highlights any new risks. Helpful references:

W3C Web Accessibility Initiative (WAI)

WebAIM

WAVE toolbar

ADA.gov

A11y Project
Ongoing Monitoring

Strong accessible marketing depends on ongoing monitoring, because websites and campaigns change constantly. Audits are essential, but websites change constantly — new products, campaigns, and content can all introduce new issues. a11y.Radar by 216digital provides real-time monitoring and compliance tracking so you can maintain continuous accessibility and fix problems early, before they turn into larger operational or legal risks.
Building Accessible Marketing That Lasts

Strong accessibility work doesn’t happen all at once — it builds as your team gains confidence, learns what to look for, and integrates accessible habits into everyday decisions. Every improvement you make helps your accessible marketing become more usable, consistent, and effective over time.

If you want support turning these practices into something your team can maintain long-term, 216digital is here to help. After a remediation project, we provide targeted training to help your developers, designers, and marketing department keep accessibility woven into their workflow so standards don’t slip with each new release or campaign.

If you’re ready to build accessibility into how your organization works — not just what it publishes — schedule an ADA Briefing with 216digital. We’ll walk through what you’re shipping, where your biggest risks sit, and the steps that will help your team stay accessible with clarity and confidence.
Kayla Laganiere

February 16, 2026

Digital Marketing, How-to Guides, Uncategorized

Accessibility, Digital Marketing, Marketer, Marketing, WCAG, Web Accessibility, Website Accessibility
Website Accessibility is Critical to Legal Risk Management
As an attorney who has represented hundreds of businesses in cases filed under the Title III of the Americans with Disabilities Act of 1990 (the “ADA”), I have repeatedly seen the legal consequence, expense, and aggravation, that business owners can experience when their website is not ADA compliant. As such, appropriate legal risk management requires an “all hands on deck” approach to website accessibility.

In the modern digital landscape, a website is often the primary storefront for a business. While you may have invested heavily in visual design and user experience, failing to consider accessibility for users with disabilities can expose your company to significant legal risk.

The ADA prohibits discrimination based on disability in places of public accommodation. While the original law was written long before the internet was used in commerce, courts and the Department of Justice (DOJ) have increasingly interpreted “places of public accommodation” to include websites. This interpretation means that if your digital content is not accessible to individuals using screen readers or other assistive technologies, you may be violating the ADA.

The consequences of non-compliance are not theoretical. They involve costly litigation, damage to brand reputation, and mandated remediation that is often more expensive than proactive compliance would have been.

Understanding the Legal Landscape of ADA Website Lawsuits

The surge in ADA website lawsuits has been dramatic and sustained. Plaintiffs and advocacy groups are actively identifying businesses with non-compliant websites and filing complaints in federal and state courts. Many law firms are also sending demand letters threatening litigation.

The Cost of Litigation

For small to medium sized businesses with limited resources, the financial impact of an ADA lawsuit can be significant. When you are sued, you generally face three distinct categories of financial exposure:
1. Plaintiff’s Legal Fees: If the plaintiff prevails or if you settle (which is the most common outcome), you are typically required to pay the plaintiff’s attorney’s fees. Because the ADA is a fee-shifting statute designed to encourage enforcement by private citizens, these fees can quickly escalate into the thousands of dollars.
2. Defense Costs: You must hire your own legal counsel to defend the claim, negotiate a settlement, or guide you through the remediation process. Specialized ADA defense counsel, like my law firm and others, are essential, but represent additional cost burden.
3. Settlement or Damages: Depending on the specific state laws involved (such as the Unruh Civil Rights Act in California or New York State Human Rights Law), you may be liable for statutory damages per violation or per visit. Even without statutory damages, settlements are often paid to resolve the case quickly.
Who Is at Risk?

No industry is immune. My law firm has represented businesses in dozens of industries, from across the United States, and around the world. While early lawsuits tended to target larger corporations, the focus has shifted significantly toward small and medium-sized businesses. Retailers, restaurants, hotels, and professional service providers are frequent targets. If your business operates a website that is interfacing with the public, you are potentially at risk.

Strategic Defenses and Remediation

If you receive a demand letter or are served with a lawsuit, your immediate response is critical. Ignoring the issue will not make it go away; quite the opposite, ignoring the issue is likely to make it worse and more expensive.

Immediate Steps to Take
1. Consult an Expert Defense Attorney: Do not attempt to navigate ADA litigation alone. Contact a lawyer who specializes in ADA defense. A good ADA defense lawyer can evaluate the validity of the claim, determine if the plaintiff has “standing” (the legal right to sue based on actual injury), and advise as to the most cost-effective strategy.
2. Conduct a Comprehensive Audit: You need to know exactly where your website fails. Automated scanning tools are a good start, but they only catch about 30% of errors. A thorough audit requires manual testing by website accessibility experts, like 216digital.
3. Initiate Remediation Immediately: Courts often look favorably upon businesses that demonstrate a swift commitment to fixing the issues. Developing a remediation plan—a roadmap for how and when you will fix the accessibility barriers—can sometimes be used as a defense or leverage in settlement negotiations. Moreover, we have found that once a business is sued, it is likely to be sued again if it does not come into compliance with ADA requirements. This is where a company like 216digital can be critical.
The Role of Accessibility Statements

Posting an accessibility statement on your website is a best practice. This statement should declare your commitment to accessibility, outline the standards you are following (e.g., WCAG 2.1), and provide a contact method for users who encounter difficulties. While a statement alone does not prevent lawsuits, it demonstrates good faith and provides an alternative channel for resolving issues before they escalate to litigation.

The Business Case Beyond Compliance

While the immediate driver for many businesses is avoiding legal action, the benefits of website accessibility extend further.
- Expanded Market Reach: There are over 60 million adults with disabilities in the United States. By making your site accessible, you open your business to a massive, often underserved market segment with significant spending power.
- SEO Benefits: Many accessibility best practices, such as using proper heading structures and alt text, also improve Search Engine Optimization (SEO), helping your site rank higher in search results.
Protect Your Business from Liability

The legal risks associated with non-compliant websites are real and growing. For business owners, the “wait and see” approach is not a viable strategy. The cost of proactive compliance is a fraction of the cost of defending a lawsuit (after which, compliance will still be necessary).

By understanding the legal landscape, adhering to WCAG standards, and working with experienced legal and technical experts, you can mitigate this entirely predictable legal risk, ensure ADA compliance, and become accessible to the maximum possible number of prospective customers.
Kayla Laganiere

February 13, 2026

Legal Compliance

Accessibility Remediation, ADA Lawsuit, Legal compliance, legal risk management, risk mitigation
Accessibility Statement: The Good, Bad, and Ugly
An accessibility statement is one of those pages most teams don’t think about until something forces the issue. A user hits a blocker and asks for help. A procurement review wants proof of process. Or someone internally asks the question no one loves answering: “What can we honestly say about accessibility right now?”

If you already work with Web Content Accessibility Guidelines (WCAG), you know the hard part isn’t writing a few well-meaning lines. It’s making sure the statement matches the lived experience of your site. It needs to be specific enough to help someone plan their next step, careful enough to hold up under scrutiny, and practical enough that it won’t be outdated after the next release.

We’ll walk through the common versions you’ll see online, what they communicate at a glance, and what to include if you want a statement that stays accurate as your site and your workflows keep evolving.

Accessibility Statement Best Practices

WCAG does not require an accessibility statement. That surprises a lot of teams. But “not required” and “not important” are two different things.

A statement helps people understand what to expect and how to get support. It also helps internal teams because it forces clarity. If it feels hard to explain your testing process or your goals, that usually points to a bigger issue. The work may be happening in pieces, but the process is not fully owned yet.

In some cases, publishing a statement is not optional. The Revised Section 508 Standards in the United States apply to many public institutions and require accessibility statements that follow a specific format. And even when an organization is not under Section 508, laws and regulations like the ADA, AODA, or EAA raise the stakes around access and transparency.

There is also a practical reality. When a complaint or demand letter happens, this page gets read. Often early. It shows what you claimed, what you promised, and whether your wording matches the experience. So it is not only communication. It can become evidence.

Missing Accessibility Statement: User and Risk Impact

No page. No link. No mention in the footer or on the contact page.

When a site has no accessibility statement, users are left guessing. If they hit a barrier, they also have no clear way to report it. Many people will not spend extra time searching for a hidden email address. They will leave.

A missing statement usually points to one of three situations:
- Accessibility has not been considered yet.
- It has been considered, but it keeps getting pushed down the list.
- Work is happening, but nobody has taken ownership of communicating it.
None of that helps someone trying to apply for a job, schedule an appointment, pay a bill, or place an order.

It can also create risk. It can look like there is no accessibility process at all. Again, that is not proof by itself. But it is not a good signal.

Boilerplate Accessibility Statement: Copy, Paste, Risk

Boilerplate is easy to spot. It often says “we are committed to accessibility” and references WCAG, but nothing else. No date. No testing details. No contact method that feels monitored. Sometimes it even claims full compliance.

This version is risky for a simple reason. It makes a promise without support.

If the site still has keyboard traps, broken form labels, missing focus states, or confusing headings, users will notice the mismatch right away. The page that was meant to build confidence does the opposite.

Boilerplate also tends to sound the same across many sites. That sameness can read as performative. People have seen it before, and many have learned it does not mean much in practice.

If your statement came from a template, treat it as a draft. It should be reviewed with the same care you would give a checkout flow, an account login, or a support page.

Aspirational Accessibility Statement: Nice Words, Few Details

This one is tricky because it can come from a good place.

Aspirational statements often sound warm and well-intentioned. They talk about inclusion, values, and long-term goals. Some mention employee groups, empathy workshops, or automated tools. The problem isn’t the heart behind it. It’s that none of this helps a user complete a task today.

Where these statements tend to fall short is in clarity. They describe the why but skip the what now. Users trying to pay a bill or submit a form need concrete information, not broad promises about the future. When a statement avoids specifics about testing, current site limitations, or how to get help, it becomes more of a brand message than a resource.

This is also where teams can unintentionally stall. Publishing a warm, values-driven accessibility statement can create the illusion that the work is “handled,” even when the practical steps are still ahead.

How to Write a Good Accessibility Statement

A strong accessibility statement is simple in a practical way. It does not try to sound impressive. It explains what you are doing, what you know, and how users can reach you if they run into a problem.

You can think of it as having a few main ingredients. The exact recipe will vary by organization, but these parts show up again and again in statements that users actually trust.

Purpose and Commitment

Start with a clear handshake. Say you are dedicated to making your website or content accessible, including for people who use assistive technology. Keep it short and human. It should feel like support, not legal language.

Standards and Guidelines (WCAG)

Mention the standard you are aiming for, such as WCAG 2.2 Level AA. If that is your target, say it. If you are still working toward it, you can say that too. Honesty here builds more trust than a bold claim.

Testing Approach and Review Dates

This is where you move from “we care” to “we have a process.”

Include:
- The date of your last accessibility evaluation
- Whether you used automated checks, manual testing, or both
- How often you plan to review the site again
You can also name what you focus on at a high level, like key user flows, forms, templates, and shared components. Users do not need a lab report. They do need to know that testing is not a rumor.

Areas of Success

This part is often missing, but it helps. Call out what is working well today. It tells users where the experience is likely to be smoother, and it shows that accessibility work is not only future tense.

Examples might include:
- Core navigation and main templates reviewed for keyboard and screen reader use
- Improved form labels and clearer error handling in key workflows
- Updates to contrast and focus styling on shared components
Keep this realistic. Don’t oversell. Just help users understand where the site is in better shape.

Areas Needing Improvement

Nobody’s site is perfect, and users already know that. The question is whether you are willing to be honest about it.

List the known problem areas that affect tasks. For example:
- Older pages that still have heading or label issues
- Some PDFs or documents that are not fully accessible yet
- Third-party tools that have accessibility limits, you are working to address
If you can add timelines or priority windows, do it. Avoid vague “we’re working on it” language. A specific window builds confidence because it shows this is planned work, not wishful thinking.

Assistive Technology and Environments Tested

Mention the kinds of environments you consider, such as desktop and mobile, keyboard-only use, and screen readers. A short list helps users understand whether your testing reflects their reality.

Contact Information and Support Process

Provide an easy way to reach out if someone runs into a barrier. Email is a baseline. Some teams also offer a phone number or an accessible form.

Just as important, include a brief note about what happens after someone reaches out. Even one sentence helps. For example, reports are reviewed and routed to the right team.

Where to Place the Accessibility Statement Link

Make sure the statement is easy to find. Put it in the footer, and consider linking it from the contact page as well. If users need a search engine to find it, you are adding friction at the exact moment they need support.

Common Accessibility Statement Mistakes

Even a well-meaning statement can miss the mark. These are the mistakes that show up the most.

Overly Legal or Technical Language

An accessibility statement is not a compliance brief. Write for people. Define acronyms. Use short paragraphs and lists. Make it scannable.

Claims You Can’t Support

Avoid saying “fully compliant” unless you can back it up and keep it true over time. Websites change constantly. A claim that was accurate once can become inaccurate fast.

A safer approach is to describe your goal, your testing, and your process.

No Clear Feedback Path

If there is no clear way to report barriers, the statement fails one of its most important jobs. And if you list an email address, make sure it is monitored.

Burying the Accessibility Statement

Put it somewhere consistent, like a global footer. Users should not have to hunt.

Make Your Accessibility Statement Match Reality

An accessibility statement only does its job if it stays close to reality. As your site changes, the statement should keep pace, reflecting what has been tested, what still needs attention, and how people can reach you when something doesn’t work as expected. If reading your current statement feels uncomfortable or outdated, that’s not a dead end. It’s a useful signal that your process needs clearer ownership, stronger testing language, or a better plan for keeping the page current.

At 216digital, our team is committed to helping you take the steps towards web accessibility on your terms by developing a strategy to integrate WCAG 2.2 compliance into your development roadmap. We offer comprehensive services that not only audit your website for accessibility but also provide solutions to meet ADA compliance requirements.

To learn what more you should do to achieve and maintain accessibility for your team, schedule a Complimentary ADA Strategy Briefing with the experts at 216digital.
Greg McNeil

February 13, 2026

How-to Guides, Legal Compliance, Web Accessibility Training

accessibility statement, Accessibility Statment, How-to, Web Accessibility, Website Accessibility
Why ARIA Links Break More Often Than You Think
Links are supposed to be the easy part. You write a few words, wrap them in an , and move on.

But ARIA links have a way of turning “easy” into “why is this broken in Safari” surprisingly fast. Not because ARIA is bad, and not because links are fragile. It usually happens when we start doing clever things to link text. We hide it. We replace it. We split it into tiny pieces for styling. Then we assume every tool people use will still understand the link the same way.

That assumption is where the trouble starts.

The focus here is understanding why ARIA links break across browsers, what the testing uncovered, and how small markup choices can ripple out into very real barriers for users.

How ARIA Links Get Their Accessible Name

A link needs a name. That name is what tools use to announce it, list it, or make it usable.

In the best case, the name is just the visible text inside the link. Simple, reliable, and supported everywhere.

When we start building ARIA links, we often change that name in one of two ways. We override it with aria-label, or we hide the visible text (often with aria-hidden) and hope ARIA will fill the gap.

Here’s the catch. Screen readers look at the accessibility tree, where ARIA is meant to live. But many browser-native features do not behave like screen readers. Some look at rendered text instead. Some use a simplified “reading view” model. Some apply their own rules to decide what counts as readable content.

So an ARIA label can be “correct” in the accessibility tree, yet still get ignored by other tools that your users rely on.

ARIA Link Patterns That Break Across Browsers

In the original write-up, the author tried a bunch of versions of the same link, including multilingual cases. Three patterns kept causing breakage.

ARIA Links and aria-label on Visible Text

This is a common move. It can happen on purpose, like when someone wants a “cleaner” name, or by accident, like when a component always injects an aria-label.

In the tests, browser speech tools did not treat that aria-label as the link’s name. Edge Read Aloud did not announce the aria-label value for any link. Chrome reader mode text-to-speech did not announce the aria-label value for any link. Safari’s Speech feature did not announce the aria-label value for any link.

So you end up with ARIA links that may sound fine in a screen reader, but feel unlabeled in browser read-aloud tools. That’s a big deal because a lot of people use read-aloud features without ever touching a screen reader.

There’s another issue too. In the tests, the aria-label values were intentionally different from the visible label so it was easy to spot. That mismatch causes a known WCAG barrier (SC 2.5.3 Label in Name), but the practical problem is even simpler. Users hear one thing and see another. That erodes trust fast.

ARIA Links and aria-hidden Inside Links

This one looks harmless until it isn’t.

aria-hidden="true" removes content from the accessibility tree. If the text inside your link is hidden, then for many tools, the label is effectively gone.

In the tests, Chrome Reader Mode visually hid every link with aria-hidden. Firefox Reader Mode visually hid every link with aria-hidden. Edge Read Aloud did not announce links with aria-hidden, regardless of other attributes. Chrome reader mode text-to-speech did not announce links with aria-hidden, regardless of other attributes.

So now your ARIA links can disappear from reader views, or get skipped by speech features, even though they still look clickable on the standard page.

There was also a more subtle interaction issue. When the tester highlighted aria-hidden links, Chrome and Edge wouldn’t let them link to the highlighted text, though that behavior shifted once more content was added. Either way, it’s a reminder that hiding text changes more than announcements. It changes how pages behave.

ARIA Links With Split Text Spans

This is the “design made me do it” pattern. It’s often used for animations, hover effects, or custom typography.

The tests showed it can create a surprising amount of fallout. Text split into letter spans did not auto-translate. Firefox Reader Mode styled span-split links as white instead of blue or purple. Safari Speech jumped past most of the page when it hit span-split text. After that jump, Safari announced subsequent links with the wrong link text, including pulling Korean text for English links. Safari Speech did not announce the span-separated letters and also did not announce the visible word those letters formed.

So you can end up with a link that looks fine, but breaks translation, looks unclickable in reader view, and causes speech tools to lose their place.

That last part is especially rough. When a speech feature starts skipping content or mislabeling later links, the whole page becomes harder to trust. Users can’t just “work around” that.

Cross-Browser Results for ARIA Links

One of the best takeaways from the cross-browser checks is this: these are not edge-case bugs in one browser. Each browser failed in its own way.

Chrome and Edge
- Reader mode and text-to-speech ignored aria-label on links.
- Reader mode hid links when aria-hidden was involved.
- Some selection and “link to highlight” behavior broke around aria-hidden content.
Firefox
- Reader view hid aria-hidden links.
- Span-split links lost normal link styling and showed up as white text.
Safari
- Speech skipped content after span-split links.
- It then announced later links with the wrong label, sometimes in the wrong language.
- It ignored aria-label values for link naming.
If your testing only includes one browser and one screen reader, it’s easy to miss all of this. The links will “work” in the sense that you can click them. But they won’t work the same way for people who browse differently.

Why ARIA Links Break in Reader Mode and Speech

ARIA labels live in the accessibility tree. Many browser reading tools do not rely on that tree the way screen readers do. Instead, they often prioritize what they can extract from rendered text or from a simplified reading model.

On top of that, aria-hidden removes content from the tree, and some tools treat that as “remove from reading,” not merely “ignore for screen readers.” When the visible label is hidden, those tools are left with less content to work with, and the link can become empty or disappear.

Per-letter spans create a different kind of problem. They turn a word into fragments, and many tools don’t rebuild those fragments into a single word reliably. Translation and reading modes are especially sensitive here because they’re trying to extract coherent content, not just replay the DOM.

So the link is still a link, but its label becomes unstable. It might be visible but not readable to speech. It might be readable in one mode but missing in another. It might translate in one browser but not another.

That inconsistency is the barrier.

What Broken ARIA Links Feel Like for Users

When ARIA links fail this way, users don’t experience it as “ARIA isn’t supported.” They experience it as missing information, broken reading flow, or a page that feels unreliable.

Reader Mode can show a page that looks mostly right, but key links are missing. Read-aloud can skip links or move through them without saying their names. Translation can work for paragraphs while navigation or call-to-action links remain untranslated. Links can lose their visual cues in reading view and look like plain text, which makes people hesitate to click.

Speech tools can be the most disruptive. When they jump around, skip content, or start announcing the wrong link text, users lose confidence in the whole page. Even basic tasks like highlighting and sharing text can become awkward when the words inside the link aren’t treated as real text.

None of this requires a screen reader. These are everyday tools. Plenty of users lean on them for fatigue, focus, dyslexia support, language support, low vision support, or just convenience.

Safer Patterns for ARIA Links

You don’t have to give up design. You just need to be careful about what you do to the actual link label.

Keep a real text label in the link. If your link has visible text, keep it as real text inside the <a>. That’s the most stable way to get a consistent accessible name across tools.

Use aria-label only when there is no visible text. Icon-only links are the right case for this. If text exists, it should usually carry the name.

Avoid aria-hidden on link labels. If an icon is decorative, hide the icon. Do not hide the words people need.

Avoid splitting words into separate spans. If you want animation, animate the container, an underline, a background, or a pseudo-element. Keep the word intact.

If you inherit a design system that already does this, treat it like a compatibility issue and add guardrails. Make sure there’s still a readable text node somewhere that tools can use. Keep the visible label aligned with the computed name. Test in Reader Mode and speech features, not only in screen readers.

Quick Tests for ARIA Links

A few fast checks can reveal the same problems that showed up in the browser experiments. These don’t take long, but they make it clear whether your link text holds up beyond a screen reader.
- Open Chrome Reader Mode and confirm the links still appear, still look like links, and keep the right text.
- Use Edge Read Aloud and listen for link names. Watch for links that go silent.
- Try Firefox Reader View and make sure the links keep normal styling instead of turning into plain text.
- Use Safari Speech and watch for skipped sections or incorrect labels on later links.
- Translate the page and see whether link text is translated as a full word instead of letter fragments.
- Highlight link text and check that selection behaves normally across the whole label.
- Inspect the accessibility tree to confirm the computed name matches what’s visible.
- Finish with a screen reader pass as a second layer instead of the only one.
If a link pattern fails any of these, it’s a sign your ARIA links are doing too much.

Sanity-Check Your ARIA Links

If your links have been “mostly fine” in screen reader checks but still feel weird in Reader Mode or read-aloud, you’re not alone. That’s exactly why these patterns are sneaky. They don’t break the click. They break the label, the reading flow, and the trust people build as they move through a page.

The upside is you don’t need a big rebuild to clean this up. Start with one or two link components that get used everywhere. Keep the visible text intact. Be careful with aria-label when text is already on screen. Don’t hide the label with aria-hidden. Avoid splitting words into lots of spans. Then run the quick checks again. When it’s fixed, you’ll hear it right away.

At 216digital, we help teams pressure-test link patterns in the same places users feel these failures. Reader modes, speech tools, translation, selection, and yes, screen readers too. If your components rely on ARIA links or stylized link labels, schedule an ADA Strategy Briefing. We’ll help you tighten the markup so links stay predictable across the tools and browsers your users actually use.
Greg McNeil

February 12, 2026

How-to Guides, Web Design & Development

ARIA, ARIA links, aria-describedby, aria-label, How-to, Web Accessibility, Website Accessibility
How to Use VoiceOver to Evaluate Web Accessibility
Most page reviews start the same way. You scan the layout, tab through a few controls, and make sure nothing obvious is broken. That catches a lot. It just doesn’t tell you what the page sounds like when a screen reader is in charge. Turn on VoiceOver, and the same interface can expose gaps you would never notice visually. A button has no name. The heading structure is thinner than it looks. A menu opens, but nothing announces that anything changed.

On macOS, Apple’s built-in screen reader gives you a direct way to hear what your site is exposing to assistive technology. We’ll cover a practical setup, the few commands that matter most, and a repeatable testing flow you can use on any page.

Why VoiceOver Testing Catches Issues Automated Tools Miss

VoiceOver is a screen reader that ships with Mac devices. When it is turned on, it announces what is on the screen, the role of each element, and its state. It also replaces mouse-first navigation with keyboard navigation so people can move through pages without relying on sight.

Testing with this tool shows how your site appears to the macOS accessibility layer in Safari. You hear whether headings form a usable outline. You find out whether regions are exposed as landmarks. You also learn whether labels give enough context when they are spoken on their own, which is a big deal for links, buttons, and form fields.

Small issues stand out more when they are spoken about. A “Learn more” link might seem harmless when it sits next to a product title. But in a list of links, it turns into five identical options with no meaning. An icon-only button might look clear on screen, but it can be announced as “button” with no name. A form field might look labeled, but if that label is not programmatically connected, the field can be read as “edit text” and nothing else.

VoiceOver is not the only screen reader that matters. NVDA and JAWS on Windows and mobile tools on phones and tablets each have their own patterns. This approach treats macOS testing as one important view into accessibility, not a substitute for broader coverage.

Web Content Accessibility Guidelines (WCAG) requirements still apply the same way. On desktop, the impact of focus order, labeling, and structure becomes more obvious when you stop scanning visually and start moving through a page one item at a time.

Set Up VoiceOver in Safari for Reliable Accessibility Testing

A stable setup makes your testing more dependable over time. You do not need anything complex. A Mac, Safari, and a space where you can hear speech clearly are enough. Headphones help if your office or home is noisy.

Before you run your first pass, set up the few things that will affect your results:
- Turn VoiceOver on with Command + F5
  - On some laptops, you may need fn + Command + F5
- Choose your VO modifier key.
  - Control + Option together, or Caps Lock
- In Safari preferences, go to the Advanced tab and enable “Press Tab to highlight each item on a webpage.”
That Safari setting is easy to miss, but it matters. Without it, you can tab and still skip controls you need to test.

Next, spend a minute in the screen reader settings. Adjust the speech rate to something you can follow without strain. If it is too fast, you will miss details during longer sessions. If it is too slow, you will start rushing and skipping steps. Set the voice and language so they match the primary language of the site.

Different macOS versions and device setups can change where settings live or how certain items are announced. You do not need the “perfect” configuration. What helps most is using one setup consistently, so results are comparable from sprint to sprint.

Turn VoiceOver On and Off Fast During Development

You can enable the screen reader through System Settings under Accessibility, but for regular work, it is worth using the keyboard toggle. Most teams rely on Command + F5 so they can switch quickly.

That quick toggle matters in real development cycles. You might review a component visually, turn VoiceOver on, test it, turn it off, adjust code, and repeat. If enabling and disabling feel slow, the step stops happening.

There is a learning curve. When the screen reader is active, you will use the VO key with other keys for many commands. You also want to know how to pause speech quickly. Pressing Control to stop reading is one of those small skills that make testing feel manageable instead of chaotic.

If you ever want a safe practice mode, turn on Keyboard Help with VO + K. VoiceOver will tell you what keys do without typing or triggering actions. Press VO + K again to exit.

VoiceOver Commands for Web Testing You’ll Use Most

You do not need every Mac keyboard shortcut to run useful tests. A small set covers most web content and keeps the process repeatable across a team.

For reading:
- Read from the top: VO + A
- Stop reading: Control
- Move to next item: VO + right arrow
- Move to previous item: VO + left arrow
For interactive elements:
- Move focus forward: Tab
- Move focus backward: Shift + Tab
- Activate an item: Return or VO + Space
Start with simple, linear navigation. Read from the top and move through items one by one. Ask yourself whether the reading order matches what you see on screen. Listen for controls that do not make sense when heard out of context, like “button” with no name or multiple links with the same vague label.

This pace will feel slower than visual scanning. That is part of the value. The slowness makes gaps in structure, naming, and focus behavior hard to ignore.

Use the VoiceOver Rotor to Check Headings, Links, and Landmarks

Once you can move through a page linearly, the Rotor helps you evaluate structure much faster.

Open the Rotor with VO + U. Use the left and right arrow keys to switch between categories and the up and down arrow keys to move through the items in that category. Common Rotor lists include headings, links, landmarks, form controls, tables, and images.

This is where structural problems become obvious. If the page outline is weak, the Rotor will tell you fast.

Start with headings. Move through the hierarchy and listen for a clear outline. Missing levels, unclear section names, or long stretches with no headings usually mean the structure is not supporting nonvisual navigation.

Next, move to landmarks. This reveals whether regions like header, navigation, main, and footer are present and used in a way that matches the layout. Too few landmarks can make the page feel flat. Too many can create noise.

Then scan links and controls. Duplicate or vague link text stands out when you hear it as a list. Controls with incomplete labeling stand out too. An icon button that looks fine can become “button” repeated several times.

You can also filter Rotor lists by typing. If you are in the headings Rotor and type “nav,” you can jump to headings that contain those characters. Small features like this make VoiceOver testing feel less like wandering and more like a targeted review.

A Repeatable VoiceOver Workflow for Web Accessibility QA

You do not need to run a full audit on every page. A light, repeatable workflow is easier to sustain and still catches a large share of issues.

When you review a new page or a major change:
1. Turn on the screen reader and let it read the beginning of the page.
2. Move through the page in order and note anything confusing or missing.
3. Use the Rotor to review headings, landmarks, links, and form controls.
4. Complete one core task using only the keyboard.
Start by listening to how the page begins. Do you hear a clear main heading early? Does navigation appear when it should? Is anything being read that is not visible or not meant to be part of the flow?

Then move through the content one item at a time. Note skipped content, unexpected jumps, or labels that do not match what you see.

Next, do your structural passes with the Rotor. Headings give you a quick sense of hierarchy. Landmarks show whether regions are exposed and used correctly. Links and form controls expose labeling patterns and repetition.

Finally, test a key journey. Pick a task that matters and complete it with no mouse. That might be searching, opening navigation, filling out a form, or moving through a checkout step. If focus jumps, if a dialog opens without being announced, or if you cannot reach a control, it is not a minor problem. It is a broken path for many users.

Along the way, watch for patterns. Maybe icon buttons from one component set often lack names. Maybe form errors rarely announce. Patterns are the difference between fixing one page and improving the whole system.

High-Impact VoiceOver Checks for Forms, Menus, and Modals

Some parts of a site deserve more focused time because they carry more weight for users and for the business.

Forms and inputs

Fields should have clear labels, including required fields and fields with special formats. Error messages need to be announced at the right time, and focus should move to a helpful place when validation fails. If the error appears visually but VoiceOver does not announce it, users may never know what went wrong.

Navigation menus and drawers

Menus should announce when they open or close. Focus should shift into them when they appear and return to a sensible point when dismissed. A menu that opens visually but stays silent is a common failure.

Modals and other overlays

Modals should trap focus while active and hand focus back cleanly when they close. Users should not be able to tab into page content behind the modal. The modal should also have a clear label so it is announced as a meaningful dialog, not just “group.”

Status updates and confirmation messages

Loading indicators, success messages, and alerts should be announced without forcing users to hunt for them. If an action completes and nothing is announced, users are left guessing.

Tables and structured data

If you use data tables, confirm that headers are associated properly so VoiceOver can announce row and column context as you move. Tables with merged headers or empty corner cells can cause confusing output, so they are worth extra attention.

These areas tend to reveal focus and naming issues quickly, especially when the UI is built from custom components.

VoiceOver Bug Notes That Lead to Faster Fixes

Bringing screen reader testing into your workflow is one of those small shifts that pays off quickly. It helps you catch problems earlier, tighten how your components behave, and ship experiences that hold up under real use.

To keep it sustainable, capture findings in a way that leads to fixes instead of debate:
- Record the page and the component or flow.
- List the steps you took
- Note what you expected to hear.
- Note what you actually heard.
- Explain the impact of completing a task.
- Suggest a direction, such as a missing label, an incorrect role, or a focus not managed.
Short, consistent notes are usually enough. Over time, your team will build a shared understanding of what “sounds right” and what needs cleanup.

Make VoiceOver Checks Part of Your Release Routine

VoiceOver testing can feel slow at first, and that is normal. You are training your ear to notice things your eyes will always gloss over. Keep the scope small, stay consistent, and let the habit build. A quick pass on one key flow each release is enough to change how teams design, label, and manage focus over time. And when you hit a pattern that keeps coming back, that is usually a sign the fix belongs in your shared components, not in one-off patches.

If you want help making this a repeatable part of how you ship, 216digital can support you. We work with teams to weave WCAG 2.1 into their development roadmap in a way that fits their product, pace, and constraints. Schedule a complimentary ADA Strategy Briefing, and we’ll talk through what you’re building, where VoiceOver testing should live, and the next changes that will have the most impact.
Kayla Laganiere

February 11, 2026

How-to Guides

Accessibility, assistive technology, How-to, screen readers, VoiceOver, Web Accessibility, Website Accessibility
Will ADA 30 Days to Comply Act Reduce Website Lawsuits?
Many business owners feel caught in the middle of the rising wave of digital accessibility lawsuits. They may care about access and want to do the right thing, but they also face unclear expectations, inherited platforms, limited resources, and legal threats that arrive with little warning. One week you are focused on running the business. The next, you are triaging risk, trying to understand what went wrong, and figuring out what you can realistically fix and how fast.

H.R. 7668, also known as the ADA 30 Days to Comply Act, is getting attention for that reason. It proposes a notice-and-cure process for certain ADA Title III claims, giving businesses a short window to address reported barriers before a lawsuit can proceed. If you have already faced multiple claims, or you are worried about being targeted next, that window can sound like overdue breathing room. More time to fix. Less pressure to settle.

The catch is what happens during that waiting period, and who pays the cost of the delay. On the web, access often means completing something time-sensitive. A job application, a class registration, a patient portal, a government form, a purchase. This article breaks down what H.R. 7668 would change, why many businesses support it, why advocates see risks, and what actually helps reduce exposure to ADA website lawsuits while still moving accessibility forward.

What H.R. 7668 Would Change

At the center of H.R. 7668 is a notice requirement and a short remediation window before a civil action may be filed under Title III. The proposal is commonly referred to as the ADA 30 Days to Comply Act.

In practical terms, it would require a person to notify a business of an alleged accessibility barrier and give the business 30 days to address it before filing a Title III lawsuit. This could change the timing of ADA Title III website lawsuits by adding a notice step before filing.

Supporters often describe it as a common-sense fix. Many businesses feel they are hit with legal pressure before they even understand what the problem is. They want a chance to respond without being forced into a quick settlement that does not always lead to lasting improvements.

At the same time, digital access is often time-sensitive. If someone cannot apply for a job, complete coursework, access healthcare information, or use a government service when it matters, waiting can mean the opportunity is gone. That tension shows up quickly once the conversation shifts from legal process to real usage.

Why Web Accessibility Issues Repeat

A notice-and-cure approach assumes a business needs a heads-up before it can act. Sometimes that is true. A missing label, a broken link, or an overlooked content update can happen.

But many web accessibility issues repeat because the source is shared.
- A page template has an incorrect heading structure, and that template drives most pages on the site.
- Buttons are built as non-button elements, so keyboard users hit the same wall across menus, filters, and modals.
- Form errors are shown only with color, and the same form pattern is reused in many places.
- A third-party tool is added without testing, then becomes required for checkout, scheduling, or account access.
- New content is published quickly, but the workflow does not include checks for alt text, table structure, or captions.
When issues keep repeating, notice is not the missing piece. A working process is.

This is also where timelines get tricky. If the barrier is tied to a design system or a CMS theme, remediation is not one edit. It can mean code changes, content revision, QA, and sometimes vendor coordination.

Why Businesses Support 30 Days to Comply

Supporters of the ADA 30 Days to Comply Act often frame the 30-day window as basic fairness and focus. Many organizations do not have in-house accessibility expertise. They are juggling older platforms, third-party tools, and competing priorities. When a lawsuit lands first, costs often go to legal defense and settlement pressure instead of to remediation. A notice-and-cure requirement, in that view, creates breathing room so dollars can go toward fixing barriers instead of quick payouts.

That argument is also tied to what the lawsuit data shows about repeat targeting. Of the more than 5,000 digital accessibility lawsuits filed in 2025, 1,427 targeted companies that had already faced an ADA web accessibility claim. In federal court alone, 46 percent of cases involved repeat defendants. Plaintiff firms track litigation history and revisit companies targeted previously for easy wins. When businesses see that cycle, it is easy to understand why some view a portion of filings as driven by litigation incentives rather than by a push for durable accessibility.

It is worth saying clearly that many lawsuits are brought by individuals with disabilities, raising legitimate access barriers. That is part of why this space is so serious. The concern from businesses is that repeat targeting can turn into a pattern where the money goes to settlements instead of fixes, and the underlying site stays vulnerable.

That is the business-side hope behind H.R. 7668. Delay litigation long enough to put resources into remediation first. Bring the focus back to what matters. A site people can use.

Why Advocates Oppose Notice-and-Cure

The civil rights concern does not disappear because repeat filings exist. Notice-and-cure requirements still place the first step on the person who hit the barrier, and that person still experiences the impact in the moment.

If someone cannot complete a time-sensitive task, a 30-day wait can function like a closed door. Even if the site is improved later, the missed opportunity does not come back. That is why disability advocates push back on any model that makes access contingent on a complaint-first process.

This is the tension the ADA 30 Days to Comply Act puts in sharper focus. Businesses want a fair chance to direct resources toward remediation instead of settlements, especially when they fear repeat targeting. People with disabilities need usable access when they arrive, not weeks later.

If policy changes move forward, the measure of success should be practical. Fewer barriers. Faster fixes that hold up over time. Less repeat litigation because the underlying issues were actually addressed.

Pros of the ADA 30 Days to Comply Act

There are situations where notice-and-cure could lead to better outcomes, especially for teams that are willing to act quickly and work on root causes.
- Reduces the rush to settle, giving teams room to invest in fixes.
- Creates a clearer internal trigger for action, especially in organizations where accessibility keeps getting postponed.
- Encourages faster response when barriers are limited, and the team can move quickly.
- Builds public trust when an organization responds with transparency and follow-through.
A notice window can be useful when it leads to real remediation and better practices afterward. The risk is when it becomes a timing shield instead of a change in behavior.

Cons of the ADA 30 Days to Comply Act

Even teams acting in good faith can run into problems with a 30-day cure period, especially in digital systems with complexity and volume.

First, it can increase the number of formal notices. If notice becomes the required entry point, more people will use it. That does not automatically mean bad intent. It can simply reflect the new process.

Second, thirty days can be tight for web remediation. Many issues do not live in one place. Navigation, forms, checkout, account access, PDFs, video libraries, and third-party tools can all be part of the claim. Fixing those well takes planning and testing.

Third, rushed fixes can backfire. A patch on one page does not help if the same component appears across the site. When teams fix symptoms instead of shared patterns, problems return on the next release.

And finally, legal exposure does not disappear. A notice step changes the timeline. It does not remove the obligation. If barriers remain, or if the response is incomplete, litigation can still follow.

This is why H.R. 7668 does not eliminate risk. It changes how the first phase may unfold.

How to Reduce ADA Website Lawsuit Risk

Policy debates tend to focus on process. Lawsuit prevention tends to come down to outcomes. The most reliable way to reduce web accessibility lawsuits is to reduce barriers.

That does not require perfection. It requires repeatable habits that hold up through releases and content changes.

A strong foundation usually includes:
- Clear design and development standards aligned with the Web Content Accessibility Guidelines (WCAG)
- Manual testing paired with automated checks
- A review step that happens before release, not only after complaints
- Content rules that help editors publish accessibly by default
- Review of third-party tools before they become part of critical tasks
- Ownership and documentation so that fixes do not drift between teams
When those pieces exist, accessibility work stops feeling like an emergency cleanup. It becomes maintenance and quality control. That is also when budgets and timelines become more predictable, and repeat issues start to drop.

This is also where web accessibility compliance becomes more predictable. When accessibility is built into design, development, and publishing, it stops being an emergency project and becomes part of quality control.

Whether the ADA 30 Days to Comply Act passes or not, that approach protects users and lowers exposure.

What to Do If You Get an ADA Notice

If a notice-and-cure structure becomes the norm, response quality will matter. Panic leads to shortcuts, and shortcuts create repeat problems.

A practical response plan often looks like this:
1. Acknowledge quickly and document everything.
  Confirm receipt. Log dates. Keep communication in one place.
2. Validate what is being alleged.
  Some claims are accurate. Some are incomplete. Testing helps separate the two. Manual checks matter here.
3. Prioritize critical user journeys first.
  Focus on the paths people need to complete tasks. Navigation, forms, checkout, account access, and core conversions usually come first.
4. Fix at the source when possible.
  If the issue is in a shared component, fix it there. If content is involved, adjust the workflow so the issue does not keep spreading.
5. Track progress with evidence.
  Save tickets, notes, test results, and before-and-after examples. Good records support good faith and reduce confusion later.
A 30-day window can help teams move quickly. It can also expose teams that lack a plan. Either way, being prepared tends to reduce cost, stress, and repeat risk.

Notice-and-Cure and the Future of ADA Website Claims

H.R. 7668 and the ADA 30 Days to Comply Act are often framed as a way to reduce bad-faith lawsuits and give businesses time to fix issues instead of paying settlements. That concern is worth taking seriously, especially when repeated targeting appears in the data.

At the same time, digital access is time-sensitive. Delays can mean missed opportunities and exclusion, even when fixes come later. That is why this proposal draws strong opinions on both sides.

The clearest path forward is still the same. Build accessibility into how websites are designed, developed, and maintained. Reduce barriers at the source. Make fixes that hold up across releases.

That kind of progress is easier to sustain when WCAG 2.1 compliance work is tied directly to the development roadmap, with clear priorities and ownership. If support is needed to build that strategy, 216digital can help you do it on your terms. Schedule a complimentary ADA Strategy Briefing and let’s build a path that supports both business goals and user needs.
Greg McNeil

February 10, 2026

Legal Compliance

ADA 30 Days to Comply Act, ADA Compliance, ADA Lawsuits, Legal compliance, state accessibility laws, Web Accessibility, Website Accessibility

What WCAG 1.4.10 Reflow Requires

What’s the Difference Between 1.4.4 Resize Text and 1.4.10 Reflow?

Why Horizontal Scrolling Hurts Users

Who Gets Blocked When Reflow Fails

CSS Fixes That Help Content Reflow

Reflow Exceptions: Tables, Maps, and More

How to Test WCAG 1.4.10 Reflow

1. Test Reflow in Chrome DevTools

2. Validate With 400% Zoom on Real Devices

Find the Element Causing Horizontal Scroll

When the Viewport Shows 318 Instead of 320

Make Reflow Part of Your Release Checks

Neurodiversity and Web Accessibility: What It Means Online

How Neurodivergent Users Experience Websites

Autism Spectrum Disorder (ASD)

ADHD

Dyslexia

Sensory Integration Differences

Motor Differences and Interaction Variability

Neurodiversity in Web Design and Development

1. Reduce Cognitive Load in Web Interfaces

2. Make Labels and Actions Explicit

3. Provide Clear Feedback in Forms and Flows

4. Add User Controls for Motion and Distractions

Cognitive Accessibility: Content, Navigation, and Forms

Use Clear Language That Reduces Rework

Create Content Hierarchy for Scanning and Comprehension

Keep Consistent Navigation and Consistent Labels

Prevent Surprise Submits and Unexpected Page Changes

Accessible Error Messages Users Can Fix

Interaction Patterns That Reduce Misclicks

Reduce Motion, Autoplay, and Visual Noise in Web Design

Stop Autoplay Audio and Video

Respect Prefers-Reduced-Motion

Contrast Without Glare: Readable Surfaces

Typography for Cognitive Accessibility

Focus Mode for Checkout, Portals, and Dashboards

How to Maintain and Test for Neurodivergent Web Accessibility

Neuro-Inclusive Standards in Components

Cognitive Accessibility QA Checklist

Usability Testing With Neurodivergent Participants

Moving Toward More Inclusive Digital Environments

Signs Your Web Accessibility Program Has Plateaued

Fix Repeat Accessibility Bugs in Templates and Components

Set Accessibility Goals That Teams Can Execute

Leadership Visibility: Metrics That Keep Accessibility Funded

Build Accessibility Capability Across Teams

Metrics That Predict Regressions

Why Accessibility Programs Stall Under Delivery Pressure

The Five Pillars of a Sustainable Accessibility Program

Accountable Owner and Scope

Budget for Prevention, Not Only Audits

Policy as Workflow Gates and Definition of Done

Leadership support

Training That Sticks: Patterns and Reinforcement

Revive Web Accessibility Outside the SDLC

Procurement Standards for Accessible Vendors

Support Ticket Tagging for Accessibility Issues

Using Accommodation Trends to Drive Fixes

Build a WCAG 2.1 Plan Your Teams Can Maintain

What Google Lighthouse Checks (and What It Doesn’t)

How Lighthouse Calculates Your Accessibility Score

Where Lighthouse Scores Stop and User Experience Starts

How Automated Accessibility Testing Evaluates Your Site

Why “Pass” Does Not Mean “Helpful”

The Limits of Automated Accessibility Testing

Keyboard Navigation and Focus Visibility

Screen Reader Output and Meaning

Understanding, Language, and Cognitive Load

Why Manual Accessibility Testing Still Sets the Standard

The Cost of Relying Only on Automated Accessibility Tests

Combining Automated and Manual Accessibility Testing

Layouts and Templates

Headings

Content

Color and Contrast

Images

Links

Carousels and Sliders

Video Captions and Transcripts