Accessibility

1What we aim for

The Web Content Accessibility Guidelines (WCAG) 2.2, level AA, on every page.

2What we have done

• Colour is measured, not assumed. Every colour comes from one generated set of tokens, text and meaningful borders are checked against the AA contrast ratios on the exact values a browser renders, in light and dark themes, and a change that drops below the bar fails the build.
• Motion follows your device. If your system asks for reduced motion, animation stops.
• Cards, links and buttons are ordinary focusable controls with a visible focus ring, and a card has one accessible name rather than reading its picture, its title and its author as three separate things.
• Each page declares its language, so a screen reader reads it with the right voice.
• A skip-to-content link at the top of every page, so a keyboard user does not have to pass the site header each time.
• Light and dark themes, switched from the bottom of every page.

3What does not work yet

• We have not run a full audit against WCAG 2.2, by ourselves or by anyone else. We would rather say so than publish a conformance claim we have not earned.

bricknity is run by a micro enterprise, which the European Accessibility Act does not require to meet its service rules. We hold ourselves to WCAG 2.2 level AA anyway, and this page says honestly where we fall short.

4Tell us

If something here is hard or impossible to use, write to [email protected]: say which page, what you were trying to do, and what you use to browse if you are happy to. We reply within 3 working days.