Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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: #6b7178

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.

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

6 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 6 <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, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | Directories | UNLV ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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

h2 Find

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We Are Rebels

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Admission Resources

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Innovative Academics

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A Worldwide Destination

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Hieu Nguyen Quote

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Campus Life

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to be a Rebel?

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Personal Data and Cookies

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Quick Links

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 From the President

2.18:1

#000000

#37474F

needs 3.0:1 (large text)

19px · bottom of viewport

title University of Nevada, Las Vegas | UNLV

2.88:1

#000000

#53575B

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

3.04:1

#000000

#AD2323

needs 4.5:1 (normal text)

16px · top of page (header area)

a University of Nevada, Las Vegas

1.40:1

#000000

#4C1212

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Students

1.10:1

#000000

#0F0F0F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Faculty/Staff

1.11:1

#000000

#101014

needs 4.5:1 (normal text)

16px · above the fold

a Alumni

1.10:1

#000000

#100F15

needs 4.5:1 (normal text)

16px · above the fold

a Donors

1.10:1

#000000

#101010

needs 4.5:1 (normal text)

16px · above the fold

a Audiences

1.10:1

#000000

#120E19

needs 4.5:1 (normal text)

16px · above the fold

a Students

1.17:1

#000000

#16103C

needs 4.5:1 (normal text)

16px · above the fold

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)

Element	Ratio	Required	FG	BG	Result
h2 Find	2.18:1	3.0:1	#000000	#37474F	Fail
h2 We Are Rebels	2.18:1	3.0:1	#000000	#37474F	Fail
h2 Admission Resources	2.18:1	3.0:1	#000000	#37474F	Fail
h2 Innovative Academics	2.18:1	3.0:1	#000000	#37474F	Fail
h2 A Worldwide Destina…	2.18:1	3.0:1	#000000	#37474F	Fail
h2 Hieu Nguyen Quote	2.18:1	3.0:1	#000000	#37474F	Fail
h2 Campus Life	2.18:1	3.0:1	#000000	#37474F	Fail
h2 Ready to be a Rebel?	2.18:1	3.0:1	#000000	#37474F	Fail
h2 Personal Data and Co…	2.18:1	3.0:1	#000000	#37474F	Fail
h3 Quick Links	2.18:1	3.0:1	#000000	#37474F	Fail
h3 From the President	2.18:1	3.0:1	#000000	#37474F	Fail
title University of Nevada…	2.88:1	4.5:1	#000000	#53575B	Fail
a Skip to main content	3.04:1	4.5:1	#000000	#AD2323	Fail
a University of Nevada…	1.40:1	4.5:1	#000000	#4C1212	Fail
a Students	1.10:1	4.5:1	#000000	#0F0F0F	Fail
a Faculty/Staff	1.11:1	4.5:1	#000000	#101014	Fail
a Alumni	1.10:1	4.5:1	#000000	#100F15	Fail
a Donors	1.10:1	4.5:1	#000000	#101010	Fail
a Audiences	1.10:1	4.5:1	#000000	#120E19	Fail
a Students	1.17:1	4.5:1	#000000	#16103C	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.

Landmark Structure

17 landmarks

PASS

17 landmarks

<main> landmark present

6 <nav> landmark(s) found

4 of 6 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

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

12 headings

PASS

12 headings

Single H1 present

H1 University of Nevada, Las Vegas
H2 Find
H3 Quick Links
H2 We Are Rebels
H2 Admission Resources
H2 Innovative Academics
H3 From the President
H2 A Worldwide Destination
H2 Hieu Nguyen Quote
H2 Campus Life
H2 Ready to be a Rebel?
H2 Personal Data and Cookies

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

7 images 7 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#gsc-i-id1	text	search	aria-label
#edit-combine	text	Search Degrees	none

Link & Button Quality

1 issue(s) across 95 links and 6 buttons

PASS

1 issue(s) across 95 links and 6 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

94 link(s) with descriptive text

95 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label

100 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /sites/default/files/css/css_oIm3ENHFMouEHYCJJf5ICidn4N0VTxGC_cctbujHBSc.css?delta=12&language=en&theme=mars&include=eJx9UlF2hDAIvJDdHCkPE7TUJFhIdrs9fVG3u75X64-OMDIwADFWhnJ38ACXQbjUDlSxeiofGCqLC6oXCIElEhc9zMZMxfMVRSjiISVAwhJBDnPME6EPVh2P5de-vBXwA0s-VxoT95CMGJp6rVBRvWAVHuiw9pNvCnBD5Yy-zXH574SeSQOmBAXZZE6IHMTkM0aCav6dUWch60HrPZ1KC9r41utqemVOPYj_NmrEL_v2LDRSMeIVUsOjQpljS7ja-J-LMtBReGmOvjH6QBJaMuHPxvVQ5Ib9sqyuZ65aBWY3CGS8sUxdmMwPI65Nl9onDpPb4e7js6HcfSP_vDz3RLvssqaZrJy4F9znCRKPbnvt4hV6dcujm2wIdutzj99-b6zLIOqW69ANblt4W50o4xazzWnuZhAYbdB3dVHaDOnyilxamVufSN8xdnrXitn1oNi1kq6Pmiv2M4zo1XxcrkXQrKPNU87ZZn_Y6l-2_on8AGBah9U

Print Stylesheet ✓ Print Optimized

Print stylesheet /sites/default/files/css/css_oIm3ENHFMouEHYCJJf5ICidn4N0VTxGC_cctbujHBSc.css?delta=12&language=en&theme=mars&include=eJx9UlF2hDAIvJDdHCkPE7TUJFhIdrs9fVG3u75X64-OMDIwADFWhnJ38ACXQbjUDlSxeiofGCqLC6oXCIElEhc9zMZMxfMVRSjiISVAwhJBDnPME6EPVh2P5de-vBXwA0s-VxoT95CMGJp6rVBRvWAVHuiw9pNvCnBD5Yy-zXH574SeSQOmBAXZZE6IHMTkM0aCav6dUWch60HrPZ1KC9r41utqemVOPYj_NmrEL_v2LDRSMeIVUsOjQpljS7ja-J-LMtBReGmOvjH6QBJaMuHPxvVQ5Ib9sqyuZ65aBWY3CGS8sUxdmMwPI65Nl9onDpPb4e7js6HcfSP_vDz3RLvssqaZrJy4F9znCRKPbnvt4hV6dcujm2wIdutzj99-b6zLIOqW69ANblt4W50o4xazzWnuZhAYbdB3dVHaDOnyilxamVufSN8xdnrXitn1oNi1kq6Pmiv2M4zo1XxcrkXQrKPNU87ZZn_Y6l-2_on8AGBah9U ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 26 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.

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
Apply Now `div.col-xs-6 > div.click-region > div.click-region-link > a.apply_now_icon`

○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

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

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

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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