Accessibility Statement

Chip Reign of ChipReign

Last updated: April 2026

ChipReign commits to WCAG 2.1 Level AA as a minimum standard across chipreign.com. This page lists what we do to meet it, what we know we don’t meet yet, and how to tell us when we’ve fallen short. Accessibility is a reader right, not an afterthought.

Our Commitment

chipreign.com aims to comply with the Web Content Accessibility Guidelines 2.1 at Level AA, published by the W3C. In the US that aligns with the ADA’s de facto accessibility standard as applied by federal courts to consumer websites. In the UK the equivalent benchmark is the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 read with the Equality Act 2010. In Australia, the Disability Discrimination Act 1992 and the Australian Human Rights Commission guidance draw on WCAG 2.1.

We don’t claim perfect compliance. Web accessibility is continuous work, especially on a site that publishes new articles every week. This page tells you where we stand today, what we’re fixing, and how to flag anything that’s broken for you.

What We Do

  • Semantic HTML. Article pages use proper heading structure (one H1, ordered H2/H3/H4) so screen readers can navigate.
  • Keyboard navigation. Every interactive element (links, buttons, menus) is keyboard-focusable with visible focus indicators.
  • Colour contrast. Text and background contrast meets or exceeds 4.5:1 for body copy and 3:1 for large text.
  • Alt text on informative images. Images that carry information have descriptive alt text. Decorative images use empty alt attributes so screen readers skip them.
  • Descriptive link text. “Read our Review Methodology” instead of “click here”. Screen reader users rely on link text to navigate.
  • Scalable layout. Pages work at 200% zoom without breaking, and reflow on mobile without horizontal scroll.
  • Accessible tables. Data tables use proper th and caption where appropriate.
  • Form labels. Every form field has an associated label.
  • Skip-to-content link. Keyboard users can skip the site header on every page.
  • No auto-playing media or timed content. Nothing plays on page load. If we ever embed video, it carries captions and a transcript.

Known Limitations

Things we know are not fully accessible yet:

  • Third-party embeds (for example, an operator’s promotional widget if we test one) may not meet WCAG 2.1 AA. Where we embed third-party content we review the accessibility and, if it fails, either rework it or remove the embed.
  • Older articles republished from source may contain decorative images with unnecessary alt text or tables missing headers. We fix these during the article’s normal re-test cycle (see the Editorial Policy).
  • We do not currently publish separate large-print or plain-language versions of technical pages. Browser zoom and Reader Mode are the current best practice for readers who need them.

Assistive Technology We Test With

  • VoiceOver on iOS and macOS.
  • TalkBack on Android.
  • NVDA with Firefox and Chrome on Windows.
  • Keyboard-only navigation on every major browser.
  • Browser zoom to 200% and 400%.
  • Automated scans with axe DevTools, Lighthouse and WAVE.

Automated scans catch about half of what human testing finds. We take both seriously.

How to Report an Accessibility Problem

If a page on chipreign.com is inaccessible to you, tell us and we’ll fix it. Email editorial@chipreign.com with:

  • The URL of the page.
  • The specific issue (which element, what went wrong).
  • The browser and assistive technology you were using, if relevant.

Response target: 3 business days to acknowledge, 10 business days to fix or explain why a fix takes longer. We publish material accessibility fixes in the site-wide Document History.

Related ChipReign Policies

Accessibility intersects with several other ChipReign policies. For how accessibility feedback becomes a site update, see our Corrections Policy. For how we produce and review content in the first place, see our Editorial Policy. For how to reach us, use the routes on our Contact page.

Escalation

If we don’t resolve an accessibility issue satisfactorily, you can also contact:

Document History

DateChange
2026-04-19Initial publication. Targeting WCAG 2.1 Level AA as minimum standard.