Skip to content
https://nau.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #fac01a
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 ModePartial Dark Mode
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
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO (missing!)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Oops, page not found! Custom Styling Navigation Homepage Link Search Form
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: NAU.edu
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name NAU.edu 192×192 icon 512×512 icon Start URL Display Mode standalone
Name NAU.edu Display Mode standalone Theme Color #fac01a Background Color #002454 Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h1 Big ideas on display
1.15:1
#000000
on
#0D1134
needs 3.0:1 (large text)
32px · top of page (header area)
h3 Explore degrees and programs
1.66:1
#000000
on
#48293D
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Big ideas on display1.15:13.0:1
#000000
#0D1134
Fail
h2 Undergraduate Sympos…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 NAU at a glance21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why students choose …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your education made …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Expand your future21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Find your people. Fi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Help elevate NAU21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Discover what's poss…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Learn wherever you a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get in touch21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Explore degrees and …1.66:13.0:1
#000000
#48293D
Fail
h3 How one NAU research…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Putting the kitchen …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Space Farming21.00:13.0:1
#000000
#FFFFFF
Pass
h3 One student. One res…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The effect of wildfi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Honey, life is just …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contact Admissions21.00:13.0:1
#000000
#FFFFFF
Pass

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+
Heading Hierarchy
23 headings
PASS
23 headings
Info::
Single H1 present
  • H1 Big ideas on display
  • H2 Undergraduate Symposium
  • H2 NAU at a glance
  • H3 Explore degrees and programs
  • H2 Why students choose NAU
  • H2 News
  • H3 How one NAU researcher studies wastewater to protect Arizonans’ health
  • H3 Putting the kitchen to the test
  • H3 Space Farming
  • H3 One student. One research project. Three minutes.
  • H3 The effect of wildfires on the water you drink
  • H3 Honey, life is just a classroom
  • H2 Your education made affordable
  • H2 Expand your future
  • H2 Find your people. Find your path.
  • H2 Help elevate NAU
  • H2 Discover what's possible  at NAU!
  • H2 Learn wherever you are
  • H2 Get in touch
  • H3 Contact Admissions
  • H3 Contact Financial Aid
  • H3 Contact University Advising
  • H3 Contact Campus Living
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
8 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
22 images 14 good alt text 8 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputcheckboxEnable vertical scrollingnone
inputcheckboxEnable vertical scrollingnone
inputcheckboxEnable vertical scrollingnone
A
Favicon & Branding
7 icon(s) detected
PASS
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Present
Manifest Icons Present
Multiple Sizes Present
A+
Lighthouse Accessibility Audits
Score 95/100 — 3 failing, 28 passed
PASS
95

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

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.nau-homepage__video-feature-embed-area > figure.wp-block-embed > div.wp-block-embed__wrapper > iframe div.nau-homepage__video-feature-embed-area > figure.wp-block-embed > div.wp-block-embed__wrapper > iframe

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 content div#js-nau-include-header > a#skip-to-content-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.

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
How one NAU researcher studies wastewater to protect Arizonans’ health  div#carousel-scroll-container-i20iah66 > div > div.news-card > a.skip-new-tab-indicator
Putting the kitchen to the test div#carousel-scroll-container-i20iah66 > div > div.news-card > a.skip-new-tab-indicator
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
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Select elements have associated label elements.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
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 buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback