Buttons missing accessible name
CriticalButtons must have discernible text for screen reader users.
WCAG 4.1.21 element(s) affected
<button>
How to fix
Add text content, aria-label, or title to all <button> elements.
Accessibility audit of huffpost.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>Add text content, aria-label, or title to all <button> elements.
Element IDs must be unique to ensure correct assistive technology behavior.
WCAG 4.1.1id="Icons/Buttons"id="Path"id="ad-inline-infinite"id="Page-1"id="Fill-1"Make each id attribute value unique within the page.
Here are the most impactful changes huffpost.com should make to improve accessibility:
Add text content, aria-label, or title to all <button> elements.
Make each id attribute value unique within the page.
huffpost.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 huffpost.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 huffpost.com's compliance status.
See the full issue list above with severity levels, affected elements, and recommended fixes for huffpost.com.
Get a free accessibility report for your website in seconds.