Templates
templates
Copy these templates into your own tools and adjust them to your team. Each one links to the guide that explains why it matters.
Accessibility bug report
template
A developer who doesn’t know WCAG by heart can’t do much with a number alone. This template makes sure every report says what’s wrong, who it affects and how to fix it.
Use one of these levels for how badly it affects people:
- Blocker: someone can’t finish the task.
- Serious: someone can finish the task, but only with a lot of effort or help.
- Minor: it’s annoying or confusing, but it doesn’t stop anyone.
Title: [Component]: [what’s wrong]
Where: [page or URL, and the component]
Steps to reproduce:
1.
2.
3.
What I expected:
What happened:
Tested with: [browser and assistive technology, like NVDA with Firefox]
WCAG: [number and name, like 1.4.3 Contrast (Minimum)]
Who is affected, and how badly: [blocker / serious / minor]
Suggestion for a fix:Example
Title: Search field: placeholder text has too little contrast
Where: every page, the search field in the header
Steps to reproduce:
1. Open any page.
2. Look at the placeholder text in the search field.
What I expected: a contrast of at least 4.5:1 against the background.
What happened: the grey text has a contrast of 2.8:1 against white.
Tested with: Chrome, Colour Contrast Analyser
WCAG: 1.4.3 Contrast (Minimum)
Who is affected, and how badly: serious, for people with low vision.
Suggestion for a fix: make the text darker, like the body text.Acceptance criteria
template
Acceptance criteria make accessibility part of a user story, and testable. They cover what is specific to this one feature. What applies to every feature, like contrast and keyboard access, belongs in the Definition of Done.
Write them together with your designers and developers. The example below is for a sign-up form: replace it with criteria for your own story.
Accessibility acceptance criteria for: [user story]
Example for a sign-up form:
- Every field has a visible label.
- Error messages say what went wrong and how to fix it.
- You can complete the form with only a keyboard.
- The focus is always visible.Definition of Done
template
The Definition of Done covers what applies to every feature, so accessibility is checked every time, not only when someone remembers. The article about the Definition of Done ends with an example you can copy and adjust to your team.
Pull request checklist
template
Add these questions to your pull request template, so they come up in every code review. On GitHub, save the template as .github/pull_request_template.md in your repository.
Agree with your team that a pull request with known accessibility issues is not done.
## Accessibility
- [ ] Works with only a keyboard, in a logical order
- [ ] The focus is always visible
- [ ] Every control has a name
- [ ] States like expanded or selected change in the code
- [ ] The HTML is semantic, and the ARIA matches it
- [ ] Works at 400% zoom
- [ ] Automated accessibility checks passDesign annotations
template
A lot of accessibility is invisible in a design. If you don’t write it down, developers have to guess. Add these notes to every screen or component you hand over.
Accessibility notes for: [screen or component]
Headings: [the level of each heading: h1, h2, h3]
Landmarks: [header, navigation, main content, footer]
Focus order: [only if it isn’t top to bottom, left to right]
Images: [the alt text of each image, or “decorative”]
Icon buttons: [the name of each button that only has an icon]
Dialogs: [where the focus goes when it opens, and when it closes]Accessibility statement
template
An accessibility statement tells users how accessible your website is, what doesn’t work yet, and how they can contact you when they get stuck. Keep it honest and up to date: a statement that lists known issues builds more trust than one that claims everything is perfect. Review it at least once a year, and after big changes.
The template follows the structure of the European model statement. For the compliance status, choose:
- Fully compliant if your website meets every requirement of WCAG 2.2 level AA, without exceptions.
- Partially compliant if it meets most requirements, with some exceptions.
- Not compliant if it doesn’t meet most requirements.
Public sector websites in the European Union
Public sector bodies in the EU have to publish an accessibility statement for every website and app, based on the model accessibility statement of the European Commission. Your country may have its own version. In the Netherlands, government organisations make their statement with toegankelijkheidsverklaring.nl (in Dutch).
Companies and the European Accessibility Act
The European Accessibility Act applies since 28 June 2025. It doesn’t ask for an “accessibility statement” by that name. Instead, service providers have to explain how their service meets the accessibility requirements, in their general terms and conditions or an equivalent document. That information has to be available in writing and orally, in a way that is accessible to people with disabilities.
A statement based on this template is a good start, but it doesn’t replace that information. Check with your legal team what your country’s law asks of you. Microenterprises that provide services, with fewer than 10 employees and an annual turnover or balance sheet total of no more than €2 million, are exempt.
# Accessibility statement for [name of the website or app]
[Organisation] wants [website] to be usable for everyone, including
people with disabilities. This statement explains how accessible
[website] is, what doesn’t work yet and how you can contact us.
## Standard
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at
level AA.
## Compliance status
[Choose one, and delete the others.]
[Website] is fully compliant with WCAG 2.2 level AA.
[Website] is partially compliant with WCAG 2.2 level AA. The parts that
aren’t are listed below.
[Website] is not compliant with WCAG 2.2 level AA. The parts that aren’t
are listed below.
## What doesn’t work yet
[For each issue: what doesn’t work and for whom, in plain language. The
WCAG criterion. An alternative, if there is one. When you plan to fix
it. For example:]
- The date picker in the booking form doesn’t work with a keyboard (WCAG
2.1.1 Keyboard). You can also book by phone. We plan to fix this in
[month and year].
## How we tested
This statement was prepared on [date], based on [a self-assessment / an
audit by [name]], following [method, like WCAG-EM].
We tested with [browsers and assistive technology, like NVDA with
Firefox and VoiceOver with Safari].
This statement was last reviewed on [date].
## Feedback and contact
If something on [website] doesn’t work for you, please tell us: [email
address, phone number or a link to the contact page]. We’ll reply within
[number] working days.
## Enforcement procedure
[Public sector bodies in the EU: describe and link to the enforcement
procedure, and give the contact details of the enforcement body. Delete
this section if it doesn’t apply to you.]Questions for suppliers
template
Many accessibility issues come from things you buy or embed: a cookie banner, a chat tool, a video player, a payment page. Your users don’t know the difference. Ask suppliers these questions before you sign, and test the product yourself.
Put the answers and your requirements in the contract, and have your legal team check the wording.
Questions about the accessibility of [product]
1. Which accessibility standard does your product meet, and which
version? For example WCAG 2.2 level AA, or EN 301 549.
2. Do you have an Accessibility Conformance Report (ACR)? When was it
made, who tested the product, and how?
3. Which accessibility issues do you know about, and when will you fix
them?
4. Can we test the product ourselves before we decide?
5. How do we report accessibility issues, and how quickly do you fix
them?
6. How do you make sure new versions stay accessible?
7. Can the parts we customise, like colours and texts, be made
accessible?