Skip to content
https://virginia.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
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::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
16 landmarks
REVIEW
16 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
5 <nav> landmark(s) found
Warning::
2 of 5 <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 "Utility Links" MAIN (missing!) ASIDE CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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 404 | The University of Virginia ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
h2 Search form
1.59:1
#000000
on
#2D3037
needs 3.0:1 (large text)
24px · above the fold
title The University of Virginia
1.59:1
#000000
on
#212F50
needs 4.5:1 (normal text)
16px · top of page (header area)
aside We use tracking technology to customize …
1.72:1
#000000
on
#1F355A
needs 4.5:1 (normal text)
16px · top of page (header area)
button Accept
1.92:1
#000000
on
#1E3D67
needs 4.5:1 (normal text)
16px · top of page (header area)
button Opt Out
3.25:1
#000000
on
#585E70
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
3.36:1
#000000
on
#5B6072
needs 4.5:1 (normal text)
16px · above the fold
a SIS
3.51:1
#000000
on
#5E6373
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a UVACanvas
3.08:1
#000000
on
#525B6F
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Search form1.59:13.0:1
#000000
#2D3037
Fail
h2 Search form21.00:13.0:1
#000000
#FFFFFF
Pass
h2 UVA Today21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Events21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Innovation21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Research Focus Areas21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Pan-University Insti…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Community21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘Distinguished’ …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 This ‘super dad’…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 New radio telescope …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We Are Wahoos21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Achievement21.00:13.0:1
#000000
#FFFFFF
Pass
title The University of Vi…1.59:14.5:1
#000000
#212F50
Fail
aside We use tracking tech…1.72:14.5:1
#000000
#1F355A
Fail
button Accept1.92:14.5:1
#000000
#1E3D67
Fail
button Opt Out3.25:14.5:1
#000000
#585E70
Fail
a Skip to main content3.36:14.5:1
#000000
#5B6072
Fail
a SIS3.51:14.5:1
#000000
#5E6373
Fail
a UVACanvas3.08:14.5:1
#000000
#525B6F
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 6 failing, 28 passed
REVIEW
88

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mobile-main-nav > ul > li > button.dropdown-toggle div.mobile-main-nav > ul > li > button.dropdown-toggle
div.mobile-main-nav > ul > li > button.dropdown-toggle div.mobile-main-nav > ul > li > button.dropdown-toggle
div.mobile-main-nav > ul > li > button.dropdown-toggle div.mobile-main-nav > ul > li > button.dropdown-toggle

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to main content body.home > a.skip-link

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.

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
LET’S GO div.form > form#redirectForm > button.submit-btn > span

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Scroll to video 2 body.home > section.home > div.video-pagination-dots > div.dot
Scroll to video 3 body.home > section.home > div.video-pagination-dots > div.dot
Scroll to video 4 body.home > section.home > div.video-pagination-dots > div.dot

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.wf-adobecaslonpro-n4-active html.wf-adobecaslonpro-n4-active

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
UVA Students Sing ‘The Good Old Song’ div.vertical-video-container > div.vertical-video-item > div.vertical-video-card > button.vertical-poster-container
Home is Where the Hoos Are div.vertical-video-container > div.vertical-video-item > div.vertical-video-card > button.vertical-poster-container
Students Tour Monticello div.vertical-video-container > div.vertical-video-item > div.vertical-video-card > button.vertical-poster-container
This is Virginia div.vertical-video-container > div.vertical-video-item > div.vertical-video-card > button.vertical-poster-container
○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
●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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` 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
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<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.
○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.
○`[lang]` attributes have a valid value
○`<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
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
A+
Heading Hierarchy
14 headings
PASS
14 headings
Info::
Single H1 present
  • H2 Search form
  • H2 Search form
  • H1 Excellent for a purpose
  • H2 UVA Today
  • H3 ‘Distinguished’ trio celebrated with highest honors of UVA and Monticello
  • H3 This ‘super dad’ has taken an unusual path to UVA women’s basketball coach
  • H2 Events
  • H2 Discovery and Innovation
  • H3 New radio telescope to help UVA astronomers stalk dark matter in deep space
  • H2 Research Focus Areas
  • H2 Pan-University Institutes
  • H2 An Uncommon Community
  • H3 We Are Wahoos
  • H3 Committed to Achievement
A+
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
6 decorative image(s) correctly marked
Info::
16 image(s) with good alt text
24 images 16 good alt text 6 decorative
IssueCount
too long2 image(s)
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 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">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#desktop-search-inputtextSearchfor/id
#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">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback