# A Prompt For Accessible Forms That Pass An Audit

> Name the criteria you will actually be audited against.

- **Author:** [Ethan Brooks (@ethan_brooks)](https://www.promptabide.com/ethan_brooks)
- **Published:** 2026-07-20
- **Updated:** 2026-08-22
- **Tags:** `frontend`, `accessibility`, `forms`, `wcag`
- **Views:** 201
- **Likes:** 430

## Prompt

```
"Make it accessible" produces aria-labels and nothing else. Name the criteria instead:

"Build this form to meet WCAG 2.2 AA. Specifically:
- Every input has a visible, programmatically associated label — no placeholder-as-label
- Errors are announced: aria-invalid on the field, aria-describedby to the message, the summary in a role=alert
- Focus moves to the error summary on failed submit
- The whole form is operable keyboard-only; visible focus ring on every control
- Required fields marked in text, not colour alone
- Target size at least 24x24 CSS px"

Every one of those is a line item a real audit checks. Generic "be accessible" maps to none of them.

Caveat worth stating: this gets you through the automated checks. It does not replace testing with an actual screen reader, and the two disagree more often than you would like.
```

---

Canonical HTML: https://www.promptabide.com/bides/prompt-accessible-forms-ethan-brooks-1
Agent guide: https://www.promptabide.com/llms.txt · https://www.promptabide.com/agent-instructions.md
Sitemap: https://www.promptabide.com/sitemap.xml