Issues found
Buttons with no accessible name
serious4 occurrences
A button with no text or label is announced only as "button", with no purpose.
How to fix: Add visible text or an aria-label to every <button>.
Form fields without labels
serious3 occurrences
Users cannot tell what to enter in unlabeled inputs.
How to fix: Associate every input with a <label for>, or add aria-label/aria-labelledby.
Interactive elements may be too small to tap accurately
minor1 occurrence
Small tap targets cause accidental activations for users with motor impairments or those using touch screens.
How to fix: Ensure all interactive elements have a minimum size of 24×24 CSS pixels, or provide sufficient spacing. WCAG 2.5.8 minimum is 24px; recommended is 44×44px.
Unlock the full accessibility auditThis is the free summary. The full Pro report groups every check by WCAG principle, samples the exact failing elements, prioritises fixes with code examples, lists what needs manual review, and exports to PDF or HTML.
Get the full report, free, straight to your inboxEvery issue, the affected elements, the exact fixes and a PDF.
We check that the address can receive mail before anything is sent; temporary inboxes are refused. You get one email with your link. No account, no subscription unless you tick the box.
Upgrade to Pro for the full report