Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 4 REVIEW 3 FIX

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #041e42

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

4 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

404 Error Page

HTTP 404, bare page

REVIEW

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Page Not Found | University of Nevada, Reno ✓Custom Styling ✗Navigation ✓Homepage Link ✓Search Form ✓

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: UNR

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name UNR ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name UNR Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 3 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA

a skip to main content

1.27:1

#000000

#041E42

needs 4.5:1 (normal text)

16px · top of page (header area)

a News

1.27:1

#000000

#041E42

needs 4.5:1 (normal text)

16px · top of page (header area)

a MyNevada

1.27:1

#000000

#041E42

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 University of Nevada…	8.93:1	3.0:1	#000000	#9DB07C	Pass
h1 University of Nevada…	8.93:1	3.0:1	#000000	#9DB07C	Pass
h2 Quicklinks	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Search	8.93:1	3.0:1	#000000	#9DB07C	Pass
h2 Find your path	8.93:1	3.0:1	#000000	#9DB07C	Pass
h2 Academics	8.93:1	3.0:1	#000000	#9DB07C	Pass
h2 Why choose Nevada?	8.93:1	3.0:1	#000000	#9DB07C	Pass
h2 Step onto campus and…	8.93:1	3.0:1	#000000	#9DB07C	Pass
h2 Academic excellence …	8.93:1	3.0:1	#000000	#9DB07C	Pass
h2 Admissions and finan…	8.93:1	3.0:1	#000000	#9DB07C	Pass
h2 Answer the call	8.93:1	3.0:1	#000000	#9DB07C	Pass
h3 A top-ranked educati…	8.93:1	3.0:1	#000000	#9DB07C	Pass
h3 A place to do awesom…	8.93:1	3.0:1	#000000	#9DB07C	Pass
h3 Big school — tight…	8.93:1	3.0:1	#000000	#9DB07C	Pass
h3 Transformative resea…	8.93:1	3.0:1	#000000	#9DB07C	Pass
title University of Nevada…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a skip to main content	1.27:1	4.5:1	#000000	#041E42	Fail
a News	1.27:1	4.5:1	#000000	#041E42	Fail
a MyNevada	1.27:1	4.5:1	#000000	#041E42	Fail
button Quicklinks	8.43:1	4.5:1	#000000	#9BA5B3	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

10 landmarks

PASS

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

Heading Hierarchy

15 headings

PASS

15 headings

Multiple H1 headings (2 found)

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

H2 Quicklinks
H2 Search
H1 University of Nevada, Reno
H1 University of Nevada, Reno duplicate H1
H2 Find your path
H2 Academics
H2 Why choose Nevada?
H3 A top-ranked education
H3 A place to do awesome things
H3 Big school — tight-knit community
H3 Transformative research access
H2 Step onto campus and into the Pack
H2 Academic excellence meets alpine adventure
H2 Admissions and financial aid
H2 Answer the call

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

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

5 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

6 image(s) with good alt text

12 images 6 good alt text 1 decorative

Issue	Count
too long	5 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#site-search	search	Search www.unr.edu	for/id

A+

Link & Button Quality

82 links, 7 buttons — all OK

PASS

82 links, 7 buttons — all OK

82 link(s) with descriptive text

82 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

89 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 28 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.

●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

●`<frame>` or `<iframe>` elements have a title

●`<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

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[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

○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

○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.

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