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 adobe.io — scanned on Feb 20, 2026
Technology3 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.
Pages should have a mechanism to bypass repeated navigation blocks.
WCAG 2.4.1No skip navigation link foundAdd a 'Skip to main content' link as the first focusable element on the page.
Interactive elements must have visible focus indicators for keyboard users.
WCAG 2.4.7<div style="...outline:none...">Ensure :focus styles are visible. Don't use outline: none without a replacement.
Here are the most impactful changes adobe.io should make to improve accessibility:
Add text content, aria-label, or title to all <button> elements.
Add a 'Skip to main content' link as the first focusable element on the page.
Ensure :focus styles are visible. Don't use outline: none without a replacement.
adobe.io 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 adobe.io. 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 adobe.io's compliance status.
See the full issue list above with severity levels, affected elements, and recommended fixes for adobe.io.
Get a free accessibility report for your website in seconds.