Accessible and intentionally flawed examples

Accessibility Practice Lab

Compare a keyboard-ready, correctly named workflow with a clearly isolated anti-pattern region whose exact defects are safe to detect in tests.

PRACTICE FIXTURE — intentionally built for automation practice

Accessible request form

Every control has a persistent name, focus is visible, and the outcome is announced without moving focus.

No request submitted

Flawed accessibility example

This practice-only region deliberately contains exactly three documented defects. It is not production UI.

Intentional anti-pattern
Email address

Deliberately low-contrast helper text for an assertion exercise.

Passing examples

Start with observable behavior

These snippets match executable tests stored inexamples/playwright-ts/.