Accessibility statement

StageReady Web builds to WCAG 2.2 level AA as a working standard. That applies both to this site and to the sites we build for clients. We treat it as part of the craft rather than something added at the end.

This page describes how stagereadyweb.com is built, what has been tested, and where we know work is still outstanding.

• Everything that can be clicked can be reached and operated with a keyboard alone.
• Every interactive element has a visible focus ring, drawn with :focus-visible so it shows for keyboard users without getting in the way of mouse users.
• The first tab stop on any page skips straight to the main content.
• Smooth scrolling is configured so the browser’s own jumps to anchors still work and content does not land underneath the fixed header.

Measured across the page types on the site:

• Exactly one h1 per page.
• No skipped heading levels, so a screen reader’s outline is usable.
• Every image has alt text. Purely decorative elements are hidden from narration.
• No repeated id values, which would otherwise break the link between a field and its label.
• Comparison tables are real tables with column and row headers, not boxes arranged to look like a table.
• FAQ answers sit in the page text rather than behind a click. That holds for screen readers and for search engines alike.
• The content on each page declares its language, so Danish and English are pronounced correctly.

The orange in our identity measures roughly 1.9:1 against the light background. That is too low for text, so we never use it for body copy on light. It is used for whole fields, rules and buttons instead, with dark text on top.

• Body text and headings are dark on light or light on dark.
• Colour is never the only way something is conveyed.
• Form errors show in red with a message beside them, not just a coloured border.

Motion is decoration on this site and never information. Nothing requires you to see an animation to understand or use the page.

• Turning motion down in your operating system disables both the smooth scrolling and every reveal.
• There is no autoplay, no carousel, and nothing that flashes.
• Smooth scrolling does not run on touch — the system’s own is better there.

These are the ones we know about:

• The comparison tables need horizontal scrolling on a phone. The table scrolls inside its own container so the page itself stays put, but it is still not a good experience on a small screen.
• The site has been tested with a keyboard and reviewed in code. It has not been tested end to end with disabled users. That is the next thing missing, and we will not write that it has been done before it has.
• Contrast is checked against the combinations the design system permits, not automatically on every page at every build.
• The document’s own language is set once the page has loaded in the browser. The content declares its language from the start, so a screen reader reads the text correctly, but the very first version of the HTML document says Danish on the English pages too.

The same baseline comes with the sites we build: keyboard operation, headings that hold together, alt text, contrast that holds up, and motion that can be turned off.

If a project has to meet a particular standard or regulation, agree it at the start so it can be built in and documented along the way. Which rules apply to your specific business is a legal question, and it needs answering somewhere other than here.

Write to us. Describe what you were trying to do, which page you were on, and what you are using — browser, screen reader, or other assistive technology. We reply within 48 hours and fix what we can fix.