CODE-LEVEL ACCESSIBILITY REMEDIATION

Don’t just find
accessibility problems.
Fix them.

EqualAccess. corrects accessibility barriers in the website itself—from forms and navigation to interactive components, themes, templates, and custom code.

We identify what isn’t working, make the technical changes where access and scope allow, and retest the experience to verify the improvement.

  • Manual testing
  • Code-level fixes
  • Assistive technology
  • Verification & retesting
Visual demonstration only. Human experts perform the work, supported by testing tools. Testing and remediation scope varies by project.

We work within your existing platform wherever the implementation can be modified.

FROM REPORT TO WORKING EXPERIENCE

An accessibility report doesn’t fix anything by itself.

An audit tells you where barriers exist. Remediation changes the website so those barriers are no longer present.

That can mean correcting HTML structure, rebuilding a custom component, changing CSS, improving keyboard interaction, fixing form relationships, or making content easier to understand.

EqualAccess. can take the findings beyond the spreadsheet and into the website.

Start with Accessibility Audits & Testing

ONE ILLUSTRATIVE MENU FINDING

  1. AUDIT

    “Keyboard user cannot open menu.”

    A finding identifies the barrier.

  2. TECHNICAL INVESTIGATION

    Find the cause.

    Inspect event handling, semantics, focus, and component state.

  3. REMEDIATION

    Correct the component.

    Change the underlying interaction, then test what changed.

  4. RETEST

    Repeat the affected journey.

    Use keyboard controls and relevant assistive technology.

  5. VERIFIED

    Confirm the tested outcome.

    The menu works as intended in the tested environment.

Finding barriers is step one. Removing them is the part your users actually experience.

REAL REMEDIATION

Accessibility should be built into the website.

We focus on the theme, templates, components, content, and interactions themselves. An accessibility widget or overlay is not a substitute for fixing inaccessible code.

Sometimes the right fix is a better HTML element. Sometimes it needs CSS, JavaScript, ARIA, content changes, or a combination of them.

PATCHING AROUND THE EXPERIENCE

Website accessibility layer

FIXING THE EXPERIENCE
  • HTML
  • CSS
  • JavaScript
  • Content
  • Components
  • Interactions

A more accessible experience

Good remediation focuses on the accessibility outcome—not simply adding more ARIA.

W3C techniques illustrate ways to meet WCAG; the techniques themselves are not mandatory. Read the W3C techniques guidance. Explore WCAG Compliance & Conformance

THE TECHNICAL WORK

From basic HTML problems
to complex user interactions.

Accessibility barriers can exist throughout a website. The remediation scope depends on what testing finds and how the website is built.

01

Structure

<main> · <h1> · <table>

Semantic structure
Correct headings, landmarks, lists, tables, page structure, relationships, and missing or inappropriate HTML elements.
Images & icons
Improve meaningful text alternatives and ensure decorative graphics do not create unnecessary screen-reader noise.
02

Keyboard

Tab · Enter · Escape

Keyboard accessibility
Make navigation, filters, product options, forms, and dialogs reachable and operable without a mouse.
Focus management
Correct missing focus indicators, illogical movement, keyboard traps, focus loss, and focus handling when interfaces change.
03

Forms

Label · Instruction · Error

Forms & validation
Connect labels and instructions, communicate required fields, explain errors, and correct programmatic relationships.
Status & error messages
Make relevant errors, success states, loading messages, cart changes, and search results available to assistive technology.
04

Navigation

Name · State · Interaction

Navigation & menus
Improve submenu behavior, keyboard operation, current states, focus order, skip mechanisms, and mobile navigation.
Accessible names & controls
Correct missing, unclear, duplicated, or inappropriate names for buttons, links, fields, icons, and custom controls.
05

Components

Role · State · Focus

ARIA & dynamic interfaces
Correct roles, states, properties, live updates, expandable controls, and custom widgets where ARIA is appropriate.
Dialogs & modals
Correct naming, initial focus, keyboard access, focus containment, closing behavior, and focus return.
06

Visual presentation

Contrast · Reflow · Zoom

Contrast & visual states
Correct text and interface contrast, visible focus, selected states, and information conveyed only through color where editable.
Responsive & zoom behavior
Address content that disappears, overlaps, clips, or becomes unusable when enlarged or reflowed.

For accessible downloads and non-web documents, explore PDF & Document Remediation.

BEFORE → FIX → VERIFY

See the difference between
finding an issue and resolving it.

Choose an example, inspect the change, and try the corrected interaction. These are isolated demonstrations—not a live accessibility scan or proof that a whole website conforms.

Menu / illustrative example

A menu that works without a mouse.

BEFORE

The dropdown opens on hover, but keyboard users cannot reliably open its links.

User impact Important pages can become unreachable for someone navigating with a keyboard.

THE FIX

Use a native button, expose the expanded state, and support opening, navigating, and closing the disclosure.

Menu code example
<button aria-expanded="false"
  aria-controls="product-links">
  Products
</button>
<ul id="product-links" hidden>…</ul>

The button toggles the list and aria-expanded. Escape closes it and returns focus to the trigger; Tab follows the visible links.

HOW WE VERIFY

Open the menu, move through its links, close it, and repeat the interaction with relevant assistive technology.

Keyboard interaction and expanded state retested.

Illustrative verification outcome. Project results are recorded after expert testing.

Form / illustrative example

An error that explains what needs to change.

BEFORE

“Invalid email” appears visually, but the field is not associated with the error and the change is not announced.

User impact A screen-reader user may not know which field needs attention or how to correct it.

THE FIX

Associate the error with the field, update the invalid state, and communicate the new message appropriately.

Form code example
<input id="demo-email" type="email"
  aria-invalid="true"
  aria-describedby="email-error">
<p id="email-error">
  Enter an email such as alex@example.com.
</p>

A connected label is also required. Validation updates the error message and invalid state; the example uses a polite status message and moves focus to an invalid field.

HOW WE VERIFY

Trigger the error using keyboard controls, read the field and its message with a screen reader, then correct the value and check again.

Error association and feedback retested.

Illustrative verification outcome. Project results are recorded after expert testing.

Modal / illustrative example

A dialog that keeps the interaction together.

BEFORE

A newsletter dialog appears while keyboard focus remains on the page behind it.

User impact Someone using a keyboard can lose context or interact with controls that should be unavailable.

THE FIX

Use an appropriately named dialog with initial focus, focus containment, closing behavior, and focus return.

Modal code example
<dialog aria-labelledby="dialog-title">
  <h2 id="dialog-title">Preferences</h2>
  <button type="button">Close</button>
</dialog>
<!-- Open with showModal(). -->

The native modal dialog makes background content inert. Opening and closing handlers set initial focus and restore focus to the opener.

HOW WE VERIFY

Open and close the dialog with a keyboard and assistive technology, check Escape, and verify where focus goes afterward.

Dialog behavior and focus return retested.

Illustrative verification outcome. Project results are recorded after expert testing.

Product Options / illustrative example

Product choices with names and states.

BEFORE

Color swatches are clickable divs with no reliable keyboard operation, accessible names, or selection state.

User impact A customer may not be able to understand the options or select the product they want.

THE FIX

Use named native radio buttons with a group label and a clear checked state.

Product Options code example
<fieldset>
  <legend>Headphone color</legend>
  <label><input type="radio"
    name="color" value="ivory" checked>
    Ivory</label>
</fieldset>

The full group uses a shared name and unique values. Native radios expose their names and checked states and support arrow-key selection.

HOW WE VERIFY

Choose each option with a keyboard and relevant assistive technology, then review the wider add-to-cart journey within the project scope.

Option names, selection, and keyboard operation retested.

Illustrative verification outcome. Project results are recorded after expert testing.

These snippets illustrate individual patterns, not complete production implementations. W3C guidance on using and testing ARIA patterns.

FLEXIBLE ACROSS PLATFORMS

We remediate accessibility issues across many common platforms.

EqualAccess. can support remediation across a wide range of website technologies.

The exact approach depends on how the website is built, what level of code or platform access is available, and whether third-party tools or vendors control part of the experience.

REMEDIATION WORKFLOWIllustrative

Platform / implementation

  • Shopify theme
  • WordPress theme/plugin
  • Webflow
  • Custom frontend
  • Third-party component

Remediation paths

  • Direct implementationWhere we can access the code
  • Collaborative implementationWith your developer or agency
  • Vendor escalationFor third-party components
  • Retesting & verificationReview the resulting changes

Accessibility issues can often be remediated without rebuilding the website.

Illustrative workflow. Scope is agreed per project.

Where we can access the implementation, we can often make the fixes directly. Otherwise, we can work alongside your developer, agency, or vendor and verify the resulting changes.

COMMON PLATFORMS WE SUPPORT

  • Shopify
  • WordPress
  • WooCommerce
  • BigCommerce
  • Webflow
  • Squarespace
  • Wix
  • Custom Websites & Web Apps

Don’t see your platform? We may still be able to help.

Get a Free ReviewChoose a time on our calendar.

SYSTEMIC REMEDIATION

One good fix can improve hundreds of pages.

Many accessibility problems repeat because they originate in a shared component, template, theme, or design pattern. We look for the source.

Illustrative finding: 83 product pages use the same inaccessible quantity selector.

Rather than handle each page as an unrelated issue, we investigate the shared product template, fix the component, and retest representative pages and relevant variations.

Page 1Page 2Page 3Page 4Page 5Page 6Page 7Page 8Page 9Page 10Page 11Page 12
SHARED PRODUCT TEMPLATE

One component-level correction

Quantity selector: named controls + keyboard operation
Retest representative pages Check how the fix behaves wherever the pattern is used.
Illustrative pattern, not a client result. A shared fix can improve every page that uses it; representative retesting is still needed.

OUR FIVE-STEP PROCESS

A clear technical process
from start to finish.

From understanding the barrier to recording the verified work, every stage has a practical purpose.

  1. 01

    Assess

    Understand what needs attention.

    Review your existing audit or assess the agreed website scope, key journeys, and detectable barriers.

    OUTPUTReviewed findings and agreed scope

  2. 02

    Manual Testing

    Reproduce barriers and set priorities.

    Test keyboard use, screen-reader behavior, and interactions. Prioritize findings by user impact, recurring patterns, severity, and dependencies.

    OUTPUTValidated findings and remediation priorities

  3. 03

    Code-Level Remediation

    Find the source. Make the change.

    Investigate the HTML, CSS, JavaScript, theme, template, component, content, or integration and implement the agreed fixes where access allows.

    OUTPUTUpdated website code, components, or content

  4. 04

    Retest & Verify

    Test the corrected experience.

    Repeat relevant automated, manual, keyboard, and assistive-technology checks, including the affected user journey.

    OUTPUTVerification results for the tested fixes

  5. 05

    Documentation

    Record what changed and what remains.

    Document remediation status, test evidence, developer notes, and limitations that need action from your team or a third-party provider.

    OUTPUTA clear remediation record

After the agreed work, Ongoing Monitoring & Support can help identify regressions as your website changes.

MORE THAN SOURCE CODE

Accessible code still has to produce an accessible experience.

Remediation isn’t complete simply because a line of HTML changed. The resulting interaction needs to be tested.

Depending on the issue and scope, verification can include manual inspection, keyboard and screen-reader testing, automated checks, responsive testing, and review of the complete user journey.

We don’t validate fixes by looking at the code alone.

THE CORRECTED EXPERIENCE, UNDER REVIEW

  1. Code inspection

    Is the markup and behavior appropriate?

  2. Keyboard

    Can someone operate it without a mouse?

  3. Screen reader

    Are names, roles, states, instructions, and changes communicated?

  4. User journey

    Can the person actually complete the task?

  5. Verified fix

    Does the corrected experience address the original barrier?

Read W3C’s overview of accessibility evaluation.

FLEXIBLE REMEDIATION SUPPORT

Use EqualAccess. where
your team needs us.

01

EqualAccess. implements

We investigate, remediate, and retest directly where technically possible, with the access required for the agreed website scope.

BEST FORBusinesses that want the accessibility work handled.

02

Your developer implements

