forms

# Forms Accessibility Skill > **Canonical source**: `examples/FORMS_ACCESSIBILITY_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md` > This skill is derived from that file. When in doubt, the example is authoritative. Apply these rules when implementing or reviewing any form, input, or validation flow. **Only load this skill if the project contains forms.** --- ## Core Mandate Forms must be understandable and operable with keyboards, touch, speech input, screen readers, screen magnification, browser autofill, password managers, and other assistive technologies. Requirements apply to initial entry, validation, recovery, review, submission, and authentication. Users must be able to complete time-limited forms when a time limit is not essential, and complete the form at 200%/400% zoom without losing content or functionality. Prefer native HTML controls. Build a custom widget only when native controls cannot meet the documented requirement, and implement the applicable keyboard, focus, name, role, state, and value behaviour. --- ## Severity Scale (this skill) | Level | Meaning | | --- | --- | | **Critical** | Blocks task completion entirely for one or more disability groups | | **Serious** | Significantly impairs access; workaround unreasonable to expect | | **Moderate** | Creates friction; workaround exists and is not too burdensome | | **Minor** | Best-practice gap; marginal impact on access | Do not assign severity from the violated rule alone — determine it from the ...