Website Accessibility Statement Example for US Sites

A visitor should not have to guess whether a website can be used with a keyboard, screen reader, zoom settings, or other assistive technology. A clear website accessibility statement example gives people a direct answer, explains where to get help, and shows that the site owner is paying attention to access rather than treating it as an afterthought.

For an early-stage business site, the statement does not need to be long or filled with legal language. It does need to be honest. Publishing a statement that claims full compliance when the site has not been reviewed can create more confusion than confidence. The useful approach is to describe current efforts, identify a contact method, and commit to addressing barriers when they are reported.

What an accessibility statement should do

An accessibility statement is a public page that explains a website’s approach to digital access. It is not the same thing as making the website accessible. A well-written page cannot fix missing image descriptions, inaccessible forms, poor color contrast, or menus that cannot be used without a mouse. It can, however, tell visitors what standards guide the work and what they can do if something does not work for them.

For a business that may eventually publish vehicle, motor, equipment, or service information, this matters in practical ways. Visitors may need to read specifications, compare options, submit an inquiry, join an email list, or contact the business. Each of those tasks should be available to people with different access needs.

A strong statement usually covers four areas: the site’s commitment to accessibility, the standard or goal it follows, known limitations where applicable, and a clear way to request assistance or report a problem. It should also say when the page was last reviewed.

Website accessibility statement example

The following website accessibility statement example is written for a US business website with general information, contact forms, and future product or service content. Replace the bracketed details before publishing it. Do not leave claims in place that the site cannot support.

Accessibility Statement

[Business Name] is committed to making its website accessible and usable for as many visitors as possible, including people with disabilities.

We work to improve the accessibility of [Website Address] as content, features, and technology are added or updated. Our goal is to support access for visitors using keyboards, screen readers, browser zoom, voice controls, and other assistive tools.

We aim to follow generally recognized web accessibility practices, including the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA where practical for our website and its services.

Accessibility is an ongoing effort. Some content or third-party features may not yet work equally well for every visitor. If you have difficulty using any part of this website, need information in another format, or would like to report an accessibility issue, please contact us at [email address] or [phone number]. Please include the page address, a brief description of the issue, and the assistive technology or browser you were using, if you are comfortable sharing that information.

We will review your request and make reasonable efforts to provide the information, service, or assistance you need.

This statement was last updated on [Month Day, Year].

How to make the example accurate

The wording above is intentionally measured. It says the business is working toward accessibility without making an unverified promise that every page, plugin, document, or outside service already meets a particular standard.

Before selecting a standard such as WCAG 2.1 Level AA, decide what the statement means for the site. If the site uses a standard WordPress theme, a newsletter provider, mapping software, embedded social feeds, payment software, or a booking tool, some visitor experiences may depend on third parties. The business still has a responsibility to consider those tools, but it should not make broad claims without testing them.

If an accessibility review has been completed, the statement can be more specific. For example, it may say that a review was conducted on a certain date and that identified issues are being addressed. Avoid publishing technical audit details unless they are accurate, current, and useful to visitors. Most people looking for help need a working contact route faster than they need a long compliance report.

The response commitment also deserves attention. Do not publish a phone number or email address that nobody monitors. Assign responsibility for incoming accessibility requests and create a simple internal process for responding. For a small organization, that can be as straightforward as checking the inbox daily, acknowledging a request promptly, and offering an alternate way to receive the needed information.

Known limitations belong in the statement when needed

There is a trade-off between brevity and transparency. A short statement is easier to read, but it may omit information that helps visitors understand a current barrier. If the business knows of a meaningful issue, mention it plainly and state what is being done about it.

For instance, a site might state that some older PDF documents are not fully accessible, while offering to provide the information in another format upon request. Or it might explain that an embedded third-party scheduling tool has accessibility limitations and provide a phone option for scheduling. Specificity is better than vague language such as “we are always improving” when there is a known obstacle.

Do not use a limitations section as an excuse to leave problems unresolved. Its purpose is to set expectations while work is underway. If the same issue remains on the page year after year, the statement is signaling that accessibility has not been treated as an operational priority.

Publish the page where visitors can find it

An accessibility statement should be easy to locate from every page, commonly in the website footer near the privacy policy and contact information. The link text should clearly say “Accessibility Statement” rather than relying on a vague label such as “More” or “Resources.”

The page itself must be accessible too. Use a clear page title, headings in logical order, readable text, sufficient color contrast, and a contact method that can be used without completing a difficult form. If the page includes a phone number, provide an email option as well. If it includes an email address, consider whether a phone option is appropriate for visitors who prefer it.

A statement is most useful when it appears alongside day-to-day accessibility work. Check that images have meaningful alternative text when they convey information. Make sure a person can reach menus, forms, buttons, and pop-ups with only a keyboard. Use labels for form fields rather than placeholder text alone. Confirm that error messages explain what needs to be corrected. These checks are not a substitute for a full accessibility evaluation, but they catch common barriers on small business sites.

Keep it current as the website grows

A holding site with a contact page and newsletter signup may have a limited accessibility footprint. That can change quickly once product galleries, downloadable documents, inventory pages, videos, account features, or online transactions are added. Review the statement whenever the site adds a major feature or changes the tools visitors use.

The date at the bottom matters because it tells visitors the page is maintained. Update it after a meaningful review, not merely because a calendar year changed. If the business receives a report about an access problem, use it as practical feedback: fix the issue when possible, document the response, and consider whether the statement should explain an ongoing limitation.

Accessibility statements work best when they sound like a real invitation for people to get help. Start with honest language, keep the contact route open, and let each reported barrier guide the next improvement.