Buttons missing accessible name
CriticalButtons must have discernible text for screen reader users.
WCAG 4.1.22 element(s) affected
<button><button>
How to fix
Add text content, aria-label, or title to all <button> elements.
Accessibility audit of whatsapp.com — scanned on Feb 20, 2026
Social Media3 issues found across 2 categories
Buttons must have discernible text for screen reader users.
WCAG 4.1.2<button><button>Add text content, aria-label, or title to all <button> elements.
Headings should follow a logical order (h1 → h2 → h3) without skipping levels.
WCAG 1.3.1<h5> "Calling" (after h3)<h4> "What we do" (after h2)Restructure headings to follow sequential order. Don't skip from h1 to h3.
ARIA attributes must be valid and used correctly to work with assistive technologies.
WCAG 4.1.2<svg role="image">Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.
Here are the most impactful changes whatsapp.com should make to improve accessibility:
Add text content, aria-label, or title to all <button> elements.
Restructure headings to follow sequential order. Don't skip from h1 to h3.
Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.
whatsapp.com scored 69/100 (grade C) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.
Our scan found 3 accessibility issues on whatsapp.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 whatsapp.com's compliance status.
See the full issue list above with severity levels, affected elements, and recommended fixes for whatsapp.com.
Get a free accessibility report for your website in seconds.