ACCESSIBILITY TASK · REVIEWED AUGUST 31, 2026
Plain-Language Check for Controls and Costs
People should understand what a control does, what is synthetic and where payment or account boundaries begin.
This task records scoped evidence. It is not accessibility certification, legal advice or a universal result.
What this page owns
Check whether companion controls and payment boundaries use understandable language.
Begin with the named task and preserve the setup. Do not turn a product statement, automated scan or reachable page into proof that a person can complete the task.
Four steps, one documented result
- 01
Read navigation and button labels without surrounding visual context.
- 02
Identify AI and fictional-character disclosures before a commercial route.
- 03
Check whether price, credits, renewal and cancellation words are concrete.
- 04
Ask whether an error tells the reader what to do next.
Make the observation reproducible
- Setup
- Device, operating system, browser, input method and assistive technology.
- Task
- Starting point, action and expected outcome in plain language.
- Result
- Pass, barrier observed or not checked — never a guessed score.
- Limit
- Plain language reduces avoidable confusion but does not replace complete terms or individual support needs.