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

Landmark Structure

Action

5 landmarks

FIX

5 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

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

No banner (header) landmark

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.

Search landmark present

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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

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

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://uga.edu/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://uga.edu/manifest.json

Manifest contains invalid JSON.

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

6 issue(s) across 65 links and 8 buttons

REVIEW

6 issue(s) across 65 links and 8 buttons

6 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://news.uga.edu/ ("Read More"); /about/academic-excellence ("Read More"); /about ("Read More"); https://wearegeorgia.uga.edu/ ("Read More"); /about/research ("Read More"); /about/value ("Read More")

59 link(s) with descriptive text

65 links

0 empty

6 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://news.uga.edu/	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Home page
/about/academic-excellence	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Academic Excellence
/about	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: About
https://wearegeorgia.uga.edu/	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Home page
/about/research	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Research
/about/value	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Value

67 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://news.uga.edu/ ("Read More"); /about/academic-excellence ("Read More"); /about ("Read More"); https://wearegeorgia.uga.edu/ ("Read More"); /about/research ("Read More"); /about/value ("Read More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Color Contrast (Screenshot)

Action

20 text elements analyzed, 14 fail WCAG AA

REVIEW

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

6 pass 14 fail WCAG AA 4 pass AA only

h1 Welcome to the University of Georgia

2.21:1

#000000

#49453F

needs 3.0:1 (large text)

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

h2 Results that Matter

1.05:1

#000000

#0B0808

needs 3.0:1 (large text)

24px · above the fold

a Faculty & Staff

2.79:1

#000000

#575450

needs 4.5:1 (normal text)

16px · top of page (header area)

a Alumni

3.11:1

#000000

#5E5B58

needs 4.5:1 (normal text)

16px · top of page (header area)

a Community

2.98:1

#000000

#5C5854

needs 4.5:1 (normal text)

16px · above the fold

a A–Z Directory

2.76:1

#000000

#57534F

needs 4.5:1 (normal text)

16px · above the fold

button Search

2.54:1

#000000

#524E49

needs 4.5:1 (normal text)

16px · above the fold

button Menu

2.62:1

#000000

#54504A

needs 4.5:1 (normal text)

16px · above the fold

p Every student’s journey is unique, but…

1.05:1

#000000

#0A0707

needs 4.5:1 (normal text)

16px · above the fold

a Learn About UGA

1.08:1

#000000

#100D0C

needs 4.5:1 (normal text)

16px · above the fold

p Discover Georgia’s flagship institutio…

1.06:1

#000000

#0C0A09

needs 4.5:1 (normal text)

16px · mid-page

a Browse Degrees

1.07:1

#000000

#0D0C0B

needs 4.5:1 (normal text)

16px · mid-page

p 20 distinct schools and colleges to prep…

1.04:1

#000000

#090706

needs 4.5:1 (normal text)

16px · mid-page

a Plan Your Visit

1.08:1

#000000

#100D0B

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 Welcome to the Unive…	2.21:1	3.0:1	#000000	#49453F	Fail
h2 Results that Matter	1.05:1	3.0:1	#000000	#0B0808	Fail
h2 University News	3.63:1	3.0:1	#000000	#676565	Pass
h2 Resources for	3.18:1	3.0:1	#000000	#BA0C2F	Pass
h2 Events	3.18:1	3.0:1	#000000	#BA0C2F	Pass
h3 The University of Ge…	3.18:1	3.0:1	#000000	#BA0C2F	Pass
title University of Georgi…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Students	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Faculty & Staff	2.79:1	4.5:1	#000000	#575450	Fail
a Alumni	3.11:1	4.5:1	#000000	#5E5B58	Fail
a Community	2.98:1	4.5:1	#000000	#5C5854	Fail
a A–Z Directory	2.76:1	4.5:1	#000000	#57534F	Fail
button Search	2.54:1	4.5:1	#000000	#524E49	Fail
button Menu	2.62:1	4.5:1	#000000	#54504A	Fail
p Every student’s jo…	1.05:1	4.5:1	#000000	#0A0707	Fail
a Learn About UGA	1.08:1	4.5:1	#000000	#100D0C	Fail
p Discover Georgia’s…	1.06:1	4.5:1	#000000	#0C0A09	Fail
a Browse Degrees	1.07:1	4.5:1	#000000	#0D0C0B	Fail
p 20 distinct schools …	1.04:1	4.5:1	#000000	#090706	Fail
a Plan Your Visit	1.08:1	4.5:1	#000000	#100D0B	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+

Heading Hierarchy

16 headings

PASS

16 headings

Single H1 present

H1 Welcome to the University of Georgia
H2 Results that Matter
H2 University News
H2 School of Medicine extends admission offers for inaugural class
H2 Working Lands for Wildlife joins University of Georgia to expand conservation impact
H2 UGA School of Nursing to be named in honor of Victoria Kay Ivester
H2 Perdue to retire as chancellor of the University System of Georgia
H2 2026 CURO Symposium breaks record with over 900 presenters
H3 The University of Georgia is…
H3 An Academic Powerhouse
H3 Built Upon Visionary Leadership
H3 Serving Communities
H3 Driving Discovery and Innovation
H3 A Top Value
H2 Resources for Current Students
H2 Events

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

3 decorative image(s) correctly marked

2 image(s) with good alt text

5 images 2 good alt text 3 decorative

All images have appropriate alt text.

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
#search	search	Search	aria-label

A+

Lighthouse Accessibility Audits

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

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav#navbar > div.navbar__right > div.navbar__right-buttons > button.navbar__right-buttons-search `nav#navbar > div.navbar__right > div.navbar__right-buttons > button.navbar__right-buttons-search`
nav#navbar > div.navbar__right > div.navbar__right-buttons > button.navbar__right-buttons-menu `nav#navbar > div.navbar__right > div.navbar__right-buttons > button.navbar__right-buttons-menu`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
UGA on Twitter `div.ugafooter__container > div.ugafooter__row > nav.ugafooter__social > a.ugafooter__social-link`

○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

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

●`button`, `link`, and `menuitem` elements have accessible names

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

●Heading elements appear in a sequentially-descending order

●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

○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

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

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