stackoverflow.com Accessibility Report

Accessibility audit of stackoverflow.com — scanned on Feb 20, 2026

Technology
0 /100
D Poor

5 issues found across 2 categories

1 Critical 4 Major

WCAG Compliance Overview

Perceivable 1 issues
Operable 2 issues
Understandable 0 issues
Robust 2 issues

Issues Found

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
1 element(s) affected
  • <a href="#">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Heading levels skip order

Major

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
3 element(s) affected
  • <h5> "Collectives™ on Stack Overflow" (after h3)
  • <h3> "Trouble clicking on a button with selenium in a mo" (after h1)
  • <h4> "Hot Network Questions" (after h1)
How to fix

Restructure headings to follow sequential order. Don't skip from h1 to h3.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
2 element(s) affected
  • id="related-tags"
How to fix

Make each id attribute value unique within the page.

Invalid ARIA attributes

Major

ARIA attributes must be valid and used correctly to work with assistive technologies.

WCAG 4.1.2
49 element(s) affected
  • <div aria-describedby="Tips for searching"> (missing ref)
  • <div aria-labelledby="h-all-questions"> (missing ref)
  • <a aria-labelledby="tag-python-tooltip-container"> (missing ref)
  • <a aria-labelledby="tag-selenium-webdriver-tooltip-container"> (missing ref)
  • <a aria-labelledby="tag-org-mode-tooltip-container"> (missing ref)
How to fix

Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Generic link text

Major

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
2 element(s) affected
  • <a href="https://stackoverflow.co/internal/?utm_medium=referral&utm_s">learn more</a>
  • <a href="https://stackoverflow.co/internal/?utm_medium=referral&utm_s">learn more</a>
How to fix

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Top Priority Fixes

Here are the most impactful changes stackoverflow.com should make to improve accessibility:

  1. #1
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  2. #2
    Invalid ARIA attributes Major

    Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

  3. #3
    Heading levels skip order Major

    Restructure headings to follow sequential order. Don't skip from h1 to h3.

Frequently Asked Questions

Is stackoverflow.com accessible?

stackoverflow.com scored 53/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is stackoverflow.com WCAG compliant?

Our scan found 5 accessibility issues on stackoverflow.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is stackoverflow.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see stackoverflow.com's compliance status.

What accessibility issues does stackoverflow.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for stackoverflow.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing