Form Labels
SaaSalyst checks whether form inputs on your page have properly associated labels. Missing form labels make your product unusable for screen reader users and fail WCAG compliance.
What SaaSalyst Checks
SaaSalyst scans all form input, select, and textarea elements for associated labels — either via <label for="..."> elements, aria-label attributes, or aria-labelledby references.
Why This Matters
Form labels are a WCAG 2.1 Level A requirement (Success Criterion 1.3.1). Screen readers announce form labels to help visually impaired users understand what each field expects. Without labels, forms are effectively unusable for assistive technology users — and this is one of the most common accessibility lawsuit triggers.
How to Fix It
- Add a <label> element with a matching for attribute for every form input: <label for="email">Email</label><input id="email" type="email">
- For inputs where a visible label is not appropriate, use aria-label: <input type="search" aria-label="Search">
- Avoid using placeholder text as the only label — placeholders disappear when the user starts typing
- Test with a screen reader (VoiceOver on Mac: Cmd+F5) to verify every form field is announced
Frequently Asked Questions
Does SaaSalyst check all forms or just the main page?
SaaSalyst checks all form elements found on the scanned page. If your main page includes a signup form, search input, or contact form, all of those inputs are evaluated for proper label associations.
Are placeholder texts enough for accessibility?
No. SaaSalyst does not count placeholder attributes as sufficient labels. Placeholders disappear when users type, leaving no context for the field's purpose. WCAG requires persistent labels via <label>, aria-label, or aria-labelledby.
Check Your SaaS Now — Free
SaaSalyst scans your website in 30 seconds and checks for Form Labels along with 40+ other business readiness signals.
Scan Your App