Search Handbook Cards

Accessibility addresses a wider range of abilities; usability addresses achievement for a specified user group

Accessibility settings need one centralised hub, not scattered menus

First launch should surface accessibility options

Accessibility laws differ in scope

Retrofitting costs far more than building accessibility in

Accessibility is usually legally constrained while usability is not, which changes how each is driven

Accessibility belongs in requirements, not in the acceptance checklist

Passing accessibility checks is not the same as being usable by disabled users

Newer standards place usability inside a broader quality-in-use concept alongside accessibility, not containing it

Accessibility standards must cover real conditions — extreme weather and low light

Double clicking is a barrier for people with motor-control impairments

Assistive technology reads the accessibility tree, not the pixels

Accessibility must be designed in before construction, not retrofitted after

Red for error and green for pass, with nothing else distinguishing them, fails accessibility outright

Duplicate in-app accessibility controls collide with system settings

Public facilities need accessibility across visual, auditory and motor impairments

Inherit OS accessibility settings rather than shipping a parallel stack

State changes must be written to the accessibility tree, not only to appearance

Spatial audio is an important accessibility channel

Accessibility and input methods are where cracks appear first

Improvements made for extreme ability conditions usually raise usability for ordinary users too

The reachability of help paths determines whether harm is discovered

Paid disabled participants belong in early design, not only acceptance

Narrow windows make combos viable only for high reaction speed

One-handed modes must keep every core action, not amputate features

Label and field must be associated in the accessibility tree

Conformance documents are useless unless they are themselves accessible

Ignoring system font size, reduced motion, or contrast splits the experience

A ramp built for wheelchairs ends up serving strollers, luggage, and cyclists too

Public terminals must accommodate different heights and physical abilities

Screen readers don't see pixels — they query the accessibility tree apps expose

Apps must respond to system setting changes live, not only on restart

Scale testing must include the system’s largest type bucket, not only the usual range

Turning off challenge should not turn off content

Screen readers speak from a virtual buffer, not from pixels

A statement must offer a channel for reporting newly found barriers

Buried options make players believe the game lacks support

Native semantic elements bring assistive-technology behavior with them

A statement must list known failures, not only claim overall compliance

Error messages must be tied to the field through accessibility properties

The haptic channel itself has users with perceptual impairments

Colour-only friend-or-foe identification creates real fairness problems

Permanent, temporary, and situational barriers overlap in need

An accessible alternative may swap how a task is done, never what it accomplishes

After assistive tech takes over, the gesture layer dies

Remapping must cover every actionable key, not only common ones

Private-sector mandates vary sharply by industry and region

Input forgiveness and aim assist need separate strength options

Level AA is the baseline most accessibility laws actually adopt

Law lags new interaction forms, leaving them in a grey zone