Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ 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

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.

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 ✗

Link & Button Quality

1 issue(s) across 89 links and 4 buttons

REVIEW

1 issue(s) across 89 links and 4 buttons

1 link(s) with no accessible text

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

Got: a#backTopButton

4 link(s) open in new tab without warning

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

Got: https://www.alaska.edu/records/records/compliance/gdpr/ua-privacy-statement/; https://www.websitepolicies.com/cookie-consent-banner-generator; https://www.alaska.edu/; /uajourney/

84 link(s) with descriptive text

89 links

1 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.alaska.edu/records/records/c…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.websitepolicies.com/cookie-c…	Powered by WebsitePolicies	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://www.alaska.edu/	Home button	new tab	Add '(opens in new tab)' to text
/uajourney/	UA Journey	new tab	Add '(opens in new tab)' to text

88 links and buttons have descriptive text

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

a#backTopButton

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

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

https://www.alaska.edu/records/records/compliance/gdpr/ua-privacy-statement/; https://www.websitepolicies.com/cookie-consent-banner-generator; https://www.alaska.edu/; /uajourney/

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

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Error 404: Document Not Found | University of Alaska System ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h1 Information for Prospective Students

1.32:1

#000000

#222222

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Featured Campaigns

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Quick Facts

1.32:1

#000000

#222222

needs 3.0:1 (large text)

19px · bottom of viewport

h3 The University of Alaska is a land-, sea…

1.32:1

#000000

#222222

needs 3.0:1 (large text)

19px · bottom of viewport

title UA System | University of Alaska System

2.36:1

#000000

#004895

needs 4.5:1 (normal text)

16px · top of page (header area)

span We use cookies to provide you with the b…

2.36:1

#000000

#004895

needs 4.5:1 (normal text)

16px · top of page (header area)

a Privacy Policy

2.36:1

#000000

#004895

needs 4.5:1 (normal text)

16px · top of page (header area)

button Accept

2.36:1

#000000

#004895

needs 4.5:1 (normal text)

16px · top of page (header area)

a Powered by WebsitePolicies

2.45:1

#000000

#0C5460

needs 4.5:1 (normal text)

16px · above the fold

div Sort by

3.88:1

#000000

#2B728B

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div Relevance

1.41:1

#000000

#1A2A2C

needs 4.5:1 (normal text)

16px · above the fold

div Date

1.14:1

#000000

#0E160F

needs 4.5:1 (normal text)

16px · above the fold

span Home button

1.07:1

#000000

#0A0C0D

needs 4.5:1 (normal text)

16px · above the fold

a UAOnline

1.07:1

#000000

#0A0B0C

needs 4.5:1 (normal text)

16px · above the fold

a Staff Directory

1.06:1

#000000

#090B0B

needs 4.5:1 (normal text)

16px · above the fold

a Careers at UA

1.06:1

#000000

#080A0A

needs 4.5:1 (normal text)

16px · mid-page

a UA System Office

1.05:1

#000000

#080909

needs 4.5:1 (normal text)

16px · mid-page

span Quick links

1.12:1

#000000

#111212

needs 4.5:1 (normal text)

16px · mid-page

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
h1 Information for Pros…	1.32:1	3.0:1	#000000	#222222	Fail
h2 Featured Campaigns	1.32:1	3.0:1	#000000	#222222	Fail
h3 Quick Facts	1.32:1	3.0:1	#000000	#222222	Fail
h3 The University of Al…	1.32:1	3.0:1	#000000	#222222	Fail
title UA System \| Universi…	2.36:1	4.5:1	#000000	#004895	Fail
span We use cookies to pr…	2.36:1	4.5:1	#000000	#004895	Fail
a Privacy Policy	2.36:1	4.5:1	#000000	#004895	Fail
button Accept	2.36:1	4.5:1	#000000	#004895	Fail
a Powered by WebsitePo…	2.45:1	4.5:1	#000000	#0C5460	Fail
a Skip to main content	9.87:1	4.5:1	#000000	#9AB7BC	Pass
div Custom Search	13.55:1	4.5:1	#000000	#C9D1D4	Pass
div Sort by	3.88:1	4.5:1	#000000	#2B728B	Fail
div Relevance	1.41:1	4.5:1	#000000	#1A2A2C	Fail
div Date	1.14:1	4.5:1	#000000	#0E160F	Fail
span Home button	1.07:1	4.5:1	#000000	#0A0C0D	Fail
a UAOnline	1.07:1	4.5:1	#000000	#0A0B0C	Fail
a Staff Directory	1.06:1	4.5:1	#000000	#090B0B	Fail
a Careers at UA	1.06:1	4.5:1	#000000	#080A0A	Fail
a UA System Office	1.05:1	4.5:1	#000000	#080909	Fail
span Quick links	1.12:1	4.5:1	#000000	#111212	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

<main> landmark present

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

A+

Heading Hierarchy

16 headings

PASS

16 headings

Single H1 present

H1 Information for Prospective Students
H2 Featured Campaigns
H2 UA news and information
H3 Quick Facts
H4 ~500
H4 Degrees, certificates and endorsements
H4 ~140
H4 eLearning programs
H4 20,500
H4 Students enrolled in 2025
H4 100,000+
H4 Alumni
H4 $239.7 M
H4 Research expenditure
H3 The University of Alaska is a land-, sea- and space-grant system of higher education established in 1917.
H4 The UA system's three universities (UAA, UAF and UAS) are separately accredited institutions with campuses and extended learning centers across the state of Alaska.

A+

Alt Text Quality

All 25 images OK

PASS

All 25 images OK

1 image(s) with alt text over 125 characters

24 image(s) with good alt text

25 images 24 good alt text

Issue	Count
too long	1 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
#gsc-i-id1	text	search	aria-label

A+

Lighthouse Accessibility Audits

Score 96/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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
campuses `div.row > div.col-md > h4 > a`

These are opportunities to improve the legibility of your content.

○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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○Form elements have associated labels

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

○Uses ARIA roles only on compatible elements

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