Accessibility statement

Our target

Altstamp aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, in the current edition of the W3C Recommendation, dated 12 December 2024.

On two points we aim higher than AA. Body text, the paragraphs and lists you read on the white page, is held to a contrast of at least 7:1, the Level AAA figure in 1.4.6 Contrast (Enhanced), where AA asks for 4.5:1. And the keyboard focus ring is a solid 3 px outline on every control, thicker than 2.4.7 Focus Visible requires.

The 7:1 figure covers body text only. Short labels meet AA, not AAA: in the comparison tables, grey text on the grey striped rows measures 6.26:1, and the status words “Check with the vendor”, set in a dark orange (#B4400A), measure 5.71:1 on white and 5.10:1 on the striped rows. The Pass and Fail words on the contrast check measure 5.79:1 and 6.40:1 on their tinted chips. All of these are above the 4.5:1 that 1.4.3 Contrast (Minimum) asks for.

Where we are

We have not made a formal conformance claim for the whole site. Every page on it, the checks, guides, comparisons, topic pages, indexes and this statement, was tested with the checks below on October 23, 2026, before the site launched. A page that is added or changed is tested the same way before it is published, and this statement is updated with it.

How we tested

We tested in Chromium, with these checks on each page:

• Automated rules: axe-core 4.11 with its WCAG 2.0, 2.1 and 2.2 Level A and AA rules and its best-practice rules, on every page, at a phone width (375 px) and a desktop width (1280 px).
• Keyboard only: the skip link is the first stop, it moves focus to the main content, every link, button and field shows a 3 px orange focus ring, and the phone menu opens and closes from the keyboard.
• Focus not hidden: nothing that takes focus ends up under the bar that stays at the top of the screen on wider windows.
• Target size: every link and button in the header and footer is at least 24 by 24 px.
• Reflow: no page scrolls sideways at widths from 320 px to 2560 px.
• Contrast: body text is ink or a dark grey that measures at least 7:1 on its background. Short labels in tables and result chips are checked against the AA figure of 4.5:1 instead (see Our target).
• Reduced motion: with the system setting to reduce motion, every element is visible at once and nothing animates.

Automated tools find only part of what can go wrong, which is why the keyboard and layout checks are done by hand as well. The patterns these checks look for are shown, one element at a time, in accessible website examples.

Known issues and gaps

One part is left out of the accessibility tree on purpose. The preview box on the contrast check shows the two colours you entered, and they may well fail, so the box is marked inert: it is out of the tab order and hidden from screen readers, and the ratio and every Pass or Fail are given in text beside it.

Some examples fail on purpose, to show what a fail looks like:

• The demo in focus indicators has one button with no focus ring and one with a faint 1px grey ring. Each sits in a box that draws this site's orange ring while the button has focus, so you can always see where focus is.
• The scrim slider in colour contrast requirements can be moved down to 0%, where its white text measures 1.07:1. It starts at 55%, which passes, says the ratio in words as it moves, and does not print.
• The samples marked “Fails 1.4.1” in use of colour carry meaning by colour alone. They are drawn text, not working links or fields, and each pair has a button that shows it without colour.
• The spacing demo in ADA compliant fonts cuts a sample card's text off when you press its button. The card is held to a fixed height only while the demo is on, so your own text-spacing tool still works on the page.
• The two examples marked “Fails 3.3.2” and “Fails 1.4.1” in ADA compliant forms are drawings of bad fields, not working fields: they are hidden from screen readers and out of the tab order, and the note under each says in words what it shows.

The contact form needs JavaScript to send. If it does not work for you, email contact@altstamp.com instead and the message reaches the same people.

What the site relies on

The pages are HTML and CSS with WAI-ARIA where HTML alone is not enough. JavaScript is used for the checks, the contact form, the “On this page” highlight and the entrance motion. Every page can be read with JavaScript turned off. The checklists, the colour palette check and the VPAT template keep what you enter in this browser's local storage so it survives a reload; it is not sent to us.

Report a barrier

If something on this site is hard or impossible to use, tell us. Name the page and what happened. Write through the contact page or email contact@altstamp.com. We read every message and fix what we can, and we will tell you if a fix will take time.

This statement follows W3C's outline. To write one for your own site, use our accessibility statement generator.