A WordPress accessibility statement page explains what a website is doing to support visitors with disabilities. It should be honest, specific, easy to find, and connected to a process for handling barriers.
The statement is not proof that every page is perfect. It is a public commitment that identifies the standard being followed, describes known limitations, and gives visitors a practical way to request help.
Name the website and its scope
State which website, subdomains, mobile experiences, and customer portals the statement covers. If third-party tools such as booking systems, payment forms, or embedded maps follow different accessibility practices, explain that distinction.
Use the business name clearly. Avoid broad claims such as “fully accessible” unless current testing supports them across the complete experience.
Reference an accessibility standard
Many organizations use the Web Content Accessibility Guidelines as a testing framework. Name the version and conformance level the team is working toward. Keep legal claims separate from the practical description of design and development work.
- Use meaningful headings and landmarks.
- Provide keyboard access to interactive controls.
- Add useful text alternatives for informative images.
- Maintain visible focus and sufficient contrast.
- Label forms and explain validation errors clearly.
Describe how the site was tested
Tell visitors whether the review included automated scans, keyboard testing, screen-reader checks, zoom, mobile layouts, or testing by people with disabilities. Include the date of the latest substantial review.
Automated tools are useful, but they cannot confirm whether link text makes sense, reading order is logical, or instructions are understandable. Combine automated checks with manual journeys through key pages.
List known limitations honestly
A useful statement names significant unresolved barriers and gives an expected improvement plan when possible. Examples may include an older PDF, a third-party widget, missing captions in archived video, or a complex chart without a complete text alternative.
Do not hide this section behind vague language. Visitors need to know whether a limitation affects the task they are trying to complete.
Provide an accessible contact route
Offer a simple way to report a problem or request information in another format. An email address and an accessible form can provide choice. Explain what details help the team investigate, such as the page URL, the task attempted, the device, and the assistive technology used.
Set a realistic response time and route messages to someone who can coordinate a fix. The contact method itself must be keyboard accessible and should not depend on a difficult CAPTCHA.
Connect the statement to real website work
The statement should reflect design, content, and development practices. Review navigation, forms, headings, links, images, documents, motion, and color use. The WordPress accessibility checklist provides a broader starting point for those checks.
Assign responsibility for each reported issue. Record severity, affected pages, owner, target date, and verification method. This turns feedback into a trackable maintenance process.
Keep the page easy to find
Link the accessibility statement from the footer, help area, or another consistent location. Use a clear page title and a readable URL. Make sure the page is indexable unless there is a specific reason to keep it private.
Update the statement after a redesign, platform migration, major third-party integration, or formal audit. Review it at least once a year even when the website has not changed significantly.
Avoid empty promises
Templates can help with structure, but the final statement must match the real website. Remove claims that the team cannot verify. Include dates, limitations, contact details, and concrete improvement practices.
A clear WordPress accessibility statement page gives visitors useful information and gives the organization a visible standard for ongoing work. The page is strongest when it reflects continuous testing, accountable ownership, and responsive support.