Accessibility

Last updated 23 August 2026 · ScorpEase LLC

We want scorpease.com to be usable by everyone, including people using a screen reader, a keyboard only, magnification, or a device we have never tested on. This page says what we target, what is actually built, and what we know is still imperfect.

What we aim for

We target WCAG 2.1 Level AA. We do not claim to have been independently audited against it, and this page is not a conformance certificate. It is a description of the current state, written by the people who built the site.

What is built in

Keyboard navigation. Every page starts with a "Skip to Content" link, and every interactive element is reachable by keyboard in a sensible order.
Visible focus. Focus outlines are never removed. Anything you tab to shows where you are.
Semantic structure. Real headings, one h1 per page, real lists, real landmarks. Expanding FAQ answers use native details elements, so they work without JavaScript and announce their state to a screen reader.
Text alternatives. Every content image has alt text. Where an image has words baked into it, the alt text conveys those words rather than just describing the picture. Decorative images are marked as decorative so they are skipped.
Readable text. Body text is set at 16px or larger, with generous line height and a constrained line length. Text scales when you zoom; nothing is locked to a fixed pixel layout.
Colour. Text is not the only way information is conveyed. Product accents are always paired with a label.
No motion. There are no animations, auto-playing media, carousels or anything that moves on its own.
No pop-ups. Nothing interrupts you — no modals, no cookie banner, no newsletter overlay.
Works without JavaScript. Every page is readable and navigable with scripts disabled. The only script on the site rewrites our email address into a clickable link, and it degrades to readable text.

Known limitations

Being specific here is more useful than claiming perfection:

One blog post has a heading-level skip. An older migrated post jumps from h1 to h3, which makes its outline harder to navigate by headings. It is on the list to fix.
Some blog header images carry text as part of the artwork. The alt text conveys the wording, but that text cannot be resized or re-coloured the way real text can.
We have not tested with every assistive technology. Testing has been keyboard, browser zoom, and structural review — not a full screen-reader pass across multiple products.
Third-party pages are outside our control. The Salary Sherpa questionnaire is hosted by Tally and Keystead Vault is a separate application. We have not assessed either against this standard, and problems there need to be raised with us so we can pursue them.

Telling us about a problem

If something on this site is hard or impossible for you to use, please tell us — it is the fastest way for it to get fixed, and we would rather hear about it than not.

Email us and describe what you were trying to do, what happened, and what you were using — browser, device, and any assistive technology. You do not need to know the technical cause.

We read every message. If something is straightforward we will usually fix it quickly; if it is not, we will tell you honestly what the timeline looks like.

If you need the information another way

If any part of this site is not working for you, email us and we will provide the same information in another form — plain text, a phone call, or whatever works. That includes the Salary Sherpa questionnaire: if the form is not usable for you, we will take your answers another way.