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

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://uark.edu/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://uark.edu/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: #fff

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 ✗

Heading Hierarchy

18 headings

REVIEW

18 headings

No H1 heading found

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

H2 Your Path
H2 Starts Here
H2 The Razorback Experience
H2 Dedicated to Arkansas
H2 Determined to Build a Better World
H2 #MyPath to Senior Walk
H2 Short Takes
H2 Record-Breaking Momentum
H2 Record-Breaking Momentum
H3 The Man Behind Murdle
H2 The Man Behind Murdle
H3 When in Rome
H2 When in Rome
H2 Arkansas News
H3 Mid-South AI Research Consortium to Fuel Innovation
H3 University Sets Research Record, Focuses on Improving Lives
H3 School of Art Invites Campus to Celebrate Fine Arts Center Grand Reopening on April 16
H3 U of A to Unveil Solar Farm on Earth Day, Launching a Landmark Clean Energy Initiative

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

Favicon & Branding

16 icon(s) detected

REVIEW

16 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, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA

label Search

1.33:1

#000000

#19260F

needs 4.5:1 (normal text)

16px · top of page (header area)

span Search

2.35:1

#000000

#3B5018

needs 4.5:1 (normal text)

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

a Home

1.37:1

#000000

#1A2910

needs 4.5:1 (normal text)

16px · above the fold

a About

3.26:1

#000000

#4D6632

needs 4.5:1 (normal text)

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

a Apply

1.33:1

#000000

#1F250D

needs 4.5:1 (normal text)

16px · above the fold

a Academics

1.09:1

#000000

#0D1006

needs 4.5:1 (normal text)

16px · above the fold

2 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 Your Path	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 Starts Here	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 Experience	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 Dedicated	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 Determined	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 #MyPath	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 Short	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 Record-Breaking Mome…	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 The Man Behind Murdl…	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 When in Rome	18.89:1	3.0:1	#000000	#F7F2EE	Pass
h2 Arkansas	18.89:1	3.0:1	#000000	#F7F2EE	Pass
title University of Arkans…	8.33:1	4.5:1	#000000	#D291A5	Pass
a Skip to content	18.78:1	4.5:1	#000000	#F2F2F4	Pass
button CLOSE	18.78:1	4.5:1	#000000	#F2F2F4	Pass
label Search	1.33:1	4.5:1	#000000	#19260F	Fail
span Search	2.35:1	4.5:1	#000000	#3B5018	Fail
a Home	1.37:1	4.5:1	#000000	#1A2910	Fail
a About	3.26:1	4.5:1	#000000	#4D6632	Fail
a Apply	1.33:1	4.5:1	#000000	#1F250D	Fail
a Academics	1.09:1	4.5:1	#000000	#0D1006	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.

Lighthouse Accessibility Audits

Score 86/100 — 4 failing, 23 passed

REVIEW

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MENU `nav#uark-brand > div#uark-site-id > nav#uark-mobile-menu-button > button.navbar-toggler`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Edit webpage Copyright of University of Arkansas `body.loaded > span#directedit-footer`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ACADEMICS `div > ul#footer-global-links > li.list-inline-item > a`
NEWS `div > ul#footer-global-links > li.list-inline-item > a`
RAZORBACKS `div > ul#footer-global-links > li.list-inline-item > a`
479-575-2000 `div.d-flex > div.flex-grow-1 > address > a`
Title IX `div.col-md-12 > ul.list-inline > li.list-inline-item > a`
Jobs `div.col-md-12 > ul.list-inline > li.list-inline-item > a`

These items highlight common accessibility best practices.

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
479-575-2000 `div.d-flex > div.flex-grow-1 > address > a`

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

●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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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

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

○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

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

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

Landmark Structure

12 landmarks

PASS

12 landmarks

<main> landmark present

9 <nav> landmark(s) found

9 of 9 <nav> elements are unlabeled

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

Skip navigation link 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+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

3 decorative image(s) correctly marked

14 image(s) with good alt text

17 images 14 good alt text 3 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
#uark-search-mobile	text	Search	for/id
#uark-search	text	Search	for/id

A+

Link & Button Quality

107 links, 9 buttons — all OK

PASS

107 links, 9 buttons — all OK

107 link(s) with descriptive text

107 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

116 links and buttons have descriptive text

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.