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.
Accessible name does not contain visible label text
moderate1 occurrence
When aria-label differs from visible button/link text, voice-control users cannot activate the element by speaking the text they see on screen.
How to fix: Ensure the aria-label contains the visible text as a substring. Prefer aria-labelledby or descriptive visible text instead.
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