washington.edu Accessibility Report

Accessibility audit of washington.edu — scanned on Feb 20, 2026

Technology
0 /100
B Good

2 issues found across 2 categories

1 Critical 1 Major

WCAG Compliance Overview

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

Issues Found

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
8 element(s) affected
  • <button>
  • <button>
  • <button>
  • <button>
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Frames missing title

Major

Iframes must have title attributes describing their content.

WCAG 2.4.1
1 element(s) affected
  • <iframe src="https://www.googletagmanager.com/ns.html?id=GTM-KQ6QQBT">
How to fix

Add descriptive title attributes to all <iframe> elements.

Top Priority Fixes

Here are the most impactful changes washington.edu should make to improve accessibility:

  1. #1
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

  2. #2
    Frames missing title Major

    Add descriptive title attributes to all <iframe> elements.

Frequently Asked Questions

Is washington.edu accessible?

washington.edu scored 77/100 (grade B) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is washington.edu WCAG compliant?

Our scan found 2 accessibility issues on washington.edu. Full WCAG compliance requires addressing all critical and major issues identified above.

Is washington.edu EAA compliant?

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

What accessibility issues does washington.edu have?

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

Scan Your Own Website

Get a free accessibility report for your website in seconds.