A statement must offer a channel for reporting newly found barriers

What it is

The list was written on some past day; new failures will appear tomorrow. A statement therefore has to give an accessibility feedback mechanism: a person can report a barrier they have just hit, and that channel itself can be finished. Email, a form, a phone line — the medium is secondary. It must be submittable from the keyboard, name a readable clock, and name an escalation (equality body, regulator). A channel buried on the page being complained about, behind a graphic CAPTCHA, is not a channel.

Why it happens

Conformance snapshots expire, and an organisation's own tests do not cover everything. Feedback treats users as ongoing sampling. The second layer is that the channel's own accessibility decides who is in the sample: if only people who can see well and pass a CAPTCHA can write in, reports will repeat problems already visible, and the people actually blocked never enter. An unstaffed alias inbox is no channel — the pressure mechanism needs an acknowledgement and a clock, or the complaint dies at send. The channel in the statement is also an on-ramp to enforcement: many templates require naming whom to escalate to next; without that sentence, the user is left inside the company's process.

Studying it

Actually submit a “report a barrier” with a screen reader, keyboard, and voice control. Record whether it completes, whether the acknowledgement is dated, whether anyone answers inside the clock. Count failures of the channel itself (CAPTCHA, unnamed fields, in-app only). Check whether the statement text names an escalation path.

Independent variables: medium (mail / form / phone); presence of a CAPTCHA; whether a clock is promised. Dependent variables: whether an assistive-technology user can submit; acknowledgement rate; days from report to list update; abandons caused by the channel.

Do not take “there is a contact-us link” as a channel — that link may point at sales.

Where it stops holding

Security reporting and abuse complaints use another door; do not force them into the accessibility form, but point to them in the statement. Rate-limiting under attack is allowed; it cannot collapse to a graphic challenge alone — keep a phone line or a simplified form for signed-in users. Staff can file defects in an internal tracker; the public statement still needs a public door. A channel is not a substitute for your own testing: zero reports may mean a broken channel, not a clean product.

Applying it

• In a “how to report” section, give at least two media, one of which does not depend on a graphic CAPTCHA, and name the response clock and the escalation party.
• Associate form fields programmatically with their visible labels. After submit, give a confirmation and a case number a screen reader can read.
• On-duty staff write reports into the defect queue and acknowledge inside the clock. If the clock is missed, change the number in the statement or add people.
• How to check: finish a barrier report from the keyboard with the display off. If that fails, fix the channel before talking about the product. Two weeks later, see whether the report entered the defect tracker and whether the public list gained a matching item.

Related

• Same group: J1.12.1 A statement must list known failures, not only claim overall compliance · J1.12.3 A statement must name test methods and the last update date · J1.12.4 Conformance documents are useless unless they are themselves accessible
• Nearby: J1.11.2 Litigation and complaints are the de facto enforcement in many places · H1.15 Accessible Form Labeling
• Search terms: accessibility feedback mechanism · report a barrier · accessibility statement