Our Goal
We want BlueprintPC to work for everyone, regardless of ability or the device or assistive technology used to browse it. Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.
Current Status
We audited the site in August 2026 against the WCAG 2.2 AA target and fixed what we found. Every page we test now reports zero critical or serious automated violations, and we check this the strict way: across all five visual themes in both light and dark mode, rather than only the default. That sweep is part of our build pipeline, so a change that reintroduces a problem fails before it ships.
We also test the things automated colour and markup checks cannot see. Keyboard tests drive the real interface to confirm you can never get trapped in a menu or dialog and that Escape always works. A screen reader runs against the catalogue to confirm that filtering and sorting are actually announced, not silently changed. And we simulate the three common types of colour blindness to confirm our category colours stay distinguishable from one another.
Even so, we are not claiming full AA conformance. Automated and simulated testing catches a meaningful share of barriers but not all of them, we have not yet run the site with real screen readers such as NVDA, JAWS or VoiceOver, and we have not tested it with disabled users. Until we have, "passes our checks" is an honest description and "conformant" would not be. We will update this statement when that changes.
What We've Done
The site is built to be operable with a keyboard alone, with visible focus states and focus management around dialogs and dynamic content. Animation respects your system's reduced-motion preference automatically, and we also give you a manual animation toggle in the interface if you want to turn motion off without changing your OS setting.
We've done a pass on colour contrast across all five visual themes, in both light and dark mode. And compatibility status in the builder — compatible, warning, or incompatible — is never conveyed by colour alone: every status pairs a colour with an icon and text, so it doesn't depend on colour perception.
Known Limitations
A few areas we know still need work:
- Dense comparison tables (build compare, bench leaderboards) are hard to use at very small viewport widths and need a better small-screen layout.
- The third-party benchmark client download surface links out to files we don't fully control the accessibility of, and the download/verification instructions need a clearer accessible presentation.
- User-submitted benchmark content isn't authored by us, so we can't guarantee it meets the same standard as the rest of the site.
- We haven't yet run the site with real screen readers (NVDA, JAWS, VoiceOver, TalkBack). Our automated screen-reader tests check that the right information is exposed, but real assistive technology adds its own behaviour on top, and only a hands-on pass can confirm how these flows actually feel to use.
- We haven't tested with disabled users. No amount of tooling substitutes for that, and it's the gap we most want to close.
Feedback
If you hit an accessibility barrier anywhere on BlueprintPC, tell us. Email hello@blueprintpc.com with what you were trying to do and what happened — we aim to respond within 5 business days. If you need any content on this site in an alternative format, ask and we'll work with you to provide it.