Accessibility statement

1. What we are aiming at

This website targets WCAG 2.2 level AA, the current version of the Web Content Accessibility Guidelines published by the W3C.

Targeting a standard is not the same as meeting it, and we are not going to claim conformance we have not measured. What follows is what we have actually done, what we have actually tested, and what we know is still missing.

2. What is built in

• Text you can resize. Type and spacing are set in relative units, so the page reflows rather than clipping when you increase text size or zoom to 200 percent.
• Contrast checked against the standard. The colour palette is checked automatically as part of our build. Our accent colour is bright enough for text on the dark background but not on the light sections, and there is a test that fails the build if anyone tries to use it there.
• Keyboard access. Every link, button and control can be reached and operated with a keyboard, and the focus outline is visible rather than removed.
• Real headings and landmarks. Pages use a single first-level heading, ordered headings under it, and standard page regions, so a screen reader can skim the structure instead of reading everything.
• Motion that respects your settings. Nothing animates above the fold at all, and if your device is set to reduce motion, the rest stops too.
• It does not depend on JavaScript. These pages ship no interactive components. Nothing you need to read or click waits for a script to load.
• Images carry alternative text and fixed dimensions, so the page does not jump around while it loads.

3. How we test

Automated accessibility checks run against the site in our own pipeline, at phone and desktop widths, every time it is built. At the date on this page they report no violations.

Separately, each page is loaded once with motion reduced and once with JavaScript switched off, and the build fails if it does not arrive intact. That is a rendering check rather than an accessibility audit, and this page does not claim it as one.

Automated results are worth exactly what automated testing is worth, which is less than people assume. Such tools catch a minority of real barriers. The rest need a person.

4. Known gaps

These are the gaps we know about today. Naming them is more useful than a conformance badge.

• White text on the red buttons. Our filled buttons use white text on the brand red, the same pairing as the logo. That measures 3.8:1 against the 4.5:1 the standard asks of text at that size. It clears the 3:1 level for large text and controls, and we chose it deliberately for the brand. It is the one place on the site where we hold a lower contrast than the rule, and we are saying so here rather than hiding it.
• No screen reader testing by a human yet. Nobody has walked this site end to end with VoiceOver, TalkBack or NVDA. Until that happens, treat the screen reader experience as untested rather than confirmed.
• No independent audit. The testing described above is ours. It has not been reviewed by a third party and no formal conformance report exists.
• Automated coverage is partial. The automated pass covers the site’s main page templates, not every individual page, and it grows as pages are added.
• No testing with people who use assistive technology daily. We have not run the site past anyone who relies on it. That is the gap most likely to be hiding a problem we have not thought of.
• The content editor is out of scope. The editing tool at the /keystatic address is third-party software used by us to publish, not part of the public site, and we make no accessibility claim about it.
• Dark by default. The site is designed dark first with light sections. There is no user-facing light theme switch. If that causes you a problem, tell us, because it is a design decision rather than a technical limit.

5. The app is assessed separately

This statement covers the website at lacedentries.com. The Laced mobile app on iOS and Android is a different codebase with different platform tooling, and it has not been assessed against WCAG. We are not going to imply otherwise by staying silent about it. If you hit an accessibility barrier in the app, the same contact route below applies and we would like the detail.

6. Telling us about a problem

Email hello@lacedentries.com with “Accessibility” in the subject line.

Useful detail, if you have it: the page address, what you were trying to do, the browser or device you were using, and the assistive technology if any. None of it is required. A one-line description of what did not work is enough to start.

We have deliberately not published a response-time commitment, because we have not measured one and a number we invent here is worth nothing to you. What we will do is reply, tell you whether we can fix it, and say when. If a fix is going to take a while, we will offer you the information or the service another way in the meantime.

7. Standards and status of this statement

• Standard targeted: WCAG 2.2, level AA.
• Conformance claim: none made. This is a statement of target, testing and known gaps.
• Assessment method: our own automated testing, described in section 3.
• Statement prepared: 19 September 2026.
• Review: this page is reviewed when the site changes materially, and at least once a year.