Skip to content
https://insidehighered.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
Heading Hierarchy
Action
57 headings, 13 skip(s)
FIX
57 headings, 13 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Tenn. Passes ‘Charlie Kirk Act’ Defending Campus Speakers From Disruption
  • H5 DOJ Extends Web Accessibility Deadline skipped
  • H5 Impact of New Grad Loan Caps on Institutions and Programs in 5 Charts
  • H5 States Grapple With Effects of OBBBA Cuts on Higher Ed
  • H5 The Myriad Complex Ways Young People Use AI
  • H5 Faculty Defect From Texas Publics, Citing Censorship Concerns
  • H2 Quick Takes
  • H5 Tenn. Bill Overhauling Tenured Faculty Disciplinary Procedures Becomes Law skipped
  • H5 Appeals Court Reinstates Indiana Ban on Student IDs for Voting
  • H5 Kentucky General Assembly Mostly Restores Higher Ed Funding
  • H2 Opinion
  • H3 Views
  • H5 3-Year Degrees Misread the Future Job Market skipped
  • H5 Can Diversity and Meritocracy Coexist?
  • H3 Columns
  • H5 Featured Gig: Executive Director, Online Education & AI Innovation, Manchester U skipped
  • H5 Tyranny at Texas Tech
  • H3 Career Advice
  • H5 How Good Is Your Advancement Team? skipped
  • H5 What We Learned From Supporting Fired Federal Workers
  • H2 Deep Dives
  • H5 The War on Student Speech skipped
  • H5 Presidents Puzzled on Rebuilding Public Trust in Higher Ed
  • H5 Presidents Pressured in Trump’s Second Term
  • H2 Resources
  • H4 Peer-to-Peer Advice skipped
  • H4 Events & Webinars
  • H4 Data & Analysis
  • H4 Membership
  • H3 The Key Podcast
  • H5 Ep. 194: In Defense of a Core Education With Andrew Delbanco skipped
  • H5 Ep. 193: 3 Big Trends in Student Success
  • H3 Campus
  • H5 Where Research Meets Enterprise: Lessons From a Successful Spin-Out Founder skipped
  • H5 How to Maximize Relationships Between University Academic and Professional Services Staff
  • H2 Editors’ Picks
  • H5 College Students Are More Polarized Than Ever. Can AI Help? skipped
  • H5 Experts: New Accreditation Rules Threaten Academic Freedom
  • H5 In Admissions Data Legal Fight, Colleges Want Protection From Punishment
  • H2 Student Voice: Amplified
  • H3 ‘A Foot in the Door’
  • H3 The Experience Imperative
  • H5 The Other Engagement Problem skipped
  • H5 Student Mental Health Challenges Persist
  • H5 Who Feels Welcome on Campus?
  • H5 The Costs Students Don’t See Coming—and Why They Matter
  • H5 Students on Academic Quality, Success
  • H5 How AI Is Changing—Not ‘Killing’—College
  • H5 Decoding Student Trust
  • H2 Sign up for Newsletters
  • H2 More to Explore
  • H4 Company skipped
  • H4 Legal
  • H4 Newsletter
  • H2 Sign up for Newsletters
  • H5 Sign up for a free account or log in. skipped
  • H4 Register to continue reading

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

