A Practical Accessibility Statement and Issue-Response Process for Small Businesses
What should a small-business accessibility statement and issue-response process contain?
Publish a concise accessibility statement that names the WCAG benchmark your business is working towards, describes known limitations without overstating conformance and provides a working support contact. Internally, route each report to a named owner, clarify what the person was trying to do, offer a practical alternative where possible, record the barrier and remediation decision, retest completed work and confirm closure when contact details permit. The statement is a communication and support mechanism, not proof that the website conforms.
State the benchmark without overstating conformance
Accessible.org recommends WCAG 2.1 AA conformance, or 2.2, together with an accessibility statement containing contact information for support. State the WCAG Level AA version the business is working towards, but avoid saying the website fully conforms unless that specific claim has been supported by a suitably qualified assessment and approved for publication.
Sources: ADA Website Compliance Guide: Accessibility and the Law | Accessible.org.
Use a website governance guide to set an approval boundary for public accessibility wording so a well-meant statement does not become an unsupported promise. The public statement should identify the benchmark, explain the current improvement approach, acknowledge known limitations honestly and display its latest review date.
Treat the statement as a support and communication document rather than certification, a legal opinion or a substitute for testing the website.
- Name the benchmark being pursued.
- Use accurate, approved wording about current status.
- Acknowledge known limitations without turning the statement into a guarantee.
Give users a working route to request support
Provide a working email address, phone route, contact form or other practical support method, and test that messages reach the person responsible for responding. Ask for the customer task, affected page or component, barrier description and preferred reply method when a reply is wanted, without requiring unnecessary personal information.
A lead-form design guide can help keep an accessibility support form proportionate so it gathers the information needed to route the issue without creating another barrier. Place the support route in the accessibility statement itself rather than assuming that a visitor will find it elsewhere on the website.
Give the route an internal owner and check it after changes to inboxes, phone systems, forms or staff responsibilities.
- Offer at least one working contact route.
- Explain what details will help the team investigate.
- Avoid requesting information that is not needed.
Route each report from acknowledgement to remediation
Route every accessibility report to a named owner who can acknowledge it, clarify the blocked task, arrange a practical alternative where possible and record the barrier for remediation. Keep an internal issue record containing the report date, affected task, page or component, barrier description, owner, response action, remediation decision and retest result.
Clear website operating rules can assign ownership and escalation paths before an accessibility report becomes urgent. Escalate a report when the team cannot reproduce or assess the barrier competently, the affected journey uses a complex or consequential system, or the report raises a specific legal complaint or dispute.
After remediation, repeat the affected task, record the result and confirm closure with the reporting person when their contact details permit. Keep an unresolved report visible with an owner and next action rather than treating acknowledgement as closure.
- Give every report a named owner.
- Offer a practical alternative where possible.
- Record remediation and retesting in the internal issue log.
Use reports to improve the next accessibility review
The Hanover Insurance Group recommends evaluating a website’s current accessibility state and determining what can be done to increase accessibility and bring it into compliance. Use accessibility reports as practical input to the next current-state review by looking for repeated barriers, affected templates, supplied components and unresolved customer tasks.
A recurring website-task guide can turn reported barriers and review triggers into owned maintenance work rather than one-off promises. Keep records proportionate by retaining the information needed to support the person and improve the website while excluding unnecessary personal information from the remediation backlog.
Review the statement whenever its benchmark, known limitations, support route or response ownership materially changes, and use recurring reports to decide whether a broader specialist assessment is needed.
- Look for repeated barriers and affected components.
- Keep unresolved reports visible.
- Turn findings into owned maintenance work.
Accessibility statement and issue-response template
Use this template to publish an honest support route and give staff a consistent path from a reported barrier to assistance, remediation and closure. Adapt the wording to the website’s actual benchmark, present condition and available support routes.
| Statement or workflow element | Suggested wording or action | Internal record |
|---|---|---|
| Accessibility benchmark and status | We are working towards WCAG Level AA for this website. We review accessibility as the website changes and do not treat this statement as certification of complete conformance. | Named WCAG version, wording approver, statement owner and review date |
| Known limitations | Describe each known barrier or limitation in plain language and explain how a person can request help or an alternative. | Known limitation, affected task or component, owner and review status |
| Support contact | If you have difficulty using this website, contact us through [working email, phone route or support form] and tell us what you were trying to do. | Contact route owner, route test date and result |
| Barrier report and response | Record the task, affected page or component, barrier and preferred reply method; acknowledge the report and offer a practical alternative where possible. | Report date, issue owner, response action and only the contact details needed for follow-up |
| Remediation and next review | Decide remediation, retest the affected task, confirm closure when possible and review repeated or unresolved barriers. | Remediation decision, retest result, closure note, recurring owner and next review trigger |
Publishing the statement does not establish complete conformance. Review it whenever the benchmark, current limitations, support contact or response ownership materially changes.
When this is not the right approach: Do not publish generic wording that makes claims the business cannot support or maintain. Seek appropriate accessibility or legal assistance when a reported barrier involves a complex system, significant customer harm, a formal conformance claim or a specific legal dispute.
Related guidance
What follow-up questions matter most?
- What should an accessibility statement say about the standard?
- State the WCAG benchmark the business is working towards, describe the current approach without making an unsupported guarantee, identify known limitations honestly and provide a working support contact.
- What contact details should an accessibility statement include?
- Provide a working email address, phone route, contact form or other practical support method. Ask only for information needed to understand the customer task, page or component, barrier and preferred contact method when a reply is wanted.
- What should happen when someone reports a barrier?
- Assign the report to a named owner, clarify the blocked task, offer a practical alternative where possible, record the barrier, decide remediation, retest any completed fix and confirm closure when contact details permit.
- How should accessibility reports improve maintenance?
- Review reports for repeated barriers, affected components and unresolved tasks. Use those patterns to update the next website accessibility review and create owned maintenance work.
What steps does this workflow follow?
How to create an accessibility statement and response route
- Name the operating benchmark: State the WCAG benchmark the business is working towards without claiming complete conformance unless that specific claim has been properly supported and approved.
- Describe status honestly: Explain the business’s current approach and known limitations in plain language, and give the statement an owner and review date.
- Publish and test a support contact: Provide a practical route for requesting help or reporting a barrier, then confirm that the route reaches the person responsible for responding.
- Ask only for useful details: Request the customer task, affected page or component, barrier description and preferred reply method where needed; avoid asking for unnecessary personal information.
- Route the report to an owner: Assign a named owner to acknowledge the report, clarify the issue, offer a practical alternative where possible and record the remediation decision.
- Retest, close and learn: Retest completed remediation, confirm closure when contact details permit and use repeated or unresolved reports to inform the next accessibility review.