Issues found
Buttons with no accessible name
serious1 occurrence
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
serious1 occurrence
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.
Page title is very short or very long
minor1 occurrence
Titles that are too short are uninformative; overly long titles are truncated in tabs and search results.
How to fix: Aim for a concise, descriptive title (roughly 4–70 characters).
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 exact fixes, and your PDF download link.
Upgrade to Pro for the full report