Perspectives

What does this evidence actually tell us?

Standards, research, platform guidance, first-person accounts and interpretation answer different questions. No Default keeps those source types visible instead of blending them into one voice.

Current perspectives

Standards + user evaluation

A passing checklist is not the same as a usable experience

W3C recommends combining standards-based evaluation with evaluation involving disabled people, while warning against generalising from one participant.

Source: W3C WAI — Involving Users in Evaluating Web Accessibility

Reviewed 7 Oct 2026

Guidance beyond conformance

Some important cognitive accessibility needs sit beyond WCAG conformance

W3C’s cognitive accessibility resources distinguish normative standards from supplemental, informative guidance intended to meet more user needs.

Source: W3C WAI — Cognitive Accessibility at W3C

Reviewed 7 Oct 2026

User diversity

One disabled person is evidence, not a representative sample

Disabled people differ in experience, preferences, adaptive strategies and assistive-technology configurations. First-person evidence should not be flattened into claims about an entire group.

Source: W3C WAI — Involving Users in Web Projects

Reviewed 7 Oct 2026

Platform guidance

Assistive-technology testing requires proficiency and a named environment

Apple’s VoiceOver evaluation guidance expects proficient testing and recognises that experienced users may rely on advanced functionality. No Default therefore scopes AT evidence to the environment actually tested.

Source: Apple Developer — VoiceOver evaluation criteria

Reviewed 7 Oct 2026

No Default interpretation

A successful task can still contain an accessibility barrier

Completion alone can hide additional effort, workarounds, repeated requests for help or recovery work. This is a working interpretation used across No Default and should be challenged where evidence does not support it.

Source: No Default — Barrier Library

Reviewed 7 Oct 2026