Capabilities · Accessibility

Find the barriers. Give your team a way to fix them.

For teams responsible for public information and services: an accessibility assessment that names the affected journey, shows the evidence, and explains how a fix will be verified.

Request a quote Book a call

Sample finding · A11Y-004

Registration journey

A keyboard user cannot submit the form.

Impact: The submit control responds to a mouse click but is skipped in the tab sequence. A visitor navigating by keyboard cannot finish registration.
Reproduce: Open the form, complete its fields using Tab, and attempt to reach and activate Submit without a pointer. Record the tested browser and page version.
Criterion: WCAG 2.1.1 Keyboard, Level A. Confirm the implementation and affected instances before assigning the final finding.
Fix: Use a native button with appropriate form behavior. Preserve visible focus and ensure errors and confirmation can be understood.
Verify: Retest keyboard submission, error recovery, and confirmation. Record the browser and screen-reader combination, evidence, and remaining issues.

Illustrative finding and proposed retest. No client information or completed test result is represented here.

Automated + manual: Complementary checks
User journeys: Test the complete task
Retesting: Document the correction

An expert assessment is a separately scoped, paid engagement. The free public audit is an automated first pass and does not include a manual review.

Free automated check

Check your own site in about a minute.

The free audit runs the axe-core engine against WCAG 2.2 AA on your homepage and returns each failure by severity, with the elements it affects. It needs your web address and nothing else.

An automated pass finds a portion of real barriers. It cannot tell you whether a visitor can finish a task, which is what the assessment below tests by hand.

Run the free audit

Engagement details

Agree what is being tested.

The assessment

Pages and complete journeys

Identify representative templates and important tasks such as registering, searching, or requesting a service. State how authenticated areas, documents, media, and third-party tools are covered.

Automated and manual checks

Use automated checks alongside keyboard, focus, screen-reader, form, and content review. Record the testing environments. An automated score, including 100, does not establish conformance.

A report your team can use

Receive affected locations, user impact, relevant criteria, reproduction steps, priorities, and recommended fixes. Coverage and limitations are stated with the findings.

Verification after remediation

Have your team or vendor make the changes, or request a fixed remediation quote. Agree retest coverage. Ongoing automated monitoring can catch some regressions; manual verification remains necessary.

From assessment to verified change.

Scope
Name the requirement
Bring the applicable contract or organizational standard, priority journeys, and known complaints. Agree the target, sample, deliverables, and fee.
Assess
Explain the evidence
Review findings with the people responsible for the site. Separate shared template defects, content work, and third-party dependencies so responsibility is clear.
Retest
Close findings with evidence
Verify agreed changes in the relevant journeys and document remaining limitations. Keep the report useful as the site and its content change.

WCAG, Title II, and Section 508 have distinct requirements.

State and local public entities

The DOJ’s Title II web rule specifies WCAG 2.1 AA. Compliance dates are April 26, 2027 for entities with populations of 50,000 or more, and April 26, 2028 for smaller entities and special district governments.

Read DOJ’s current guidance

Federal Section 508

The Revised 508 Standards incorporate WCAG 2.0 Level A and AA and contain additional ICT requirements. A contract may specify further requirements, including a later WCAG version. We agree the applicable scope before testing.

Read the U.S. Access Board standards

Looking for LFW's own accessibility statement, the one covering this website? Read LFW's accessibility statement

Start with the journey your visitors need to complete.

Bring the requirement and the site. We will discuss assessment coverage, responsibilities, and what your team needs from the findings.