Skip to main content
NetGuard
Search
Sign in Check a domain

Accessibility statement

What we have done, what we have tested, and the two things we know are not right yet.

Last updated

Commitment

This site aims to meet WCAG 2.2 at level AA. Accessibility is not a feature that was added at the end; the colour palette was chosen by running every foreground and background pairing through a contrast check before any page was written, and the check runs as part of the test suite so a change that breaks it fails the build.

What has been done

  • All 56 colour pairings meet at least 4.5:1 for body text and 3:1 for large text and interface borders, in both light and dark themes.
  • Status is never signalled by colour alone: each message and badge carries its own icon and wording.
  • Every interactive target is at least 44 by 44 CSS pixels.
  • A single, consistent focus ring appears on keyboard focus everywhere, and is never removed.
  • The site works entirely without JavaScript: forms submit, navigation opens, search runs, and the coverage checker returns a rendered page.
  • Headings run in order with no levels skipped, and every page has exactly one h1.
  • Images carry descriptive alternative text; decorative SVG is hidden from assistive technology.
  • Form fields have real labels, errors are announced, and an error summary at the top of the form links to each field.
  • A bypass link is the first focusable element on every page.
  • Motion respects prefers-reduced-motion: transitions are reduced to near zero rather than merely shortened.
  • Text reflows to 320 pixels wide without horizontal scrolling, and remains usable at 200% zoom.

How it was tested

Keyboard-only traversal of every page and every form. Automated contrast checking of the full palette. Manual checks at 320, 375, 768 and 1280 pixels wide. Rendering with JavaScript disabled and with CSS disabled.

It has not been tested with a screen reader by someone who uses one daily, and it has not been through a third-party audit. Saying otherwise would be the kind of claim this site exists to avoid.

Known problems

  • The blocklist tables on the coverage page are long. They are inside a scrollable region with a keyboard focus stop, which is correct but tedious to traverse. A filter control would be better.
  • The uptime bars on the status page convey their information through an adjacent text summary. The bars themselves are hidden from assistive technology rather than made meaningful individually.

Telling us about a problem

Email hello@netguard.example or use the contact form. We reply to every enquiry within one working day. Please say which page and what happened; a description of what you expected is more useful than a screenshot.

This statement was prepared on 21 August 2026 by reviewing the site against WCAG 2.2 AA. It is reviewed whenever a page is added.

Contact