Accessibility

Accessibility commitment

This site targets WCAG 2.2 AA through semantic design, keyboard support, contrast, reflow and ongoing review.

Page purpose

How Accessibility commitment is applied and where the commitment is bounded.

The Accessibility page explains the site's intended direction: content and interactions should be understandable, perceivable and operable across a range of devices, input methods and assistive technologies. It describes the design and engineering practices used to pursue that goal, such as semantic structure, keyboard access, readable contrast, reflow and meaningful labels. This is a commitment to ongoing attention and remediation, not a claim that every page, component, browser and assistive-technology combination is fully conformant or free of barriers.

The page also defines the limits of the statement and provides a route for feedback. Automated checks can identify some issues, while manual review and lived experience reveal others; neither a tool score nor a single test establishes complete accessibility. Visitors should use the published site contact channel to report a barrier, including the affected page, task and technology where comfortable, without sending sensitive information. Feedback can then be reviewed, clarified and prioritized within the site's maintenance process.

Target

The outcome targeted by the commitment.

A clear statement of accessibility intent without a blanket conformance claim.
Transparent limits on what testing and the published statement establish.
A usable feedback route for reporting barriers and supporting investigation.

Application

How the target is applied and reviewed.

Design content and interaction with semantic, keyboard, visual and responsive needs in view.
Combine automated checks with manual inspection and representative task testing where feasible.
Document limitations without treating a passing score as complete assurance.
Invite barrier reports through the site's published contact channel.
Review the reported context, clarify when needed and prioritize remediation proportionate to impact.

Verification

What is monitored and checked.

Priority journeys can be completed using keyboard and supported assistive interaction patterns under tested conditions.
Accessibility feedback contains enough non-sensitive context to investigate the barrier.
Confirmed issues receive an owner, disposition and follow-up within the maintenance process.
The statement is reviewed when material site or testing scope changes.

Known limits

What this statement alone does not establish.

Stating or implying complete WCAG conformance without sufficient current evidence.
Relying on automation while missing keyboard, screen-reader, zoom or cognitive barriers.
Requesting unnecessary personal or sensitive information in an accessibility report.
Leaving the statement unchanged as the site and its components evolve.

Decision questions

Clarifying the target, limits and feedback route.

What does this page establish about WCAG conformance?

It describes an accessibility goal, supporting practices and the limits of available review; it does not establish full conformance. Conformance requires evidence for a defined scope and point in time, and real combinations of content, browsers and assistive technologies may still reveal barriers that need investigation.

What information should I include when reporting a barrier?

Use the published site contact channel and, where comfortable, include the page address, the task you were trying to complete, what happened, and the browser or assistive technology involved. Do not send passwords, confidential records or unnecessary personal information.