Structure and landmarks
Pages use one main landmark, one primary heading, ordered section headings, and semantic header, navigation, article, list, and footer elements where appropriate.
Access standard · record A-11
Accessibility Statement
The Bureau aims for WCAG 2.2 Level AA and documents what the site supports, what remains outside its control, and what has not yet been formally tested.
Conformance record
Target stated without a false certificate
WCAG conformance is a testable claim. This site states its target and assessment method separately rather than treating good intentions as certification.
Accessibility is part of document control
A file is not complete when a keyboard user cannot reach it, a heading does not describe it, a focus state disappears, or essential image information is available only by sight.
Implemented controls
What the site is designed to support
These controls are part of the current design system and publishing checks. They still require continued review as content and commerce features are added.
Keyboard and focus
Navigation and links are keyboard reachable, the site provides a skip link, controls target at least 44 pixels, and focus-visible states use a high-contrast outline.
Colour and state
Approved text-and-paper colour pairs meet the documented contrast roles. Status is also written in words or rules rather than communicated by colour alone.
Responsive reading
Layouts collapse through verified breakpoints, long labels can wrap, reading columns remain bounded, and cards avoid fixed copy heights that clip enlarged text.
Images and text equivalents
Editorial and product images require meaningful alternative text when they convey information. Decorative filing lines are hidden from assistive technology.
Motion and interaction
The design avoids hover lifts, parallax, autoplay, flashing effects, and motion-dependent meaning. Hover is not the only way to reach content.
Limitations register
Known boundaries and planned handling
A useful statement names gaps in ordinary language. It does not hide them behind a claim that every possible browser and assistive technology combination has passed.
- Formal testing
- The full site has not yet received an independent accessibility audit or broad disability-led usability test.
- Avoid a full-conformance claim; continue manual and automated checks and record verified issues.
- Third-party shops
- Marketplace pages, checkout, and account flows are operated by external platforms and may not match this site's controls.
- Name the destination before transfer and evaluate verified store links before publication where practical.
- Product artwork
- Print-on-demand art can contain stylized visual text that is not a structured digital document.
- Provide the essential wording and context in nearby web copy or alternative text; do not rely on the product image alone.
- Feedback channel
- A verified, monitored public accessibility contact route is not active.
- Publish the route only after the address, responsibility, privacy handling, and response process are real.
Technical record
Compatibility and technologies
The site is built with semantic HTML, CSS, JavaScript, and SVG. It is intended for current standards-supporting browsers and assistive technologies; older or unusual combinations may expose defects not yet recorded.
Input
Keyboard, pointer, and touch
Core navigation and reading should not require a precise pointer or a hover gesture. Focus order is expected to follow the document order.
Presentation
Zoom and reflow
Text and components are designed to reflow through the registered responsive layouts without hiding primary actions or creating horizontal page overflow.
Semantics
Names, roles, and purpose
Controls and links use visible labels that describe their destination. Decorative elements do not receive misleading accessible names.
Assessment & future feedback
What an actionable barrier report includes
The eventual Records Desk should ask only for details that help reproduce the problem and provide an alternative.
Field 01
Page
The URL and the heading, control, image, or file involved.
Field 02
Barrier
What could not be perceived, understood, reached, or operated.
Field 03
Environment
Browser, device, operating system, and assistive technology if relevant.
Field 04
Goal
What the reader was trying to read, download, submit, or purchase.
Field 05
Alternative
A preferred accessible format or workaround, when one is known.
Current assessment method
The present statement is based on internal self-evaluation of page structure, responsive layouts, design-token contrast, keyboard-visible states, image alternatives, and rendered templates. It is not an external certification. Material accessibility errors follow the Corrections Policy.
Statement guidance
W3C WAI: Developing an Accessibility Statement
Last reviewed: 11 October 2026 · Review trigger: material template, navigation, form, product, or marketplace change
Related controls
Access defects are record defects.
See how significant accessibility problems are classified, amended, and documented.