Buttons missing accessible name
CriticalButtons must have discernible text for screen reader users.
WCAG 4.1.24 element(s) affected
<button><button><button><button>
How to fix
Add text content, aria-label, or title to all <button> elements.
Accessibility audit of clever.com — scanned on Feb 20, 2026
Technology2 issues found across 2 categories
Buttons must have discernible text for screen reader users.
WCAG 4.1.2<button><button><button><button>Add text content, aria-label, or title to all <button> elements.
Iframes must have title attributes describing their content.
WCAG 2.4.1<iframe src="“https://www.googletagmanager.com/ns.html?id=GTM-NXZFLLD”">Add descriptive title attributes to all <iframe> elements.
Here are the most impactful changes clever.com should make to improve accessibility:
Add text content, aria-label, or title to all <button> elements.
Add descriptive title attributes to all <iframe> elements.
clever.com scored 77/100 (grade B) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.
Our scan found 2 accessibility issues on clever.com. Full WCAG compliance requires addressing all critical and major issues identified above.
The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see clever.com's compliance status.
See the full issue list above with severity levels, affected elements, and recommended fixes for clever.com.
Get a free accessibility report for your website in seconds.