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 2 REVIEW 5 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 ✗

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 Error 404: Document Not Found | University of Alaska Fairbanks ✓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

h1 UAF Home

1.32:1

#000000

#222222

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Where will your journey take the world?

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 From accounting to Yup’ik language and…

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A place to find yourself.

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Include everyone in the journey.

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What — and who — we’re made of

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Where you'll learn.

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 News and events

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Land acknowledgment

1.32:1

#000000

#222222

needs 3.0:1 (large text)

24px · bottom of viewport

title UAF Home | University of Alaska Fairbank…

2.97:1

#000000

#1E5C8D

needs 4.5:1 (normal text)

16px · top of page (header area)

span We use cookies to provide you with the b…

2.97:1

#000000

#1E5C8D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Privacy Policy

1.30:1

#000000

#111C4E

needs 4.5:1 (normal text)

16px · top of page (header area)

button Accept

1.30:1

#000000

#111C4E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Powered by WebsitePolicies

2.54:1

#000000

#185087

needs 4.5:1 (normal text)

16px · above the fold

a Skip to main content

3.63:1

#000000

#406894

needs 4.5:1 (normal text)

16px · above the fold

div Custom Search

3.14:1

#000000

#4C5D77

needs 4.5:1 (normal text)

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

div Sort by

1.27:1

#000000

#00203D

needs 4.5:1 (normal text)

16px · above the fold

div Relevance

1.05:1

#000000

#040811

needs 4.5:1 (normal text)

16px · above the fold

div Date

1.05:1

#000000

#080808

needs 4.5:1 (normal text)

16px · above the fold

a A-Z

1.05:1

#000000

#080808

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
h1 UAF Home	1.32:1	3.0:1	#000000	#222222	Fail
h2 Where will your jour…	1.32:1	3.0:1	#000000	#222222	Fail
h2 From accounting to Y…	1.32:1	3.0:1	#000000	#222222	Fail
h2 A place to find your…	1.32:1	3.0:1	#000000	#222222	Fail
h2 Include everyone in …	1.32:1	3.0:1	#000000	#222222	Fail
h2 What — and who —…	1.32:1	3.0:1	#000000	#222222	Fail
h2 Where you'll learn.	1.32:1	3.0:1	#000000	#222222	Fail
h2 News and events	1.32:1	3.0:1	#000000	#222222	Fail
h2 Land acknowledgment	1.32:1	3.0:1	#000000	#222222	Fail
title UAF Home \| Universit…	2.97:1	4.5:1	#000000	#1E5C8D	Fail
span We use cookies to pr…	2.97:1	4.5:1	#000000	#1E5C8D	Fail
a Privacy Policy	1.30:1	4.5:1	#000000	#111C4E	Fail
button Accept	1.30:1	4.5:1	#000000	#111C4E	Fail
a Powered by WebsitePo…	2.54:1	4.5:1	#000000	#185087	Fail
a Skip to main content	3.63:1	4.5:1	#000000	#406894	Fail
div Custom Search	3.14:1	4.5:1	#000000	#4C5D77	Fail
div Sort by	1.27:1	4.5:1	#000000	#00203D	Fail
div Relevance	1.05:1	4.5:1	#000000	#040811	Fail
div Date	1.05:1	4.5:1	#000000	#080808	Fail
a A-Z	1.05:1	4.5:1	#000000	#080808	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

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

9 headings

PASS

9 headings

Single H1 present

H1 UAF Home
H2 Where will your journey take the world?
H2 From accounting to Yup’ik language and culture.
H2 A place to find yourself.
H2 Include everyone in the journey.
H2 What — and who — we’re made of
H2 Where you'll learn.
H2 News and events
H2 Land acknowledgment

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

2 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

13 image(s) with good alt text

16 images 13 good alt text 1 decorative

Issue	Count
too long	2 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

Link & Button Quality

172 links, 7 buttons — all OK

PASS

172 links, 7 buttons — all OK

8 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://ecampus.uaf.edu/; /aurora/index.php; https://www.usda.gov/; https://www.nifa.usda.gov/; https://www.alaska.edu/webaccessibility/; https://www.alaska.edu/records/records/compliance/gdpr/ua-privacy-statement/

164 link(s) with descriptive text

172 links

0 empty

0 generic text

8 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
https://ecampus.uaf.edu/	UAF eCampus	new tab	Add '(opens in new tab)' to text
/aurora/index.php	Aurora magazine: Winter 2025	new tab	Add '(opens in new tab)' to text
https://www.usda.gov/	U.S. Department of Agriculture…	new tab	Add '(opens in new tab)' to text
https://www.nifa.usda.gov/	National Institute of Food and…	new tab	Add '(opens in new tab)' to text
https://www.alaska.edu/webaccessibility/	notice of web accessibility	new tab	Add '(opens in new tab)' to text
https://www.alaska.edu/records/records/c…	Privacy Statement	new tab	Add '(opens in new tab)' to text

171 links and buttons have descriptive text

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://ecampus.uaf.edu/; /aurora/index.php; https://www.usda.gov/; https://www.nifa.usda.gov/; https://www.alaska.edu/webaccessibility/; https://www.alaska.edu/records/records/compliance/gdpr/ua-privacy-statement/

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

A+

Lighthouse Accessibility Audits

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

●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

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