Skip to content
https://wfu.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
13
7 PASS 2 REVIEW 4 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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, 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 3 pass AA only
title Wake Forest University
1.21:1
#000000
on
#1A1A1A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Top of page
1.91:1
#000000
on
#3D3C3C
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

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 Welcome to Wake For…18.30:13.0:1
#000000
#F3EFE6
Pass
h2 Events18.30:13.0:1
#000000
#F3EFE6
Pass
h2 By the Numbers18.30:13.0:1
#000000
#F3EFE6
Pass
h2 Where to start18.30:13.0:1
#000000
#F3EFE6
Pass
h2 Get to know WFU18.30:13.0:1
#000000
#F3EFE6
Pass
h2 Resources18.30:13.0:1
#000000
#F3EFE6
Pass
h3 Misty Copeland to de…18.30:13.0:1
#000000
#F3EFE6
Pass
h3 Schaack wins NSF CAR…18.30:13.0:1
#000000
#F3EFE6
Pass
h3 Reinventing the (Ham…18.30:13.0:1
#000000
#F3EFE6
Pass
h3 Jazz Ensemble Concer…18.30:13.0:1
#000000
#F3EFE6
Pass
h3 “A Night in Italy…18.30:13.0:1
#000000
#F3EFE6
Pass
h3 Innuendo Spring Conc…18.30:13.0:1
#000000
#F3EFE6
Pass
h3 Why Wake Forest?18.30:13.0:1
#000000
#F3EFE6
Pass
h3 Support Wake Forest18.30:13.0:1
#000000
#F3EFE6
Pass
h3 Wake Forest Giving …18.30:13.0:1
#000000
#F3EFE6
Pass
title Wake Forest Universi…1.21:14.5:1
#000000
#1A1A1A
Fail
span Top of page1.91:14.5:1
#000000
#3D3C3C
Fail
a Skip to main content4.83:14.5:1
#000000
#7C787B
Pass
span Menu5.47:14.5:1
#000000
#858184
Pass
a Admissions6.86:14.5:1
#000000
#979294
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+
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Global navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
25 headings
PASS
25 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 (empty)
  • H1 Wake Forest University
  • H2 Welcome to Wake Forest
  • H2 Wake Up to what’s possible.
  • H2 News
  • H3 Misty Copeland to deliver 2026 Commencement address
  • H3 Schaack wins NSF CAREER Award
  • H3 Reinventing the (Hamster) Wheel
  • H2 Our motto means more.
  • H2 Around Campus
  • H2 Events
  • H3 Jazz Ensemble Concert
  • H3 “A Night in Italy”
  • H3 Innuendo Spring Concert
  • H2 Colleges & Schools
  • H3 Why Wake Forest?
  • H4 Affordability
  • H4 Our Hometown
  • H4 Facts & Figures
  • H2 By the Numbers
  • H2 Where to start
  • H2 Get to know WFU
  • H2 Resources
  • H3 Support Wake Forest
  • H3 Wake Forest Giving Societies

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A
Alt Text Quality
All 29 images OK
PASS
All 29 images OK
Info::
6 image(s) with alt text over 125 characters
Info::
11 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
29 images 12 good alt text 11 decorative
IssueCount
too long6 image(s)
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 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::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search-headertextSearch our site:for/id
inputsubmitSubmit searcharia-label
#search-footertextSearch our site:for/id
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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Wake Forest University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://prod.wp.cdn.aws.wfu.edu/wfu-gutenberg-quarantheme/assets/css/print.css?ver=1776866700
Print Stylesheet ✓ Print Optimized
Print stylesheet https://prod.wp.cdn.aws.wfu.edu/wfu-gutenberg-quarantheme/assets/css/print.css?ver=1776866700 ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 28 passed
PASS
97

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

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
div.wp-block-column > p.has-text-align-center > strong > a div.wp-block-column > p.has-text-align-center > strong > a
div.container > div.wp-block-media-text > figure.wp-block-media-text__media > a div.container > div.wp-block-media-text > figure.wp-block-media-text__media > 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.

○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
●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.
●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.
●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
●Identical links have the same purpose.
○`[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 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 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.
○`[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.
○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