Skip to content
https://auburn.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
3
REVIEW
5
PASS
5
INFO
0
Checks
13
5 PASS 5 REVIEW 3 FIX
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
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::
Search form present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Close the navigation modal Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
10 icon(s) detected
REVIEW
10 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::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Navigation UX
Action
3 navigation pattern(s)
REVIEW
3 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA 2 pass AA only
h1 Auburn University homepage
1.33:1
#000000
on
#0B2341
needs 3.0:1 (large text)
32px · bottom of viewport
h2 About Auburn
1.33:1
#000000
on
#0B2341
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore Auburn
1.33:1
#000000
on
#0B2341
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Auburn Stories
1.33:1
#000000
on
#0B2341
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connect with Us
1.33:1
#000000
on
#0B2341
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Events
1.33:1
#000000
on
#0B2341
needs 3.0:1 (large text)
24px · bottom of viewport
title Auburn University Homepage | Auburn Univ…
1.59:1
#000000
on
#362F27
needs 4.5:1 (normal text)
16px · top of page (header area)
p Cookie Acknowledgement
2.10:1
#000000
on
#4A4136
needs 4.5:1 (normal text)
16px · top of page (header area)
p This website uses cookies to collect inf…
2.79:1
#000000
on
#605245
needs 4.5:1 (normal text)
16px · top of page (header area)
a Privacy Statement
4.00:1
#000000
on
#776A5D
needs 4.5:1 (normal text)
16px · top of page (header area)
p for more information.
4.05:1
#000000
on
#7B6A5A
needs 4.5:1 (normal text)
16px · above the fold
span I Understand
4.49:1
#000000
on
#86705D
needs 4.5:1 (normal text)
16px · above the fold
a Auburn
1.75:1
#000000
on
#423426
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Current Students
1.31:1
#000000
on
#2C1E19
needs 4.5:1 (normal text)
16px · above the fold
a Faculty and Staff
2.68:1
#000000
on
#684C36
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Parents and Families
1.41:1
#000000
on
#392215
needs 4.5:1 (normal text)
16px · mid-page

2 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
h1 Auburn University ho…1.33:13.0:1
#000000
#0B2341
Fail
h2 About Auburn1.33:13.0:1
#000000
#0B2341
Fail
h2 Explore Auburn1.33:13.0:1
#000000
#0B2341
Fail
h2 Auburn Stories1.33:13.0:1
#000000
#0B2341
Fail
h2 Connect with Us1.33:13.0:1
#000000
#0B2341
Fail
h2 Events1.33:13.0:1
#000000
#0B2341
Fail
title Auburn University Ho…1.59:14.5:1
#000000
#362F27
Fail
p Cookie Acknowledgeme…2.10:14.5:1
#000000
#4A4136
Fail
p This website uses co…2.79:14.5:1
#000000
#605245
Fail
a Privacy Statement4.00:14.5:1
#000000
#776A5D
Fail
p for more information…4.05:14.5:1
#000000
#7B6A5A
Fail
span I Understand4.49:14.5:1
#000000
#86705D
Fail
a Skip to Primary Navi…6.81:14.5:1
#000000
#A58F7A
Pass
a Skip to Content6.37:14.5:1
#000000
#A38971
Pass
a Auburn1.75:14.5:1
#000000
#423426
Fail
button Info for7.45:14.5:1
#000000
#B1957A
Pass
a Prospective Students7.37:14.5:1
#000000
#A89686
Pass
a Current Students1.31:14.5:1
#000000
#2C1E19
Fail
a Faculty and Staff2.68:14.5:1
#000000
#684C36
Fail
a Parents and Families1.41:14.5:1
#000000
#392215
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
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation shortcuts" SEARCH MAIN ASIDE "gdprtitle" 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+
Heading Hierarchy
6 headings
PASS
6 headings
Info::
Single H1 present
  • H1 Auburn University homepage
  • H2 About Auburn
  • H2 Explore Auburn
  • H2 Auburn Stories
  • H2 Connect with Us
  • H2 Events
A+
Alt Text Quality
All 73 images OK
PASS
All 73 images OK
Info::
10 decorative image(s) correctly marked
Info::
63 image(s) with good alt text
73 images 63 good alt text 10 decorative
All images have appropriate alt text.
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">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
qtextAuburn University Searcharia-label
inputsubmit(none)none

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

<input type="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

A+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 27 passed
PASS
100

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.

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
`[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.
`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
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 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
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[accesskey]` values are unique
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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
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
`<frame>` or `<iframe>` elements have a title
`<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
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.
`[lang]` attributes have a valid value
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.
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