ACCESSIBILITY AUDITS & TESTING

Find the accessibility barriers that actually stop people from using your website.

EqualAccess. combines automated analysis with expert manual testing, keyboard evaluation, assistive technology, and real user journeys to uncover problems a scan alone cannot explain.

Know what’s wrong, where it happens, why it matters, and what needs to be fixed.

  • Automated analysis
  • Manual expert testing
  • Assistive technology
  • Actionable findings
Visual demonstration only; counts are illustrative. Human experts perform the work, supported by testing tools. Coverage and deliverables vary by project.

WCAG-based testing for websites, e-commerce experiences, and web applications.

MORE THAN AUTOMATION

A scanner helps find issues.
It cannot evaluate the whole experience.

Tools quickly flag detectable problems. Human evaluation adds the context needed to understand barriers and turn potential issues into useful findings.

AUTOMATED ANALYSIS

Find technical patterns.

Detectable markup problems, some contrast failures, missing attributes, certain ARIA issues, and repeated patterns across pages.

MANUAL TESTING

Understand the behavior.

Keyboard usability, focus order, meaningful labels, alternative-text quality, forms, dynamic interactions, context, and intent.

ASSISTIVE TECHNOLOGY

Check what is communicated.

Accessible names, roles, states, screen-reader announcements, dynamic updates, and navigation behavior.

USER JOURNEYS

Follow the complete task.

Can someone browse, choose, submit, book, or buy using the important flows on your website?

VALIDATED FINDINGS

A useful audit explains barriers—not just error counts.

W3C explains that knowledgeable human evaluation is required; no tool alone determines accessibility. Read W3C’s evaluation guidance.

THE EVALUATION

We test the parts of your website
people actually have to use.

The scope depends on your platform, important functionality, and the technical accessibility standard agreed for the engagement.

StructureKeyboardFormsFocus
A website, under reviewDEMO
NavigationSearch
PAGE STRUCTUREContent people can navigate.

Headings · Landmarks · Reading order

Image + text alternativeForm + feedbackInteractive component
VisualComponentsScreen readerJourneys
A connected view of the website. The detailed testing areas are below.

Structure & semantics

Headings, landmarks, lists, tables, page language, relationships, and semantic HTML.

Keyboard access

Tab order, operation, traps, shortcuts, menus, controls, forms, and interactive functionality.

Focus

Visible focus, logical movement, focus loss, dialogs, navigation changes, and dynamic content.

Forms

Labels, instructions, required fields, validation, errors, status messages, autocomplete, and submission.

Navigation

Main and mobile menus, dropdowns, skip mechanisms, links, search, breadcrumbs, and consistency.

Images & visual content

Text alternatives, decorative content, icons, charts, visual instructions, and information conveyed by appearance.

Color & presentation

Text and non-text contrast, text spacing, zoom, reflow, orientation, and color-only information.

Interactive components

Accordions, tabs, modals, carousels, filters, product selectors, tooltips, widgets, and dynamic states.

Media

Captions, transcripts, audio-description considerations, controls, and prerecorded content where applicable.

Assistive technology

Names, roles, states, reading order, screen-reader output, dynamic announcements, and component behavior.

Responsive experiences

Desktop and mobile behavior within the agreed scope.

Important user journeys

Checkout, registration, accounts, reservations, booking, quote requests, search, applications, and contact forms.

Define the target with WCAG Compliance & Conformance. For downloadable content, explore PDF & Document Remediation.

REAL TASKS MATTER

Problems often appear
when someone tries to do something.

Your homepage can look accessible while an important workflow is unusable. We look beyond isolated pages to the journeys that matter to your visitors and business.

E-commerce: A purchase depends on every part of the journey working.

  1. 01Browse
  2. 02Choose product
  3. 03Select options
  4. 04Add to cart
  5. 05Checkout
  6. 06Confirmation
Potential barriers to investigate
  • Inaccessible filters
  • Unlabeled product options
  • Cart updates not announced
  • Form errors
  • Keyboard traps

Restaurant: Make the path from finding a location to reserving a table usable.

  1. 01Find location
  2. 02Read menu
  3. 03Choose time
  4. 04Reserve
Potential barriers to investigate
  • Inaccessible menu PDFs
  • Booking widgets
  • Calendar controls
  • Modal focus

Services: Check whether a prospective customer can reach you and understand the response.

  1. 01Understand service
  2. 02Request quote
  3. 03Complete form
  4. 04Submit
Potential barriers to investigate
  • Heading structure
  • Input labels
  • Error messages
  • CAPTCHA
  • Confirmation states

Healthcare: Important information and scheduling need to work together within the tested scope.

  1. 01Find information
  2. 02Choose service
  3. 03Complete intake
  4. 04Schedule
Potential barriers to investigate
  • Forms
  • PDFs
  • Instructions
  • Booking interfaces
  • Third-party portals

People experience a task they’re trying to complete—not a checklist of criteria.

AUTOMATED ACCESSIBILITY ANALYSIS

Inspect more of the website,
then put the results in context.

Depending on scope, we may combine multiple tools and browser checks to identify patterns across pages, templates, and components.

  • Missing accessible names
  • Certain contrast failures
  • Invalid or inappropriate ARIA
  • Missing form relationships
  • Some structural issues
  • Missing image alternatives
  • Markup problems affecting accessibility
  • Repeated template patterns
Page checksMarkup checksTemplate checks
EQUALACCESS. EXPERT REVIEWValidate the finding.
Understand the impact.
Confirmed barrierNeeds manual reviewNot an issue
Illustrative review paths. A tool flag is an input to evaluation, not a final conclusion.

We don’t paste scanner output into a spreadsheet and call it an audit.

W3C guidance on selecting and combining evaluation tools.

MANUAL EXPERT TESTING

Some of the most important questions
require a person.

We interact with navigation, forms, components, content, and workflows to identify barriers that depend on behavior, context, or human judgment.

Illustrative keyboard pathDEMO
Home1 · TabProducts2 · Tab + EnterContact4 · Tab
HeadphonesSpeakers3 · Escape returns to Products
TabTabEnterEscape

Reach it. Open it. Close it. Keep your place.

Static demonstration of a keyboard path. The highlighted location is illustrative and does not move your actual keyboard focus.
Keyboard-only navigation
Can each important control be reached and operated?
Focus order
Does focus move in a logical, predictable sequence?
Visible focus
Can a keyboard user tell where they are?
Content structure
Do headings, landmarks, tables, and relationships communicate meaning?
Alternative text
Does it communicate the image’s purpose, rather than merely exist?
Forms
Are labels, instructions, errors, and state changes understandable?
Dynamic components
Do menus, tabs, filters, and dialogs behave appropriately?
Zoom & reflow
Does the experience remain usable when enlarged or reflowed?

SCREEN READER & ASSISTIVE TECHNOLOGY

What’s on the screen and what’s
communicated can be very different.

Testing helps us evaluate how content, controls, states, instructions, and dynamic changes are communicated through assistive technology.

Visual interfaceDEMO
Everyday headphones
Add to Cart

A clear-looking control can still have an unclear accessible name.

ILLUSTRATIVE SCREEN-READER TRANSCRIPT

BEFORE
“Button.”

The purpose of the control is unclear.

AFTER REMEDIATION
“Add to Cart, button.”

On activation: “Item added to cart.”

Text illustration only. Exact wording varies by screen reader, browser, settings, and implementation. No audio plays.

What we can evaluate
  • Navigation landmarks
  • Heading structure
  • Links and buttons
  • Form labels and errors
  • Names, roles, and states
  • Dialog behavior
  • Dynamic updates
  • Reading order

Screen-reader testing adds evidence. It does not replace the other testing methods.

FROM EXPERIENCE TO FINDING

What does an accessibility
finding actually look like?

Select an example to see the test, the barrier, its user impact, and a practical recommendation. Findings shown here are illustrative and remain open.

ILLUSTRATIVE COMPONENT
Navigation under testDEMO

Global navigation / Products

EA–001 · EXAMPLE FINDINGOpen

Navigation accessibility barrier

Test
Navigate the website using only the keyboard.
Finding
The Products menu opens on mouse hover, but keyboard users cannot reliably open its submenu.
User impact
A person who cannot use a mouse may be unable to reach product categories.
Recommended fix
Use an appropriate interactive trigger, implement keyboard behavior, expose the expanded state, and verify focus behavior.

Illustrative mapping. The final criterion references follow the actual findings and agreed standard.

Next: Code-Level Remediation
ILLUSTRATIVE COMPONENT
Form under testDEMO

Contact form / Email

EA–002 · EXAMPLE FINDINGOpen

Form accessibility barrier

Test
Submit the contact form with a missing required field, using a screen reader.
Finding
The error appears visually but is not programmatically associated with the field.
User impact
A screen-reader user may know submission failed without knowing what to correct.
Recommended fix
Associate the error with the field and communicate the changed error state appropriately, then retest the interaction.

Illustrative mapping. The final criterion references follow the actual findings and agreed standard.

Next: Code-Level Remediation
ILLUSTRATIVE COMPONENT
Product Options under testDEMO

Product template / Color selector

EA–003 · EXAMPLE FINDINGOpen

Product Options accessibility barrier

Test
Choose a product color using keyboard navigation and a screen reader.
Finding
Color options are clickable visually, but are not keyboard operable and do not expose the selected state.
User impact
Some customers cannot configure the product before adding it to the cart.
Recommended fix
Use appropriately named controls with keyboard support and programmatic selection states. Retest product selection and the cart journey.

Illustrative mapping. The final criterion references follow the actual findings and agreed standard.

Next: Code-Level Remediation
ILLUSTRATIVE COMPONENT
Modal under testDEMO

Newsletter dialog / Opening behavior

EA–004 · EXAMPLE FINDINGOpen

Modal accessibility barrier

Test
Open the dialog using keyboard navigation.
Finding
The dialog appears visually, but focus remains on content behind it.
User impact
The user may continue navigating the underlying page without realizing a dialog opened.
Recommended fix
Correct dialog semantics, naming, opening focus, keyboard behavior, closing, and focus return. Verify with keyboard and assistive technology.

Illustrative mapping. The final criterion references follow the actual findings and agreed standard.

Next: Code-Level Remediation

SMART SCOPING

Comprehensive testing doesn’t mean
repeating the same page thousands of times.

Large websites often reuse templates, navigation, forms, and other components. We build a representative scope around meaningful differences and important journeys.

An illustrative 5,000-page store does not automatically need 5,000 separate manual page audits. Shared patterns can be evaluated together, while unique content, page states, and complete multi-step processes need consideration.

Testing scope is agreed before the work begins and clearly recorded in the findings.

010203040506070809101112

Global

Header · Navigation · Search · Footer

Templates

Home · Collection · Product · Content · Account

Journeys

Search · Product selection · Cart · Checkout

Components

Filters · Dialogs · Forms · Carousels

Illustrative scoping model. Representative sampling informs the assessment; it does not automatically establish conformance for every page.

Read W3C’s WCAG evaluation methodology overview.

HOW IT WORKS

From website review
to a clear remediation plan.

Our five-step framework connects testing to the work that follows. An audit provides assessment, expert testing, and documentation; implementation and post-fix verification are scoped separately.

  1. 01

    Assess

    Define the scope. Inspect the patterns.

    Agree pages, templates, components, journeys, environments, and the target standard. Automated analysis identifies candidates for further review.

    OUTPUTDefined scope and initial technical findings

  2. 02

    Manual Testing

    Validate the actual barriers.

    Combine manual, keyboard, assistive-technology, visual, and journey testing. Prioritize findings by impact, recurrence, and remediation needs.

    OUTPUTValidated barriers and a prioritized roadmap

  3. 03

    Code-Level Remediation

    Turn findings into technical changes.

    Your developer can implement the recommendations, or EqualAccess. can remediate where code access and a separate agreed scope allow.

    OUTPUTImplementation, when commissioned

  4. 04

    Retest & Verify

    Confirm the effect of the changes.

    After remediation, repeat the relevant tests and affected journeys when verification is included.

    OUTPUTVerification status for the retested findings

  5. 05

    Documentation

    Keep an actionable record.

    The audit report records the scope, evidence, impact, WCAG references, and guidance. Add remediation and verification updates as work progresses.

    OUTPUTAudit findings and subsequent technical records

Your audit report is delivered when the evaluation is complete; it does not wait for remediation. Need us to fix the issues too? Explore Code-Level Remediation.

ACTIONABLE FINDINGS

Your developer shouldn’t have to guess
what the report means.

Every meaningful finding should answer the questions needed to understand and act on it.

EqualAccess.ILLUSTRATIVE REPORT
CHECKOUT / EMAIL FIELDOpen

