Accessibility Statement

This statement explains how we design and test accessible form tasks, the limits we know about, and how to report a barrier.

Effective November 11, 2026

At a glance

Form control

Each control needs a clear label, keyboard access, visible focus, and an error that explains the fix.

Form owner

The owner must test every adapted question and provide another support route if the form blocks a person.

Accessibility report

A useful report names the page, task, barrier, and optional device details without demanding expert language.

Our approach

We aim for keyboard operability, persistent labels, visible focus, meaningful headings, clear errors, responsive layouts, and sufficient contrast. We test common form flows at narrow widths and with browser zoom.

Known limits

User-created forms can include unclear wording or color choices outside our editorial templates. Form owners should test their adapted form and provide an accessible support route.

Feedback

If a page or form blocks you, report the page address, task, browser, device, and assistive technology when you are comfortable sharing them. We will investigate the barrier and provide an alternative route where practical.

Related implementation guidance

Apply the online form accessibility checklist and adapt the accessibility feedback template when collecting reports.