Accessibility, stated honestly.
We want this site to work for everyone who needs it. This page says what we aim for, what we have actually built, and where we still fall short — so you can judge it yourself.
Last updated: 2026-10-15
An honest note
We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our target, and we build with them in mind. We have not completed an independent accessibility audit, so we do not claim full conformance. What follows is a description of what is really in the code today, plus the gaps we already know about.
If something on this site gets in your way, that is a bug worth fixing. The contact section at the bottom of this page says exactly how to report it.
A way past the navigation
Every page starts with a “Skip to content” link that becomes visible on keyboard focus and jumps to the main content.
One clear heading per page
Each page has exactly one top-level heading, with sections and sub-sections nested beneath it in order.
Real landmarks
Pages use a main region, header, navigation, and footer rather than a wall of divs, so assistive technology can move between regions.
Visible keyboard focus
Interactive elements show a clear focus outline — reinforced across links, buttons, fields, tabs, and menus — so keyboard users can always see where they are.
Respect for reduced motion
When your device asks for reduced motion, the site's animations and transitions are cut down and reveal effects show their content immediately.
Forms that announce themselves
Fields have real labels; hints and errors are linked to their control; required fields are marked visually and for screen readers; and success or failure is announced and focused.
Decoration stays decorative
Decorative graphics and the footer banner are hidden from assistive technology, so they are not read out as meaning.
Native controls where possible
Grouped choices use a real fieldset and legend, and native inputs give keyboard behaviour for free.
Language and colour scheme declared
Pages declare their language and advertise the dark colour scheme so native controls and browsers match.
Reflows to a phone
Layouts collapse to a single column and long email addresses and links are allowed to wrap, so pages fit a narrow screen without sideways scrolling.
No independent audit yet
We have not had the site tested by an external accessibility specialist or by people using a wide range of assistive technology. Until we have, conformance is an aim, not a badge.
Dark theme only
The site ships a single dark colour scheme. There is no light mode yet, which will not suit everyone.
Some features need JavaScript
Form submission and the live Problem Commons and project lists rely on JavaScript. The site's written content is static and readable without it, but those interactive features are not.
Large decorative display type
Headings use a large display typeface. Text reflows and can be enlarged, but we have not yet checked every page at the maximum browser zoom.
The admin panel is out of scope
This statement covers the public site. The internal stewardship panel behind Cloudflare Access is not part of the public experience and is not covered here.
Animations are reduced, not individually audited
We respect the reduced-motion setting globally, but we have not audited every individual animation by hand.
The most useful report names the page, what you were trying to do, what happened, and what you were using — your browser, your device, or the assistive technology you rely on.
You can also leave feedback through the site’s contact form and choose “Something is broken”.
We aim to acknowledge an accessibility report quickly and to tell you honestly whether and when it will be fixed. No silent queues.
Report an accessibility issue
A person reads every message, usually within 72 hours.
hello@buildforgood.org