Error not communicated.

Finding
A visible validation error is not associated with the email field or announced when it appears.
Location
/checkout · Email field
Impact
A screen-reader user may not know why submission failed.
WCAG
Applicable criterion recorded after evaluation.
Recommendation
Associate the error with the field and communicate the updated state.
A validated finding is not a verified fix. This issue is still open.
What is wrong?
A plain-language explanation of the barrier.
Where is it?
The page, template, component, or interaction.
Who can it affect?
The affected user experience.
How was it found?
The relevant automated, manual, keyboard, or assistive-technology method.
Which requirement?
The applicable WCAG criterion or agreed technical requirement.
How should it change?
Practical remediation guidance.
Has it been fixed?
Remediation and retesting status when verification is included.

Found accessibility barriers? We can fix them.

NOT EVERY FINDING HAS THE SAME IMPACT

Start with barriers that
affect important experiences.

Prioritization gives your team an order of work. We consider impact, reach, implementation effort, and the dependencies needed to address each finding.

User impact
Does the barrier block access to content or prevent an action?
Journey importance
Does it affect checkout, account access, booking, or another important task?
Recurrence
Is it isolated, or repeated through a shared template or component?
Technical severity
How does the implementation fail the applicable requirement?
Remediation efficiency
Could one component change address repeated barriers?
Third-party control
Can your team change the code, or is a vendor involved?
GREATER USER IMPACT
ISOLATED · HIGH IMPACT

Address promptly

A task-blocking issue on one important page.

REPEATED · HIGH IMPACT

Prioritize the shared fix

A barrier affecting an important journey across the site.

ISOLATED · LOWER IMPACT

Schedule the correction

Limited reach, with a clear next action.

REPEATED · LOWER IMPACT

Plan a component fix

Recurring friction worth correcting at the source.

IsolatedREACH & RECURRENCERepeated
Illustrative planning aid, not a risk score. Prioritization determines sequence; it does not remove applicable accessibility requirements.

PLATFORM-AGNOSTIC TESTING

We can audit the experience across a wide range of platforms.

Accessibility testing is not limited to Shopify, WordPress, or any one CMS.

EqualAccess. evaluates the experience people actually receive—structure, navigation, forms, keyboard behavior, assistive-technology support, and important user journeys—regardless of how the website is built.

ACCESSIBILITY TEST SCOPEIllustrative
Example website URL
https://example.comExample
Platform
  • Unknown
  • Custom
Platform detection is optional.

Testing layers

  • Automated checks
  • Manual review
  • Keyboard navigation
  • Screen reader testing
  • User-journey testing

Testing scope can be defined regardless of platform.

Illustrative workflow. Scope is agreed per project.

COMMON PLATFORMS WE SUPPORT

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

Don’t see your platform? That usually isn’t a barrier to accessibility testing.

Get a Free ReviewChoose a time on our calendar.

WHAT YOU RECEIVE

Clear findings
your team can act on.

ACCESSIBILITY EVALUATION
ILLUSTRATIVE REPORT OUTLINE

The context behind
every recommendation.

  1. 01 Scope & environments
  2. 02 Validated findings
  3. 03 Impact & priorities
  4. 04 Recommended changes
  5. 05 Limitations & next steps
Documentation of the technical evaluation, not a certificate.
Defined testing scope
The pages, templates, components, journeys, environments, and requirements covered.
Accessibility audit report
Validated findings with locations, impact, WCAG references, and guidance.
Manual testing findings
Barriers discovered through human interaction, visual review, and contextual testing.
Assistive-technology findings
Relevant screen-reader and interaction issues within the agreed scope.
Prioritized recommendations
A practical starting point for addressing the barriers.
Remediation guidance
Technical direction for your developers or agency.
Review walkthrough
A discussion of important findings and next steps, where included.
Path to verification
Retesting of affected functionality can follow remediation.

Supporting a procurement request? Explore VPAT & ACR. Building internal capability? See Consulting & Training.

THE REPORT ISN’T THE FINISH LINE

Findings should lead
to a better website.

Some organizations have developers ready to work from the audit. Others need us to handle the technical changes. We can support either approach.

UNDERSTAND THE BARRIER

Clear findings with evidence and a practical recommendation.

MAKE THE CHANGE

Address the underlying component, content, or interaction.

CONFIRM THE OUTCOME

