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

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

2 issue(s) across 85 links and 4 buttons

REVIEW

2 issue(s) across 85 links and 4 buttons

2 link(s) with no accessible text

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

Got: https://news.ua.edu/2026/03/ua-launches-automotive-engineering-exchange-program/; https://news.ua.edu/2026/03/ua-launches-automotive-engineering-exchange-program/

1 link(s) open in new tab without warning

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

Got: https://uasystem.edu/

82 link(s) with descriptive text

85 links

2 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://news.ua.edu/2026/03/ua-launches-…	(empty)	empty	Add link text or aria-label
https://news.ua.edu/2026/03/ua-launches-…	(empty)	empty	Add link text or aria-label
https://uasystem.edu/	Part of the University of Alab…	new tab	Add '(opens in new tab)' to text

86 links and buttons have descriptive text

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

https://news.ua.edu/2026/03/ua-launches-automotive-engineering-exchange-program/; https://news.ua.edu/2026/03/ua-launches-automotive-engineering-exchange-program/

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://uasystem.edu/

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

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | The University of Alabama ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 WHERE LEGENDS

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

32px · bottom of viewport

h1 ARE MADE

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

32px · bottom of viewport

h1 WHERE LEGENDS

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

32px · bottom of viewport

h1 ARE MADE

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Home

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

32px · bottom of viewport

h2 LEGENDARY

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

24px · bottom of viewport

h2 NEWS

1.00:1

#9E1B32

needs 3.0:1 (large text)

24px · bottom of viewport

h2 EXPERIENCE

1.00:1

#9E1B32

needs 3.0:1 (large text)

24px · bottom of viewport

h2 TRIUMPH

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contact

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Resources

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Tools

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

24px · bottom of viewport

h3 RESEARCH

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

19px · bottom of viewport

h3 COMMENCEMENT

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

19px · bottom of viewport

h3 RESEARCH

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

19px · bottom of viewport

h3 RESEARCH

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

19px · bottom of viewport

h3 COMMENCEMENT

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

19px · bottom of viewport

h3 RESEARCH

2.66:1

#000000

#9E1B32

needs 3.0:1 (large text)

19px · bottom of viewport

title The University of Alabama

2.66:1

#000000

#9E1B32

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

2.53:1

#000000

#90263B

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

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 WHERE LEGENDS	2.66:1	3.0:1	#000000	#9E1B32	Fail
h1 ARE MADE	2.66:1	3.0:1	#000000	#9E1B32	Fail
h1 WHERE LEGENDS	2.66:1	3.0:1	#000000	#9E1B32	Fail
h1 ARE MADE	2.66:1	3.0:1	#000000	#9E1B32	Fail
h1 Home	2.66:1	3.0:1	#000000	#9E1B32	Fail
h2 LEGENDARY	2.66:1	3.0:1	#000000	#9E1B32	Fail
h2 NEWS	1.00:1	3.0:1	#9E1B32	#9E1B32	Fail
h2 EXPERIENCE	1.00:1	3.0:1	#9E1B32	#9E1B32	Fail
h2 TRIUMPH	2.66:1	3.0:1	#000000	#9E1B32	Fail
h2 Contact	2.66:1	3.0:1	#000000	#9E1B32	Fail
h2 Resources	2.66:1	3.0:1	#000000	#9E1B32	Fail
h2 Tools	2.66:1	3.0:1	#000000	#9E1B32	Fail
h3 RESEARCH	2.66:1	3.0:1	#000000	#9E1B32	Fail
h3 COMMENCEMENT	2.66:1	3.0:1	#000000	#9E1B32	Fail
h3 RESEARCH	2.66:1	3.0:1	#000000	#9E1B32	Fail
h3 RESEARCH	2.66:1	3.0:1	#000000	#9E1B32	Fail
h3 COMMENCEMENT	2.66:1	3.0:1	#000000	#9E1B32	Fail
h3 RESEARCH	2.66:1	3.0:1	#000000	#9E1B32	Fail
title The University of Al…	2.66:1	4.5:1	#000000	#9E1B32	Fail
a Skip to content	2.53:1	4.5:1	#000000	#90263B	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

Page Structure — as a screen reader sees it

Heading Hierarchy

22 headings

PASS

22 headings

Multiple H1 headings (3 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 WHERE LEGENDSARE MADE
H1 WHERE LEGENDSARE MADE duplicate H1
H1 Home duplicate H1
H2 LEGENDARY ACADEMICS
H3 MAJORS AND PROGRAMS
H3 UA ONLINE
H3 RESEARCH
H3 EXPERIENTIAL LEARNING
H2 UNIVERSITY NEWS
H3 UA-Developed Software Used for NASA Moon Missions
H3 RESEARCH
H3 COMMENCEMENT
H3 RESEARCH
H3 UA-Developed Software Used for NASA Moon Missions
H3 RESEARCH
H3 COMMENCEMENT
H3 RESEARCH
H2 THE ALABAMA EXPERIENCE
H2 EVERY TRIUMPHHAS ITS ORIGIN STORY
H2 Contact
H2 Resources
H2 Tools

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 18 images OK

PASS

All 18 images OK

12 decorative image(s) correctly marked

6 image(s) with good alt text

18 images 6 good alt text 12 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
#UA_BrandBar_SearchInput	search	Search	for/id
#UA_BrandBar_MenuSearchInput	text	Search	for/id

Lighthouse Accessibility Audits

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

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wp-block-group > div.wp-block-group > p.has-text-align-center > a `div.wp-block-group > div.wp-block-group > p.has-text-align-center > a`

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.

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
Copyright © 2026 `div.ua_brand-footer_logo-copyright > p > span > a`
(205) 348-6010 `div.ua_brand-footer_logo-copyright > p > span > a`
Contact UA `div.ua_brand-footer_logo-copyright > p > span > a`
Accessibility `nav > ul.ua_brand-footer_link-list > li > a`
SACSCOC `nav > ul.ua_brand-footer_link-list > li > a`
Taskstream `nav > ul.ua_brand-footer_link-list > li > a`

These items highlight common accessibility best practices.

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

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

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

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

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

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