We provide validated findings and technical guidance. Your developer, agency, or engineering team implements the changes; EqualAccess. retests.

BEST FOROrganizations with an established development team.

03

We work together

Your developer handles standard implementation while we work through complex barriers, review proposed fixes, and perform verification.

BEST FORAgencies, e-commerce teams, and businesses with ongoing technical support.

Building your team’s own capability? Explore Consulting & Training.

THIRD-PARTY TECHNOLOGY

Some barriers live
outside your codebase.

Chat, payments, booking tools, review widgets, maps, subscriptions, and embedded forms may be controlled by another provider. If your team cannot change their underlying code, neither can we.

Your website
PaymentBookingChatReview widgetVendor-controlled barrierMapsSubscriptions
Illustrative integration map. Control over each component is assessed during review.
Identify
Confirm the barrier.
Document
Record how it affects the experience.
Configure
Check available settings and implementation changes.
Escalate
Provide technical detail for the vendor.
Work around
Evaluate an accessible alternative path.
Replace
Consider another solution when needed.

We won’t mark a third-party problem “fixed” while the underlying barrier remains.

WHEN THE WEBSITE IS ALREADY UNDER SCRUTINY

The complaint may identify a few barriers.
The website may contain more.

We can investigate the reported issues, evaluate the broader experience, remediate within the agreed technical scope, retest important functionality, and document the work.

ADA Website Lawsuit Support
ILLUSTRATIVE ALLEGATION
“Navigation inaccessible by keyboard.”

Reproduce the issue. Check the shared component. Correct the interaction. Retest and record the result.

Your attorney handles the legal matter.
EqualAccess. handles the website.

WHAT YOU RECEIVE

More than a list
of recommendations.

EqualAccess.

REMEDIATION RECORD · ILLUSTRATIVE

Changes you can trace.

Illustrative remediation record with four verified issues and one issue requiring vendor action.
IssueStatus
Mobile menu keyboard accessVerified
Form error announcementVerified
Product swatch controlsVerified
Third-party review widgetVendor action
Footer contrastVerified

Verified work and outstanding limitations stay separate.

Illustrative report, not a certification or a client result.
Technical remediation
Corrections within the agreed code, themes, templates, components, or content where technically possible.
Issue tracking
A record of the findings being addressed and their current status.
Verification & retesting
Relevant fixes tested again after implementation.
Developer notes
Technical context for your developer, agency, platform provider, or vendor.
Remaining limitations
Known barriers that cannot be resolved within the current scope.
Remediation summary
A record of completed work, verified fixes, and outstanding items.
Optional ongoing support
Continued review as code, pages, components, and integrations change.

Preparing procurement documentation after remediation? Explore VPAT & ACR.

WORK WITH WHAT YOU HAVE

Remediation doesn’t automatically
mean starting over.

Many barriers can be corrected within existing themes, templates, components, and content. We investigate whether the current implementation can be repaired reliably or creates a larger technical limitation.

Identified barrier
REPAIR

Correct what’s there.

Improve the existing implementation.

REFACTOR

Rework the component.

Change a structure that makes reliable accessibility difficult.

REPLACE

Choose a better foundation.

Consider another component or solution when remediation is not practical.

Make the existing experience work better wherever practical.

BUSINESS-CRITICAL ACCESSIBILITY

Can someone actually
complete the task?

WCAG criteria guide technical evaluation. We also test fixes in the context of what the person is trying to do.

E-COMMERCE · ILLUSTRATIVE TESTING SCOPE

Can every customer select the product they want?

  1. 01Browse
  2. 02SelectExample focus for testing
  3. 03Add to cart
  4. 04Checkout
  5. 05Confirmation

Check filters, product names, option controls, cart feedback, checkout errors, and confirmation. A barrier anywhere can interrupt the purchase.

RESTAURANT · ILLUSTRATIVE TESTING SCOPE

Can someone choose a time and complete the reservation?

  1. 01Find location
  2. 02Review menu
  3. 03Choose timeExample focus for testing
  4. 04Reserve

Check location information, accessible menus, date and time controls, booking fields, and confirmation—including vendor-controlled booking tools.

