Skip to content
Skip to content
TechSpecs
Accessibility

Accessibility Statement

Our commitment to making TechSpecs usable by everyone, the standards we follow, and how to report an accessibility barrier.

Last updated: June 2026

TechSpecs is committed to making our content usable by as many people as possible, including those who rely on assistive technologies. We treat accessibility as part of building the site well - an ongoing effort, never an afterthought.

The standard we aim for

WCAG 2.1, Level AA

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA - the widely adopted benchmark for making web content more perceivable, operable, understandable, and robust for everyone, whatever device or assistive technology they use.

What we do

How we put that into practice

Accessibility shows up in the day-to-day decisions we make about structure, colour, and interaction across the whole site.

Semantic structure

Pages use proper headings, landmarks, and lists so screen readers can navigate and skim them.

Keyboard access

Every interactive element is reachable and operable with a keyboard, with a clearly visible focus state.

Colour & contrast

Body text and meaningful UI meet AA contrast, and you can switch between a light and dark theme.

Text alternatives

Images that carry information include descriptive alt text so nothing is lost without sight.

Responsive & scalable

Content reflows and stays readable when zoomed or viewed on small screens, without horizontal scrolling.

Reduced motion

We honour your operating-system “reduce motion” preference and keep animation subtle and optional.

Being honest

Known limitations

We’re not perfect yet. Some older content predates our current standards, and embedded third-party material or advertising served by partners may not fully meet our target. Where a third-party component falls short, we look for an accessible alternative - and we’re continually reviewing and improving the site.

Report a barrier

Hit a wall? Tell us

If something on TechSpecs is hard or impossible to use, we want to fix it. To help us reproduce the problem quickly, please include:

  • The page URL where it happened
  • What went wrong and what you expected
  • Your browser and any assistive technology you were using
Report a barrier