doi.org Accessibility Report

Accessibility audit of doi.org — 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 1 issues
Robust 0 issues

Issues Found

Page missing language attribute

Critical

The <html> element must have a valid lang attribute to help screen readers pronounce content correctly.

WCAG 3.1.1
1 element(s) affected
  • <html>
How to fix

Add lang attribute to the <html> element, e.g., <html lang="en">.

Page missing title

Major

Each page must have a <title> element to help users understand the page purpose.

WCAG 2.4.2
1 element(s) affected
  • <title>
How to fix

Add a descriptive <title> element inside <head>.

Top Priority Fixes

Here are the most impactful changes doi.org should make to improve accessibility:

  1. #1
    Page missing language attribute Critical

    Add lang attribute to the <html> element, e.g., <html lang="en">.

  2. #2
    Page missing title Major

    Add a descriptive <title> element inside <head>.

Frequently Asked Questions

Is doi.org accessible?

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

Is doi.org WCAG compliant?

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

Is doi.org EAA compliant?

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

What accessibility issues does doi.org have?

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

Scan Your Own Website

Get a free accessibility report for your website in seconds.