Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-ufh8hi

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://utah.gov/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://utah.gov/manifest.json

Manifest contains invalid JSON.

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: #175264

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

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Heading Hierarchy

15 headings

REVIEW

15 headings

No H1 heading found

Every page should have one H1 that describes the page content.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 Text Size
H3 Contrast
H3 Appearance
H3 Chatbot
H3 (empty)
H3 I am:
H2 Featured Services
H2 Utah Local
H3 My Representatives
H3 Meetings
H3 Jobs
H2 Visiting Utah
H3 Travel & Tourism
H3 Utah State Parks
H3 View More

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Link & Button Quality

1 issue(s) across 25 links and 16 buttons

REVIEW

1 issue(s) across 25 links and 16 buttons

6 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://le.utah.gov/GIS/findDistrict.jsp"]; a[href="https://www.utah.gov/pmn/"]; a[href="./local/#jobs"]; a[href="https://www.visitutah.com/"]; a[href="https://stateparks.utah.gov"]; a[href="./visit/"]

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#bgInfo--activator

19 link(s) with descriptive text

25 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://le.utah.gov/GIS/findDistrict.jsp	My Representatives Find…	img no alt	Add alt attribute to the image
https://www.utah.gov/pmn/	Meetings Find upcoming …	img no alt	Add alt attribute to the image
./local/#jobs	Jobs Find Job openings …	img no alt	Add alt attribute to the image
https://www.visitutah.com/	Travel & Tourism Inform…	img no alt	Add alt attribute to the image
https://stateparks.utah.gov	Utah State Parks Visit …	img no alt	Add alt attribute to the image
./visit/	View More Utah visiting…	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label

34 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://le.utah.gov/GIS/findDistrict.jsp"]; a[href="https://www.utah.gov/pmn/"]; a[href="./local/#jobs"]; a[href="https://www.visitutah.com/"]; a[href="https://stateparks.utah.gov"]; a[href="./visit/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Icon-only buttons need an aria-label so screen readers can announce them.

button#bgInfo--activator

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

15 icon(s) detected

REVIEW

15 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

h3 Text Size

2.43:1

#000000

#175264

needs 3.0:1 (large text)

19px · mid-page

h3 Contrast

1.19:1

#000000

#021936

needs 3.0:1 (large text)

19px · mid-page

h3 Appearance

1.28:1

#000000

#071D49

needs 3.0:1 (large text)

19px · mid-page

title Home | Utah.gov

1.19:1

#000000

#021936

needs 4.5:1 (normal text)

16px · top of page (header area)

a Utah.gov - An official website

1.19:1

#000000

#021936

needs 4.5:1 (normal text)

16px · top of page (header area)

label Search Utah.gov

1.19:1

#000000

#021936

needs 4.5:1 (normal text)

16px · top of page (header area)

button Search

1.19:1

#000000

#021936

needs 4.5:1 (normal text)

16px · top of page (header area)

a Services

1.19:1

#000000

#021936

needs 4.5:1 (normal text)

16px · above the fold

a Government

1.19:1

#000000

#021936

needs 4.5:1 (normal text)

16px · above the fold

a Business

1.19:1

#000000

#021936

needs 4.5:1 (normal text)

16px · above the fold

a Employment

1.19:1

#000000

#021936

needs 4.5:1 (normal text)

16px · above the fold

a Education

1.19:1

#000000

#021936

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 Text Size	2.43:1	3.0:1	#000000	#175264	Fail
h3 Contrast	1.19:1	3.0:1	#000000	#021936	Fail
h3 Appearance	1.28:1	3.0:1	#000000	#071D49	Fail
h3 Chatbot	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 I am:	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 My Representatives	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Meetings	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Jobs	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Travel & Tourism	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Utah State Parks	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 View More	18.43:1	3.0:1	#000000	#F0F0F0	Pass
title Home \| Utah.gov	1.19:1	4.5:1	#000000	#021936	Fail
a Utah.gov - An offici…	1.19:1	4.5:1	#000000	#021936	Fail
label Search Utah.gov	1.19:1	4.5:1	#000000	#021936	Fail
button Search	1.19:1	4.5:1	#000000	#021936	Fail
a Services	1.19:1	4.5:1	#000000	#021936	Fail
a Government	1.19:1	4.5:1	#000000	#021936	Fail
a Business	1.19:1	4.5:1	#000000	#021936	Fail
a Employment	1.19:1	4.5:1	#000000	#021936	Fail
a Education	1.19:1	4.5:1	#000000	#021936	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

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

6 decorative image(s) correctly marked

6 images 6 decorative

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
#nav--search	search	Search Utah.gov	aria-label
#homeSearch	search	Search	for/id

A+

Lighthouse Accessibility Audits

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

●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

●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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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