Write your accessibility statement in five minutes.
An accessibility statement tells visitors which standard you work to, where you stand and how to reach you. Answer a few questions and get one as plain HTML you own. No account needed; nothing you type leaves your browser.
Last reviewed October 26, 2026. General information, not legal advice.
Accessibility statement for this website
We want everyone to be able to use this website, whatever technology or ability they bring to it. This statement says which standard we work to, where we stand, and how to tell us when something is in the way.
Conformance status
The Web Content Accessibility Guidelines (WCAG) describe how to make web content accessible to people with disabilities. This website is partially conformant with WCAG 2.2 Level AA. Partially conformant means that most of the content meets the standard and the exceptions are listed below.
What we do
To keep this website accessible, the owner of this site:
- Runs automated accessibility audits on a schedule and works through the results.
- Tests key pages by hand with a keyboard and a screen reader.
Feedback and contact
If you cannot use part of this website, or want to tell us about an accessibility problem, please contact us.
We aim to respond within five business days.
About this statement
This statement was prepared on November 5, 2026 and last reviewed on November 5, 2026.
It was written with the free accessibility statement generator from Accessora (https://accessora.io/tools/accessibility-statement-generator).
Publish it where people look.
Give the statement its own page, for example /accessibility-statement, and link it from the footer of every page. That is where visitors, auditors and lawyers look first. Paste the HTML into your CMS, or drop the downloaded file onto your server as it is.
If your site runs Accessora, the widget already has an Accessibility Statement panel that explains the widget's own features in any of its 44 languages. Your statement about the site still belongs on its own page, linked from the footer.
Keep the date current. Review the statement after every audit and whenever you ship a fix, and update the known limitations so they match what the audit results show. Our own accessibility statement was written with this tool, so you can see one in use.
What the output looks like.
A statement for a fictional shop, generated with the form above. Partially conformant, two known issues, a contact and a date.
Show the example statement
Accessibility statement for quillandkiln.com
Quill & Kiln wants everyone to be able to use quillandkiln.com, whatever technology or ability they bring to it. This statement says which standard we work to, where we stand, and how to tell us when something is in the way.
Conformance status
The Web Content Accessibility Guidelines (WCAG) describe how to make web content accessible to people with disabilities. quillandkiln.com is partially conformant with WCAG 2.2 Level AA. Partially conformant means that most of the content meets the standard and the exceptions are listed below.
What we do
To keep quillandkiln.com accessible, Quill & Kiln:
- Runs automated accessibility audits on a schedule and works through the results.
- Tests key pages by hand with a keyboard and a screen reader.
- Offers an accessibility widget with adjustments such as larger text, higher contrast and text to speech.
- Has named a person responsible for accessibility.
Known limitations
Some parts of quillandkiln.com do not meet the standard yet. These are the ones we know about:
- Product videos: Videos published before 2025 have no captions. Workaround: Email us and we will send a transcript. Planned fix: Captions for the full back catalog by March 2027.
- Gift card PDFs: Downloadable gift cards are images inside a PDF and cannot be read by a screen reader. Workaround: Gift card details are also sent as plain text in the order email. Planned fix: A tagged, text-based PDF is in progress.
Compatibility
quillandkiln.com is designed to work with current versions of Chrome, Firefox, Safari and Edge, and with VoiceOver and NVDA.
Feedback and contact
If you cannot use part of quillandkiln.com, or want to tell us about an accessibility problem, please contact us.
We aim to respond within five business days.
- Email: [email protected]
About this statement
This statement was prepared on October 26, 2026 and last reviewed on October 26, 2026.
It was written with the free accessibility statement generator from Accessora (https://accessora.io/tools/accessibility-statement-generator).
What a good statement includes.
The form follows the structure the W3C recommends for accessibility statements. These are the parts, and why each one is there. Read more in our WCAG guide and the EAA guide.
- 1
Scope
Which site, app or pages the statement covers. One domain is the simplest answer.
- 2
Standard and level
WCAG, the version and the level you work to. Level AA is what laws point to.
- 3
Conformance status
Fully, partially or not conformant, or not yet assessed. Partially conformant with a clear list is normal and honest.
- 4
What you do
Audits, manual testing, training, a named owner. The measures that keep the status true.
- 5
Known limitations
Each problem, who it affects, a workaround if there is one, and when you plan to fix it.
- 6
Feedback contact
An email at least, a response time, and a person or team who actually reads it.
- 7
Dates
When it was prepared and last reviewed. A statement with an old date reads as abandoned.
Not sure what your known limitations are? An audit finds many of them and tags each one with its WCAG criterion.
See how audits work
Is an accessibility statement legally required?
It depends where you are. The European Accessibility Act asks service providers to publish information on how their service meets the requirements, and EU public sector bodies must publish a statement in a set format. The ADA does not require one. Either way, visitors and auditors look for one, and it costs little to publish.
How often should I update it?
After every audit and every fix that changes the known limitations, and at least once a year even if nothing changed, so the review date stays current.
Should I list known issues?
Yes. A statement that claims full conformance with no exceptions is rarely believed. Listing what you know is wrong, with a workaround and a planned fix, shows that you have looked and that you are dealing with it.
Can I use this for an app?
Yes. Put the app name in the website field and describe the platforms in the compatibility field. The structure is the same; only the scope changes.
Find your known issues with an audit.
Add your site, run a scan, and use what it finds to fill in your known limitations. 7-day free trial on every plan.