HEALTHCARE · ILLUSTRATIVE TESTING SCOPE

Can someone understand and complete the form?

  1. 01Find service
  2. 02Read information
  3. 03Complete formExample focus for testing
  4. 04Schedule

Check service content, instructions, field labels, required states, error handling, and scheduling interactions within the agreed scope.

SERVICES · ILLUSTRATIVE TESTING SCOPE

Can a prospective client request the service?

  1. 01Understand service
  2. 02Request quoteExample focus for testing
  3. 03Submit information
  4. 04Receive confirmation

Check service navigation, quote controls, form instructions, error feedback, and the final confirmation.

ACCOUNT · ILLUSTRATIVE TESTING SCOPE

Can someone finish the account task without losing context?

  1. 01Sign in
  2. 02Navigate account
  3. 03Update informationExample focus for testing
  4. 04Complete action

Check sign-in fields, account navigation, forms, dynamic updates, focus management, and confirmation of the completed action.

ACCESSIBILITY AFTER THE FIX

The website keeps changing
after the project.

New products, pages, campaigns, apps, plugins, releases, and third-party tools can introduce barriers after remediation. Keep accessibility in the maintenance process.

Explore Ongoing Monitoring & Support
CONTINUITY, AFTER HANDOFF
Remediation verified

The agreed work is documented.

Website update

A new component creates something new to check.

Expert review & support

Assess the change, test it, address new barriers, and record the result.

CODE-LEVEL REMEDIATION FAQ

Common questions about
accessibility remediation.

Website accessibility remediation is the process of correcting accessibility barriers identified through testing. Depending on the issue, this can involve HTML, CSS, JavaScript, content, templates, themes, forms, navigation, or interactive components.

Yes. An audit identifies accessibility problems. Remediation changes the website to address those problems. EqualAccess. can support both the evaluation and the technical remediation process.

Yes, when direct remediation is included in the project and we have the technical access necessary to make the changes. If your internal developer or agency owns implementation, we can instead provide technical guidance and retest their fixes.

In many cases, yes. We first review the existing findings to determine whether they provide enough information and whether the issues still exist on the current website. Additional testing may be needed when the audit is incomplete, outdated, or the site has changed substantially.

EqualAccess. can perform accessibility remediation across a wide range of website technologies where the relevant implementation can be modified.

Common examples include Shopify, WordPress, WooCommerce, BigCommerce, Webflow, Squarespace, Wix, and custom websites and web applications.

The exact approach depends on the platform, site architecture, third-party integrations, and level of technical access available.

Not necessarily. Many accessibility problems can be repaired within an existing website. If a component cannot be reliably remediated, we may recommend refactoring it or replacing it instead.

An overlay or widget should not be treated as a substitute for correcting inaccessible underlying code and content. EqualAccess. focuses on the website itself and the actual user experience rather than relying on a separate layer as the remediation strategy.

ARIA can be useful when native HTML cannot provide the semantics or behavior needed for a component, but adding ARIA is not automatically an accessibility fix. We use native HTML where appropriate and apply ARIA when it supports the required accessible interaction.

The verification method depends on the issue. It may include code inspection, automated checks, keyboard testing, screen-reader testing, responsive testing, and repeating the affected user journey.

Only where the relevant implementation can actually be changed. If the inaccessible code is controlled entirely by a third-party vendor, we can document the barrier and evaluate available configuration changes, workarounds, vendor escalation, or alternative solutions.

No. EqualAccess. provides technical accessibility services, not legal advice, and no accessibility provider can guarantee that remediation will prevent future legal claims. Our work focuses on identifying accessibility barriers, correcting them within the agreed scope, and verifying the resulting experience.

For websites that change regularly, EqualAccess. can continue with ongoing accessibility monitoring, periodic manual testing, remediation support, and verification to help identify new barriers introduced over time.

READY TO FIX THE WEBSITE?

Turn accessibility findings
into working fixes.

Whether you already have an audit or aren’t sure where to begin, EqualAccess. can help identify the barriers, remediate the underlying website, and verify the improvements.

Already have an audit, demand letter, or issue list? We can start by reviewing the work you already have.

Opens in a new tab.