On June 9, 2026, we shipped accessibility statements on dennisyu.com and blitzmetrics.com. One agent session: two pages, two footer links, a cache purge, live verification. As of today, this is a standard component of every personal brand website we build — and this post is the spec our website agents follow.
This component extends our standard for how we build a personal brand website, and verifying it is part of how we QA a personal brand website. Pair it with our website audit checklist when reviewing any site end to end. Build it in from day one, or catch it in QA — either way, no site ships without it.
Understand Why an Accessibility Statement Matters
Under ADA Title III, a business open to the public needs a website that people with disabilities can actually use. The Department of Justice has never issued a formal technical rule for private-business sites, but courts and settlements consistently point to one benchmark: the Web Content Accessibility Guidelines (WCAG).
Thousands of ADA website lawsuits are filed every year in US federal and state courts, and small businesses are frequent targets. The DOJ’s 2024 rule codified WCAG 2.1 AA for state and local government sites, and the European Accessibility Act has applied to companies selling to EU consumers since June 28, 2025. The direction is one-way.
An accessibility statement does not make your site accessible. It does three things: names your target standard, states your honest status, and gives a visitor with a barrier a direct way to reach you — before they reach a law firm. That documented good faith matters in a demand letter, and the contact channel resolves most issues for free.
There is a selfish reason too. The work behind the statement — semantic headings, alt text, descriptive links, real contrast — is the same structure Google and AI engines parse. Accessibility and entity SEO are the same discipline wearing different badges.
Adopt the Five Requirements
A site meets the BlitzMetrics accessibility-statement standard when all five are true:
- Dedicated page at /accessibility-statement/ — its own URL, not a paragraph buried in the privacy policy.
- WCAG 2.2 Level AA named as the target, with an honest status. “Partially conformant” is the truthful answer for most sites. Never claim full conformance you have not tested.
- A monitored contact email and a response pledge. We commit to five business days.
- A footer link on every page, placed next to the Privacy Policy.
- A date, reviewed and updated as the site changes.
Copy the Template
Replace the bracketed placeholders. This is the exact structure live on our own sites.
Accessibility Statement [OWNER / COMPANY] is committed to making this website accessible to everyone, including people with disabilities. CONFORMANCE STATUS We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. [DOMAIN] is partially conformant with WCAG 2.2 Level AA: some parts of the content do not yet fully conform, and we are actively working to close those gaps. MEASURES WE TAKE - Use semantic HTML with a logical heading structure - Provide alternative text for meaningful images - Maintain sufficient color contrast between text and backgrounds - Support keyboard navigation - Write descriptive link text instead of phrases like "click here" - Review new content for accessibility before publishing COMPATIBILITY This website is designed to work with current versions of major browsers and common assistive technologies, including screen readers such as VoiceOver, NVDA, and JAWS. KNOWN LIMITATIONS - Some older posts and images may lack complete alternative text or captions. - Embedded third-party media may not fully meet accessibility standards. [LIST ANY THIRD-PARTY PLATFORMS, such as course portals, and offer alternative formats on request] FEEDBACK If you encounter an accessibility barrier or need content in an alternative format, email [MONITORED EMAIL]. We aim to respond within five business days. ASSESSMENT AND UPDATES We assess this site through self-evaluation, combining automated tools with manual checks such as keyboard-only navigation and screen reader testing. This statement was prepared on [DATE] and is reviewed as the site evolves.
Automate It: Instructions for Website Agents
If you are a human, hand this section to whoever — or whatever — builds your sites. If you are an agent executing a personal brand website build, treat the five requirements above as acceptance criteria and follow these steps:
- Create the page.
POST /wp-json/wp/v2/pageswith title “Accessibility Statement”, slugaccessibility-statement, statuspublish, and the populated template as content. Check for an existing page at that slug first; update rather than duplicate. - Add the footer link.
POST /wp-json/wp/v2/menu-itemsinto the footer menu, ordered next to the Privacy Policy item. If the theme uses a builder footer instead of a menu, edit the footer template. - Purge and verify. Clear any page cache (WP Rocket or similar), fetch the live URL, and confirm the page renders and the footer link appears site-wide.
- Use facts only. Fill placeholders with the owner’s real monitored email and today’s date. Do not invent audits, certifications, or conformance claims.
See the Standard Live
Two reference implementations, published the day this standard was set:
Learn, Do, Teach
We learned the requirement, did it on our own sites the same day, and documented it here so any builder — human or AI — can repeat it without us. That is the process standard we hold every component to: it is not done until someone else can ship it from the written spec.
