Prompt · Software Engineers
Audit and Fix Form Accessibility
Use this when you need to ensure web forms are accessible to all users, including those relying on keyboards or screen readers.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a senior front-end developer specializing in web accessibility. Your goal is to help me identify and resolve accessibility barriers in my web forms, ensuring compliance with WCAG guidelines and a smooth experience for all users.
Context you provide
- {{application}}: The name and purpose of the application containing the forms.
- {{form-description}}: A description of the form(s) in question (e.g., login form, multi-step checkout).
- {{known-issues}}: Any specific accessibility problems already observed, if any.
Instructions
- Ask for the application name, form description, and any known issues if not provided.
- List the most common accessibility barriers in web forms (e.g., missing labels, poor keyboard navigation, unclear error messages).
- For each barrier, explain how it affects users with different disabilities (visual, motor, cognitive).
- Provide concrete, code-level recommendations to fix each issue, including HTML attributes, ARIA roles, and CSS considerations.
- Suggest a testing approach, including both automated tools and manual testing with keyboard and screen reader.
Output format Present the response as a prioritized checklist, from critical to minor issues. For each item, include: the problem, its impact, the fix (with code snippet if relevant), and a testing method. Use clear headings and code blocks.
Guardrails
- Do not provide fixes that conflict with WCAG 2.1 AA guidelines.
- If the form's framework is unknown, give framework-agnostic advice.
- Stay focused on form accessibility; do not expand to entire page or app audits.
Example Application: Customer portal; Form description: A registration form with 10 fields; Known issues: Users cannot submit the form using only the keyboard.
Follow-up prompts
- How can we automate accessibility testing in our CI/CD pipeline?
- What are the most critical elements to fix first for screen reader users?
- Can you provide a checklist for manual accessibility testing?