D
Form Accessibility
Action
4 of 22 controls have issues
FIX
4 of 22 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="op" id="edit-submit">; <input type="submit" name="op" id="edit-submit--2">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email_address" id="edit-email-address">; <input type="email" name="email_address" id="edit-email-address--2">
Info::
18 control(s) properly labeled
22 controls
18 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#edit-group-6059d596b6checkboxDaily News Updatefor/id
#edit-group-7451d44576checkboxWeekly News Updatefor/id
#edit-group-0460c9abc8checkboxAdmissions Weekly Updatefor/id
#edit-group-ea0f10cedecheckboxDiversity Weekly Updatefor/id
#edit-group-716bc5b6b6checkboxStudent Successfor/id
#edit-group-dcbb3d1a6ccheckboxCareer Advicefor/id
#edit-group-allcheckboxAll Newslettersfor/id
#edit-job-titletextJob Titlefor/id
#edit-urlihetextLeave this field blankfor/id
#edit-group-6059d596b6--2checkboxDaily News Updatefor/id
#edit-group-7451d44576--2checkboxWeekly News Updatefor/id
#edit-group-0460c9abc8--2checkboxAdmissions Weekly Updatefor/id
#edit-group-ea0f10cede--2checkboxDiversity Weekly Updatefor/id
#edit-group-716bc5b6b6--2checkboxStudent Successfor/id
#edit-group-dcbb3d1a6c--2checkboxCareer Advicefor/id
#edit-group-all--2checkboxAll Newslettersfor/id
#edit-job-title--2textJob Titlefor/id
#edit-urlihe--2textLeave this field blankfor/id
#edit-email-address--2email(Email Address)placeholder only
#edit-email-addressemail(Email Address)placeholder only
#edit-submit--2submit(none)none
#edit-submitsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" name="op" id="edit-submit">; <input type="submit" name="op" id="edit-submit--2">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="email" name="email_address" id="edit-email-address">; <input type="email" name="email_address" id="edit-email-address--2">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found | Inside Higher Ed ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA
h2 Sign up for Newsletters
1.07:1
#000000
on
#0C0C0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sign up for Newsletters
1.07:1
#000000
on
#0C0C0C
needs 3.0:1 (large text)
24px · bottom of viewport
title Inside Higher Ed | Higher Education News…
2.03:1
#000000
on
#404040
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.02:1
#000000
on
#020308
needs 4.5:1 (normal text)
16px · top of page (header area)
a Advertisement
1.04:1
#000000
on
#050609
needs 4.5:1 (normal text)
16px · top of page (header area)
a Search
1.07:1
#000000
on
#0B0B0B
needs 4.5:1 (normal text)
16px · top of page (header area)
button Register
1.07:1
#000000
on
#0B0B0B
needs 4.5:1 (normal text)
16px · above the fold
button Log In
1.82:1
#000000
on
#393939
needs 4.5:1 (normal text)
16px · above the fold
a Search
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · above the fold
span Register
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · above the fold
span Log In
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · above the fold
a Become a Member
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · above the fold
a Find A Job
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · above the fold
span Solutions
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · above the fold
a Institutional Subscriptions
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · above the fold
a Advertising & Marketing
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · mid-page
a Consulting Services
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · mid-page
a Data & Insights
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · mid-page
a Hiring & Jobs
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · mid-page
a Event Partnerships
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Sign up for Newslett…1.07:13.0:1
#000000
#0C0C0C
Fail
h2 Sign up for Newslett…1.07:13.0:1
#000000
#0C0C0C
Fail
title Inside Higher Ed | H…2.03:14.5:1
#000000
#404040
Fail
a Skip to main content1.02:14.5:1
#000000
#020308
Fail
a Advertisement1.04:14.5:1
#000000
#050609
Fail
a Search1.07:14.5:1
#000000
#0B0B0B
Fail
button Register1.07:14.5:1
#000000
#0B0B0B
Fail
button Log In1.82:14.5:1
#000000
#393939
Fail
a Search1.79:14.5:1
#000000
#383838
Fail
span Register1.79:14.5:1
#000000
#383838
Fail
span Log In1.79:14.5:1
#000000
#383838
Fail
a Become a Member1.79:14.5:1
#000000
#383838
Fail
a Find A Job1.79:14.5:1
#000000
#383838
Fail
span Solutions1.79:14.5:1
#000000
#383838
Fail
a Institutional Subscr…1.79:14.5:1
#000000
#383838
Fail
a Advertising & Market…1.79:14.5:1
#000000
#383838
Fail
a Consulting Services1.79:14.5:1
#000000
#383838
Fail
a Data & Insights1.79:14.5:1
#000000
#383838
Fail
a Hiring & Jobs1.79:14.5:1
#000000
#383838
Fail
a Event Partnerships1.79:14.5:1
#000000
#383838
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A
Alt Text Quality
All 41 images OK
PASS
All 41 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
38 image(s) with good alt text
41 images 38 good alt text
IssueCount
too long3 image(s)
A
Lighthouse Accessibility Audits
Score 91/100 — 4 failing, 31 passed
PASS
91

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Consent div#CybotCookiebotDialogNav > ul#CybotCookiebotDialogNavList > li.CybotCookiebotDialogNavItem > a#CybotCookiebotDialogNavDeclaration
PRIVACY POLICY div#CybotCookiebotDialogBodyContentText > p > a > span
TERMS OF USE div#CybotCookiebotDialogBodyContentText > p > a > span
Advertisement div#block-ihe-dfptagtakeover-billboard > div.flex > div.block > a
Lawmakers in multiple states named bills after Turning Point USA’s controversia… div.grid-column-1 > div.ihe-card > div.content-field_lead > p
Advertisement div.paragraph > div.flex > div.block > a
Advertisement div.paragraph > div.flex > div.block > a
Advertisement div.paragraph > div.flex > div.block > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
DOJ Extends Web Accessibility Deadline div.hero-article-main > div.ihe-card > div.ihe-card--title > h5.featured-story-title
Tenn. Bill Overhauling Tenured Faculty Disciplinary Procedures Becomes Law div.swiper-slide > article.card-thumbnail > div.card-body > h5
3-Year Degrees Misread the Future Job Market div#swiper-wrapper-55bbe2ffd91f0321 > div.article-list-item-first > div.article-list-item > h5
Featured Gig: Executive Director, Online Education & AI Innovation, Manchester U div#swiper-wrapper-2029e2edacb210efc > div.article-list-item-first > div.article-list-item > h5
How Good Is Your Advancement Team? div#swiper-wrapper-05559cf10f7d109238 > div.article-list-item-first > div.article-list-item > h5
The War on Student Speech div.swiper-slide > article.card-thumbnail > div.card-body > h5
Peer-to-Peer Advice div.swiper-slide > div.paragraph > div.card-teaser-summary > h4
Ep. 194: In Defense of a Core Education With Andrew Delbanco div.item-list > ul > li > h5.views-field
Where Research Meets Enterprise: Lessons From a Successful Spin-Out Founder div.item-list > ul > li > h5.views-field
College Students Are More Polarized Than Ever. Can AI Help? div.swiper-slide > article.card-thumbnail > div.card-body > h5
The Other Engagement Problem div.collection-container > div.article-list-with-image > div > h5
Company div.footer-inner-wrapper > div#footer-top > div.menu-links-company > h4.heading-line

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
A photograph of the Tennessee State Capitol on a sunny, nearly cloudless day. div#swiper-wrapper-89b6a954755f2ded > div.swiper-slide > article.card-thumbnail > a
Privacy screens for voting div#swiper-wrapper-89b6a954755f2ded > div.swiper-slide > article.card-thumbnail > a
A photo illustration of orange hands reaching from outside of the frame to cove… div#swiper-wrapper-d110cfbe1ef3e56410 > div.swiper-slide > article.card-thumbnail > a
A photo illustration of a group of people around a table putting together a puz… div#swiper-wrapper-d110cfbe1ef3e56410 > div.swiper-slide > article.card-thumbnail > a
A photo illustration of a robot, representing AI, with smoke coming out of the … div#swiper-wrapper-e2ed2e7fdd45e4ed > div.swiper-slide > article.card-thumbnail > a
A photo illustration of the U.S. Capitol casting a shadow. div#swiper-wrapper-e2ed2e7fdd45e4ed > div.swiper-slide > article.card-thumbnail > a
A student with a beard writes on a clipboard div.collection-teaser > div.collection-container > div.article-list-with-image > a
Two students talk to one another in a larger group setting div.collection-teaser > div.collection-container > div.article-list-with-image > a
Two male students walk on a pathway through a quad on a college campus. div.collection-teaser > div.collection-container > div.article-list-with-image > a
A mason jar stuffed full of money with a "college" label on it. div.collection-teaser > div.collection-container > div.article-list-with-image > a
Students smile during college graduation. div.collection-teaser > div.collection-container > div.article-list-with-image > a
A student using AI on a cellphone at a desk covered in study materials. div.collection-teaser > div.collection-container > div.article-list-with-image > a
Close-up of a teacher shaking hands with student at graduation. div.collection-teaser > div.collection-container > div.article-list-with-image > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search Register Login nav.header-main-nav > div#block-responsivemenumobileicon > div#pelcro-register > ul.flex

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback