You build the form. We make it accessible.
Ever spent hours coding a perfect signup form, only to realize screen readers can't understand it? Yeah, that's frustrating.
Forms are everywhere - logins, checkouts, contact pages, surveys. But most forms are accessibility nightmares:
- Inputs without proper labels
- Buttons that just say "Submit" (submit what?)
- Error messages that aren't linked to the fields
- Required fields with no indication they're required
People using screen readers? They're guessing. That's not okay.
cm-forms is like Black for HTML forms. Point it at your HTML files, and it automatically adds the accessibility attributes everyone needs.
cm-forms .🔍 Analyzing 5 HTML files...
Found 3 forms with 12 inputs
✓ Auto-fixed:
• Added aria-required to 8 required fields
• Linked 3 error messages with aria-describedby
• Connected 12 labels to their inputs
⚠ Needs your input:
Button on line 45 says "Submit" - that's vague!
Suggest: "Create account" or "Sign up" ?
✓ Modified 23 elements across 3 files
✓ Your forms are now more accessible!
That's it. Seriously.
- Finds all forms in your HTML files
- Adds ARIA labels, roles, and required attributes automatically
- Asks you when things are ambiguous (we can't read your mind!)
- Explains what changed and why
- Makes your forms work for everyone
Think of it as a helpful friend who knows WCAG guidelines and saves you hours of tedious work.
🔬 Research Phase
We're figuring out the best way to build this. What we're exploring:
- Which fixes are always safe to auto-apply
- When we should ask instead of assuming
- How to explain accessibility without overwhelming people
- What forms need most in real projects
We need people to research and document what makes forms accessible. Not theory - practical stuff.
What we're looking for:
- Best practices: What should every form have? (real examples, not just "add labels")
- Risk areas: When could auto-fixing break things or make wrong assumptions?
- Edge cases: Multi-step forms, dynamic forms, custom controls - what's tricky?
- Testing insights: How do screen reader users actually interact with forms?
- Pattern library: What are the correct ARIA patterns for different form types?
How to contribute:
Dive into HTML form accessibility. Read the specs, test with screen readers, find real broken forms and document what they need. Write it in plain language.
Check out our research wiki to see how to submit your findings. No expertise required - if you can spot a problem and explain how to fix it, that helps.
GitHub issues, wiki edits, random notes in a text file - all welcome.
Forms are everywhere. Login pages, checkouts, contact forms, surveys. When they're not accessible, people get locked out of important things.
Good news: form accessibility has clear patterns. Bad news: doing it manually is tedious and easy to mess up.
Let's automate the tedious parts.
cm-forms is part of the comfort mode toolkit – tools that make the web more comfortable for everyone.
Simple tools for accessible web. No expertise required.