Retest the experience and document what changed or remains.

Your team fixes

We provide findings and technical guidance, then retest the work within the agreed scope.

EqualAccess. fixes

Where code access and scope allow, we can implement the remediation and verify the result.

Explore Code-Level Remediation

ACCESSIBILITY UNDER SCRUTINY

Understand the website
behind the allegations.

Technical testing can investigate whether reported barriers are present and whether similar issues occur elsewhere. We review the allegations, test the affected functionality, and evaluate the broader agreed scope.

Get Priority Support

Your attorney handles
the legal matter.

EqualAccess. handles
the website.

WHEN TO GET AN AUDIT

You don’t have to wait
until accessibility becomes urgent.

You’re unsure where the site stands

Establish a baseline and understand the barriers currently present.

You’re about to redesign

Find recurring problems before they move into the new website.

You’ve finished a redesign

Test important pages and journeys before assuming the new experience is accessible.

A customer or procurement team is asking

Gather technical evidence for accessibility documentation or an ACR.

You received a demand letter or lawsuit

Evaluate the reported technical issues and the broader website.

Your team has made accessibility fixes

Verify whether changes addressed the original barriers.

Your website has changed significantly

Retest affected templates, functionality, content, and journeys.

Planning proactive improvements? See ADA Website Compliance.

ACCURATE EXPECTATIONS

An audit tells you what needs attention.
It doesn’t fix the website by itself.

An audit is an evaluation. If it identifies barriers, remediation is still needed. A scanner score or audit report is not a permanent guarantee for a website that keeps changing.

Connect evaluation with remediation, verification, and ongoing accessibility work.

Once the agreed fixes are complete, Ongoing Monitoring & Support can help identify new barriers as content, code, and integrations change.

ACCESSIBILITY AUDIT FAQ

Common questions about
website accessibility testing.

A website accessibility audit is a structured evaluation designed to identify barriers that can prevent people with disabilities from using a website or web application. The agreed scope is tested against a technical accessibility standard such as WCAG using appropriate automated and human evaluation methods.

No. Automated tools can help identify certain accessibility issues, but they cannot evaluate every requirement or determine accessibility on their own. W3C states that knowledgeable human evaluation is required.

Depending on scope, manual testing can include keyboard navigation, focus behavior, content and semantic structure, visual inspection, forms, error handling, interactive components, zoom and reflow, screen-reader behavior, and complete user journeys.

Screen-reader testing can be included when appropriate to evaluate how structure, controls, forms, states, and dynamic information are communicated through assistive technology. It is used alongside other testing methods rather than as the only accessibility test.

Not necessarily. Many websites contain large numbers of pages built from the same templates and components. We typically define a representative scope covering important page types, shared components, and critical user journeys, while automated analysis can help identify patterns across a wider set of pages.

Accessibility testing isn't limited to a specific platform. EqualAccess. can evaluate websites and web applications across a wide range of technologies, including Shopify, WordPress, WooCommerce, BigCommerce, Webflow, Squarespace, Wix, and custom websites and web applications.

We define the testing scope around the website's pages, templates, components, functionality, and important user journeys—not simply the platform name.

The target depends on the engagement. WCAG 2.2 Level AA is a strong current technical target when an organization is free to choose, while certain laws, procurement requirements, contracts, or existing programs may reference WCAG 2.1 or WCAG 2.0. We define the target standard during scoping rather than assuming the same version applies to every project.

Yes. If you already have an audit, EqualAccess. can review it to determine whether the findings are current and actionable. Additional testing may be needed if the report is outdated, incomplete, or the website has changed.

Yes. Findings can include practical remediation guidance so your internal developer or agency understands what needs to change. EqualAccess. can also provide code-level remediation directly when included in scope.

Yes, verification can be scoped after remediation to determine whether the affected functionality now addresses the original finding.

No. EqualAccess. provides technical accessibility services, not legal advice. An audit identifies technical accessibility barriers within the agreed scope; it does not guarantee a legal outcome or prevent future claims.

Official references: W3C accessibility evaluation and WCAG 2.2.

START WITH WHAT’S ACTUALLY THERE

Know what’s inaccessible.
Know what to fix next.

Tell us about your website, platform, and what prompted the review. We’ll help determine the testing scope and a clear path from findings to remediation and verification.

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

Opens in a new tab.