What we aim for
Conformance with WCAG 2.2 at level AA. The site is built by hand rather than from a theme marketplace, so most of what follows is deliberate rather than accidental.
What is in place
- A skip link, landmark regions, and one H1 per page.
- Every image carries alt text; decorative product art is hidden from assistive technology.
- Keyboard access to the menu, the search overlay and the theme toggle, with visible focus and focus returned to where you were when a dialog closes. Menu and search buttons that open a panel announce that with
aria-haspopup. - Comparison tables with named columns and a caption; the product column stays pinned on phones, and a table that scrolls horizontally on a narrow screen can be scrolled with the keyboard, not only a swipe.
- Text and interface colors checked against the 4.5:1 contrast threshold in both the light and dark themes, page by page, with one exception: see Known gaps.
- Form fields, including the newsletter signup, meet the minimum tap-target size.
- Animation that respects your system’s reduced-motion setting, in both of the site’s animation systems.
- Native, non-JavaScript FAQ accordions, so they work without scripts.
Known gaps
- One department-color background style, used behind hero images on a handful of pages, doesn’t reach 4.5:1 for lighter body text at its exact center point. We calculated this from the color values rather than finding it on a live page; if you spot text that’s hard to read on a colored background, that’s likely it, and we want to hear about it.
- We verify keyboard Tab order and focus-ring visibility by reading the code that handles it, not yet by recording a live pass on every template; a recorded keyboard walkthrough is scheduled for our next accessibility review.
- Some pages carry a “checked” freshness line at 12px; we are raising it.
- Our automated checks run in light mode; dark-mode contrast is checked by hand, less often.
- Third-party embeds (the cookie-consent banner, occasional YouTube frames) follow their providers’ accessibility, not ours.
In plain terms
The core reading path, from a guide’s verdict through its comparison table to the buy button, works with a keyboard and a screen reader today. The gaps above are real, narrow, and listed on purpose: we’d rather name a limitation than claim a badge we haven’t earned.
Tell us
If something on this site does not work for you, email support@beforeyoubuyguide.com with the page address and what happened. Accessibility reports jump the queue the same way corrections do; we reply within a few days and log fixes on the corrections page.
Last updated September 27, 2026