Skip to content
SaaSHelms home
AdvertiseGet listed free
Home

Accessibility statement

Our target is WCAG 2.2 AA. Here's what we've built in, what we know about, and how to tell us about a problem.

Page owner: [Editor-in-chief] Updated

Our target

We want everyone to be able to use SaaS Helms, including people who use screen readers, keyboard navigation, magnification or voice control. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.

What we've built in

  • Text contrast of at least 4.5:1, and a visible focus ring on every link, button and control.
  • A "Skip to content" link, labelled landmarks and real headings in order.
  • Tables with proper headers and captions; wide tables can be scrolled with the keyboard.
  • Filters, sort, compare, accordions, menus and pop-overs that work with the keyboard; Esc closes overlays and returns focus.
  • No information shown by colour alone: every chip and yes/no cell has text or an icon.
  • Touch targets of at least 24×24px, and 44×44px for main mobile actions.
  • No carousels, autoplay or flashing content; motion is switched off if your device asks for reduced motion.
  • A cookie banner that never traps focus or blocks the page.

Current status

Status on 19 Oct 2026: our templates are designed to meet WCAG 2.2 AA, but the site has not had an independent accessibility audit yet. Known issues: none recorded so far. We will list any issue we find here, with the date and our plan to fix it.

Tell us about a problem

If something on SaaS Helms is hard to use, email [contact email] with the subject "Accessibility", the page URL and what happened. We aim to reply within 2 working days. If you need content in another format, ask and we will help.