Skip to content
https://ncsu.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 REVIEW 3 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name 192×192 icon 512×512 icon Start URL Display Mode
Icons 2 icon(s)
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.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <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
Heading Hierarchy
Action
36 headings, 2 skip(s)
REVIEW
36 headings, 2 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 About
  • H2 Admissions
  • H3 Life at NC State
  • H3 Apply Now
  • H2 Academics
  • H2 Innovation
  • H2 Community
  • H1 Fashion Week Takeover
  • H6 A Joyous Return to Earth skipped
  • H3 Jesse Eisenberg to Headline 2026 Human Factor Series
  • H3 Lenovo Investment Advances Esports
  • H2 More From NC State
  • H6 Golfer Marie Eline Madsen Builds off Dynamite Freshman Season skipped
  • H6 Grad Programs Climb Atop the Rankings
  • H6 Discover Design Studies
  • H6 Eighth Day of Giving Makes Its Mark
  • H2 Think and Do With Us
  • H2 Top 50 University in the United States
  • H2 Top 10 Best Value Among U.S. Public Universities
  • H2 See Yourself Here
  • H2 We Solve Problems
  • H3 Results
  • H3 Celebrate Earth Month
  • H2 Upcoming Events
  • H3 Sexual Assault Awareness Month Denim Installation
  • H3 Emerging Designers Textile Showcase
  • H3 Celebration of Sustainability
  • H3 Sustainability Showcase
  • H3 A Creek in Carolina: Artworks by Bobby C. Martin
  • H2 Campus Map
  • H2 Connect With Us
  • H1 Find NC State websites, locations and people duplicate H1
  • H2 MyPack Portal
  • H2 University Libraries
  • H2 Academic Calendar
  • H2 Majors and Careers

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

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
h1 Fashion Week Takeover
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Find NC State websites, locations and pe…
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 About
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Admissions
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Academics
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Innovation
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Community
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More From NC State
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Think and Do With Us
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Top 50 University in the United States
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Top 10 Best Value Among U.S. Public Univ…
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 See Yourself Here
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 We Solve Problems
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Upcoming Events
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Campus Map
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connect With Us
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 MyPack Portal
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 University Libraries
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Academic Calendar
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Majors and Careers
2.35:1
#000000
on
#990000
needs 3.0:1 (large text)
24px · bottom of viewport

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
h1 Fashion Week Takeove…2.35:13.0:1
#000000
#990000
Fail
h1 Find NC State websit…2.35:13.0:1
#000000
#990000
Fail
h2 About2.35:13.0:1
#000000
#990000
Fail
h2 Admissions2.35:13.0:1
#000000
#990000
Fail
h2 Academics2.35:13.0:1
#000000
#990000
Fail
h2 Innovation2.35:13.0:1
#000000
#990000
Fail
h2 Community2.35:13.0:1
#000000
#990000
Fail
h2 More From NC State2.35:13.0:1
#000000
#990000
Fail
h2 Think and Do With Us2.35:13.0:1
#000000
#990000
Fail
h2 Top 50 University in…2.35:13.0:1
#000000
#990000
Fail
h2 Top 10 Best Value Am…2.35:13.0:1
#000000
#990000
Fail
h2 See Yourself Here2.35:13.0:1
#000000
#990000
Fail
h2 We Solve Problems2.35:13.0:1
#000000
#990000
Fail
h2 Upcoming Events2.35:13.0:1
#000000
#990000
Fail
h2 Campus Map2.35:13.0:1
#000000
#990000
Fail
h2 Connect With Us2.35:13.0:1
#000000
#990000
Fail
h2 MyPack Portal2.35:13.0:1
#000000
#990000
Fail
h2 University Libraries2.35:13.0:1
#000000
#990000
Fail
h2 Academic Calendar2.35:13.0:1
#000000
#990000
Fail
h2 Majors and Careers2.35:13.0:1
#000000
#990000
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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) 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 18 images OK
PASS
All 18 images OK
Info::
5 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
18 images 11 good alt text 2 decorative
IssueCount
too long5 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#navcheckcheckboxMenufor/id
#querytextSearch all of ncsu.edufor/id
A
Favicon & Branding
6 icon(s) detected
PASS
6 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+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://www.ncsu.edu/wp-content/themes/ncstate-theme-v4/dist/styles/print.css?ver=4.15.1
Print Stylesheet Print Optimized
Print stylesheet https://www.ncsu.edu/wp-content/themes/ncstate-theme-v4/dist/styles/print.css?ver=4.15.1 Inline @media print Not detected
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 26 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.

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
A Joyous Return to Earth div.wp-block-ncst-spotlight-image > figure.spotlight__image > div.content > h6
Golfer Marie Eline Madsen Builds off Dynamite Freshman Season div.ncst-curated-news-list__container > div.wp-block-ncst-curated-news > div.curated-news__content > h6

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
🐺📍➡️ Swipe to see how you made your mark, Wolfpack. Your 18,028 gifts totaled $… div#sbi_18082935728359067 > div.sbi_inner_wrap > div.sbi_photo_wrap > a.sbi_photo
Ready, set, SEARCH. 🐺🔍 There are FIVE stuffed Wufs hidden across campus (main a… div#sbi_18065938292324268 > div.sbi_inner_wrap > div.sbi_photo_wrap > a.sbi_photo
Where will YOU make your mark today? 📍 On Day of Giving, every gift is a way to… div#sbi_17904540792219805 > div.sbi_inner_wrap > div.sbi_photo_wrap > a.sbi_photo
These students won free $$$ to support their favorite areas of NC State‼️ YOU c… div#sbi_18175961164386092 > div.sbi_inner_wrap > div.sbi_photo_wrap > a.sbi_photo

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
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
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.
Skip links are focusable.
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 buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
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.
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