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 as.com — scanned on Feb 20, 2026
Technology4 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.
Headings should follow a logical order (h1 → h2 → h3) without skipping levels.
WCAG 1.3.1<h3> "El Athletic agarra otra tacada" (after h1)Restructure headings to follow sequential order. Don't skip from h1 to h3.
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.
ARIA attributes must be valid and used correctly to work with assistive technologies.
WCAG 4.1.2<section aria-labelledby="b_h_t"> (missing ref)Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.
Here are the most impactful changes as.com should make to improve accessibility:
Add text content, aria-label, or title to all <button> elements.
Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.
Restructure headings to follow sequential order. Don't skip from h1 to h3.
as.com scored 61/100 (grade C) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.
Our scan found 4 accessibility issues on as.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 as.com's compliance status.
See the full issue list above with severity levels, affected elements, and recommended fixes for as.com.
Get a free accessibility report for your website in seconds.