Accessibility Statement

The standard applied

This site targets the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. That is the level referenced by most public-sector procurement rules and the one that Title III litigation against business websites in the United States is generally measured against.

What that means here

• Semantic HTML with one logical heading order per page, so a screen reader can navigate by structure.
• Every interactive control reachable and operable by keyboard alone, with a visible focus indicator that is never removed.
• A skip link to the main content as the first focusable element on every page.
• Text contrast meeting or exceeding 4.5:1 for body copy and 3:1 for large text and interface components.
• Text alternatives on images that carry meaning, and empty alternatives on images that are purely decorative.
• Diagrams published as inline SVG with a role and an accessible label describing what the figure shows, rather than as flat pictures of text.
• Form fields with real labels, errors reported in text rather than by color alone, and status messages announced to assistive technology.
• Layouts that reflow to 320 CSS pixels and remain usable at 200 percent zoom, without horizontal scrolling.
• No content that moves, flashes or auto-plays, and no motion that cannot be reduced by the operating system preference.

Known limitations

Stating a standard is easy; the honest part is where the site falls short of it.

• Third-party embeds. Content served from another provider — payment forms, social embeds, mapping — is not fully under this studio’s control. Where an embed is known to present barriers, an accessible alternative route to the same task is provided.
• Complex diagrams. A technical figure has an accessible label and is explained in the surrounding text, but a diagram with many data points is harder to convey in a label than in a table. Where the detail matters, the data is also given as a table.
• Older articles. Material published before a given standard was adopted is brought up to it on review rather than all at once.

Testing

Pages are checked with automated tooling and by hand: keyboard-only navigation, screen reader passes, contrast measurement, zoom and reflow at mobile widths. Automated tools catch a minority of real barriers, so they are treated as a first pass rather than as proof.

Reporting a barrier

If something on this site is unusable with the technology you use, report it through the contact page and choose the accessibility topic. Describing the page, the technology and what happened is enough. Accessibility reports are handled with the same priority as corrections.

If the contact form itself is the barrier, email [email protected] directly.

Last reviewed October 8, 2026.