Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 3 REVIEW 2 FIX

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

7 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 7 <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.

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

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

Display Mode standalone Theme Color #ab0520 Background Color #ab0520 Icons 2 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA 14 pass AA only

title University of Arizona in Tucson, AZ

2.77:1

#000000

#AB0520

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Main Menu	7.40:1	3.0:1	#000000	#A29795	Pass
h2 Main navigation	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h2 Your Future Awaits	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h2 The Arizona Impact	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h2 See Yourself Here	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h2 Footer - Main	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h2 Information For	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h2 Topics	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h2 Resources	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h2 Connect	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h3 Main Campus	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h3 Online	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h3 Near You Network	3.87:1	3.0:1	#000000	#6A6D3E	Pass
h3 International	3.87:1	3.0:1	#000000	#6A6D3E	Pass
title University of Arizon…	2.77:1	4.5:1	#000000	#AB0520	Fail
a Skip to main content	5.89:1	4.5:1	#000000	#CD6979	Pass
label Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Resources	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Campus Map	21.00:1	4.5:1	#000000	#FFFFFF	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.

Landmark Structure

17 landmarks

PASS

17 landmarks

<main> landmark present

7 <nav> landmark(s) found

1 of 7 <nav> elements are unlabeled

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

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

Heading Hierarchy

19 headings, 1 skip(s)

PASS

19 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Main Menu
H2 Main navigation
H1 Congratulations, Future Wildcats!
H2 Start Your Wildcat Journey
H2 Your Future Awaits
H4 U of A professors Elaine Romero, Erika Hamden named 2026 Guggenheim Fellows skipped
H4 Turning up the volume on global health, U of A students take aim at $1M Hult Prize
H4 Arizona, men's basketball head coach Tommy Lloyd agree to contract extension through 2031 season
H3 Main Campus
H3 Online
H3 Near You Network
H3 International
H2 The Arizona Impact
H2 See Yourself Here
H2 Footer - Main
H2 Information For
H2 Topics
H2 Resources
H2 Connect

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

A+

Alt Text Quality

All 29 images OK

PASS

All 29 images OK

2 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

26 image(s) with good alt text

29 images 26 good alt text 1 decorative

Issue	Count
too long	2 image(s)

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-keys	search	Search this site	aria-label
#edit-keys--2	search	Search this site	aria-label
#az-select-menu-select	select	Select your audience	for/id

Link & Button Quality

179 links, 21 buttons — all OK

PASS

179 links, 21 buttons — all OK

4 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /research/space; https://safety.arizona.edu; https://www.arizona.edu/information-security-privacy; https://www.arizona.edu

175 link(s) with descriptive text

179 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/research/space	Arizona's Impact in Space	new tab	Add '(opens in new tab)' to text
https://safety.arizona.edu	Campus Safety	new tab	Add '(opens in new tab)' to text
https://www.arizona.edu/information-secu…	University Information Securit…	new tab	Add '(opens in new tab)' to text
https://www.arizona.edu	The University of Arizona	new tab	Add '(opens in new tab)' to text

196 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

/research/space; https://safety.arizona.edu; https://www.arizona.edu/information-security-privacy; https://www.arizona.edu

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | The University of Arizona ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /sites/default/files/css/css_-FxQjKG-sPC2hfPoUz_QCPciWVBycQaCwtwmIrQaunE.css?delta=7&language=en&theme=az_barrio&include=eJyNUtFuwyAM_CESPmePyICT0ACOMOnSfv1M2mjNpml9Qfb5bIs7AzNWE_IFXaWiHXPvaM0VC7hqEpQxZJPhamLIMxtOCn53VEwLFSg3AyXcKYOZEDwWM4RNwd1YKCWQhnv3iDoahs5BvgJ3MrtRHBVshEQ2RDzQIeIWbESzwNjKZ8DUCRM23gIFxgLLxPqU9W0yFM__kSpu9R2OfMXNYxGF_Fv0hD7AmWl4iaGyK4hZ_1lpPYwRmwmYV31OlSWqXKXr0HaMZCF2XG9i1KjcLIvFHvHJY642kpv1S6x2vR2Jb1kw7n8O7Lp9z07zZV0g9nCBTQk51JvBZNFrB0sNlJX8tJ3HQXymaiQaxSrHqB-hRB8gpyVndapm-oZ3xfQQogD9seBF5-eOF63XvKw2Bp7QK76xHKO2wKiuAT9Z72-fyK8RvwBsdyft

Print Stylesheet ✓ Print Optimized

Print stylesheet /sites/default/files/css/css_-FxQjKG-sPC2hfPoUz_QCPciWVBycQaCwtwmIrQaunE.css?delta=7&language=en&theme=az_barrio&include=eJyNUtFuwyAM_CESPmePyICT0ACOMOnSfv1M2mjNpml9Qfb5bIs7AzNWE_IFXaWiHXPvaM0VC7hqEpQxZJPhamLIMxtOCn53VEwLFSg3AyXcKYOZEDwWM4RNwd1YKCWQhnv3iDoahs5BvgJ3MrtRHBVshEQ2RDzQIeIWbESzwNjKZ8DUCRM23gIFxgLLxPqU9W0yFM__kSpu9R2OfMXNYxGF_Fv0hD7AmWl4iaGyK4hZ_1lpPYwRmwmYV31OlSWqXKXr0HaMZCF2XG9i1KjcLIvFHvHJY642kpv1S6x2vR2Jb1kw7n8O7Lp9z07zZV0g9nCBTQk51JvBZNFrB0sNlJX8tJ3HQXymaiQaxSrHqB-hRB8gpyVndapm-oZ3xfQQogD9seBF5-eOF63XvKw2Bp7QK76xHKO2wKiuAT9Z72-fyK8RvwBsdyft ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 25 passed

PASS

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
U of A professors Elaine Romero, Erika Hamden named 2026 Guggenheim Fellows `div.node__content > div.card > a.field-group-link > h4.card-title`

These are opportunities to improve keyboard navigation in your application.

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

●Select elements have associated label elements.

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

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