Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 REVIEW 6 FIX

Link & Button Quality

Action

10 issue(s) across 178 links and 44 buttons

FIX

10 issue(s) across 178 links and 44 buttons

4 link(s) with no accessible text

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

Got: a.off-canvas-menu-trigger (#782 on page); https://www.uab.edu/news/news-you-can-use/understanding-and-managing-storm-an…; https://www.uab.edu/news/research-innovation/new-uab-startup-seeks-to-scale-s…; https://www.uab.edu/news/health-medicine/new-department-of-defense-funding-ad…

9 link(s) open in new tab without warning

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

Got: https://www.facebook.com/uabstudents; https://twitter.com/UABStudents; https://www.instagram.com/uab.edu/; https://www.youtube.com/user/UABNews; https://www.snapchat.com/add/uab.snapdragon; https://www.linkedin.com/company/uab; https://www.uab.edu/privacy; https://www.uab.edu/privacy; https://www.onetrust.com/products/cookie-consent/

6 button(s) with no accessible text

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

Got: button (#1331 on page); button (#1343 on page); button (#1359 on page); button (#1375 on page); button (#1391 on page); button.ot-host-box (#1470 on page)

165 link(s) with descriptive text

178 links

4 empty

0 generic text

9 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/uabstudents	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/UABStudents	Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/uab.edu/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/UABNews	Youtube	new tab	Add '(opens in new tab)' to text
https://www.snapchat.com/add/uab.snapdra…	Snapchat	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/uab	Linkedin	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://www.uab.edu/news/news-you-can-us…	(empty)	empty	Add link text or aria-label
https://www.uab.edu/news/research-innova…	(empty)	empty	Add link text or aria-label
https://www.uab.edu/news/health-medicine…	(empty)	empty	Add link text or aria-label
https://www.uab.edu/privacy	Find out more about privacy at…	new tab	Add '(opens in new tab)' to text
https://www.uab.edu/privacy	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

203 links and buttons have descriptive text

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

a.off-canvas-menu-trigger (#782 on page); https://www.uab.edu/news/news-you-can-use/understanding-and-managing-storm-an…; https://www.uab.edu/news/research-innovation/new-uab-startup-seeks-to-scale-s…; https://www.uab.edu/news/health-medicine/new-department-of-defense-funding-ad…

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://www.facebook.com/uabstudents; https://twitter.com/UABStudents; https://www.instagram.com/uab.edu/; https://www.youtube.com/user/UABNews; https://www.snapchat.com/add/uab.snapdragon; https://www.linkedin.com/company/uab; https://www.uab.edu/privacy; https://www.uab.edu/privacy; https://www.onetrust.com/products/cookie-consent/

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

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

button (#1331 on page); button (#1343 on page); button (#1359 on page); button (#1375 on page); button (#1391 on page); button.ot-host-box (#1470 on page)

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

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

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

Got: https://uab.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: #1e6b52

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

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Skip navigation link detected

Back-to-top link detected

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Skip Link Skip link detected

Labeled Navigation 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Heading Hierarchy

Action

33 headings, 1 skip(s)

REVIEW

33 headings, 1 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

2 empty heading(s)

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

H1 Explore UAB
H2 Future Students
H2 Current Students
H2 Parents & Family
H2 Alumni
H2 Faculty & Staff
H2 Researchers
H2 Patients
H2 Colleges & Schools
H5 Search skipped
H1 Welcome to UAB duplicate H1
H2 Defined by Excellence and Achievement
H2 Ready to Become a Blazer?
H2 By the Numbers
H2 Transforming Lives, Every Day
H2 A Bold Vision
H2 The City is Your Classroom
H2 Looking for your path?
H2 Latest News
H2 About UAB
H2 About UAB
H1 Nondiscrimination Statement duplicate H1
H2 Privacy at UAB
H2 Privacy Preference Center
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Social Media Cookies
H4 Functionality Cookies
H4 Performance Cookies
H4 Advertising Cookies
H3 Performance Cookies
H3 (empty)
H4 (empty)

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

Alt Text Quality

3 of 17 images have issues

REVIEW

3 of 17 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 decorative image(s) correctly marked

13 image(s) with good alt text

17 images 13 good alt text 1 decorative 3 missing

Issue	Count
missing	3 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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

REVIEW

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

2 pass 18 fail WCAG AA 1 pass AA only

h1 Welcome to UAB

1.34:1

#000000

#122722

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Nondiscrimination Statement

1.34:1

#000000

#122722

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Colleges & Schools

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Defined by Excellence and Achievement

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to Become a Blazer?

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 By the Numbers

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Transforming Lives,

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Every Day

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A Bold Vision

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The City is Your Classroom

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Looking for your path?

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest News

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 About UAB

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy at UAB

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Preference Center

1.34:1

#000000

#122722

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Manage Consent Preferences

1.34:1

#000000

#122722

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Performance Cookies

1.34:1

#000000

#122722

needs 3.0:1 (large text)

19px · bottom of viewport

title Home - The University of Alabama at Birm…

2.42:1

#000000

#1A5632

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Explore UAB	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Welcome to UAB	1.34:1	3.0:1	#000000	#122722	Fail
h1 Nondiscrimination St…	1.34:1	3.0:1	#000000	#122722	Fail
h2 Colleges & Schools	1.34:1	3.0:1	#000000	#122722	Fail
h2 Defined by Excellenc…	1.34:1	3.0:1	#000000	#122722	Fail
h2 Ready to Become a Bl…	1.34:1	3.0:1	#000000	#122722	Fail
h2 By the Numbers	1.34:1	3.0:1	#000000	#122722	Fail
h2 Transforming Lives,	1.34:1	3.0:1	#000000	#122722	Fail
h2 Every Day	1.34:1	3.0:1	#000000	#122722	Fail
h2 A Bold Vision	1.34:1	3.0:1	#000000	#122722	Fail
h2 The City is Your Cla…	1.34:1	3.0:1	#000000	#122722	Fail
h2 Looking for your pat…	1.34:1	3.0:1	#000000	#122722	Fail
h2 Latest News	1.34:1	3.0:1	#000000	#122722	Fail
h2 About UAB	1.34:1	3.0:1	#000000	#122722	Fail
h2 Privacy at UAB	1.34:1	3.0:1	#000000	#122722	Fail
h2 Privacy Preference C…	1.34:1	3.0:1	#000000	#122722	Fail
h3 Manage Consent Prefe…	1.34:1	3.0:1	#000000	#122722	Fail
h3 Performance Cookies	1.34:1	3.0:1	#000000	#122722	Fail
title Home - The Universit…	2.42:1	4.5:1	#000000	#1A5632	Fail
a Jump to navigation	6.73:1	4.5:1	#000000	#769A84	Pass

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 85/100 — 4 failing, 27 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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Apr 21, 2026 `li.tw-relative > div.tw-col-span-2 > div.tw-flex > div`
Apr 20, 2026 `li.tw-relative > div.tw-col-span-2 > div.tw-flex > div`
Apr 21, 2026 `li.tw-relative > div.tw-col-span-2 > div.tw-flex > div`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.tw-list-none > li.tw-relative > div.tw-overflow-hidden > img.tw-w-full `ul.tw-list-none > li.tw-relative > div.tw-overflow-hidden > img.tw-w-full`
ul.tw-list-none > li.tw-relative > div.tw-overflow-hidden > img.tw-w-full `ul.tw-list-none > li.tw-relative > div.tw-overflow-hidden > img.tw-w-full`
ul.tw-list-none > li.tw-relative > div.tw-overflow-hidden > img.tw-w-full `ul.tw-list-none > li.tw-relative > div.tw-overflow-hidden > img.tw-w-full`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tw-relative > div.md:tw-grid > div.md:tw-col-span-2 > iframe.ratio `div.tw-relative > div.md:tw-grid > div.md:tw-col-span-2 > iframe.ratio`

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.tw-bg-white > div#main-nav > div > a `div.tw-bg-white > div#main-nav > div > a`
li.tw-relative > div.tw-col-span-2 > div.tw-text-right > a.stretched-link `li.tw-relative > div.tw-col-span-2 > div.tw-text-right > a.stretched-link`
li.tw-relative > div.tw-col-span-2 > div.tw-text-right > a.stretched-link `li.tw-relative > div.tw-col-span-2 > div.tw-text-right > a.stretched-link`
li.tw-relative > div.tw-col-span-2 > div.tw-text-right > a.stretched-link `li.tw-relative > div.tw-col-span-2 > div.tw-text-right > a.stretched-link`

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.

○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

●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

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

●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

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○No form fields have multiple labels

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

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

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <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

Form Accessibility

1 of 10 controls have issues

PASS

1 of 10 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="text" name="vendor-search-handler" id="vendor-search-handler">

9 control(s) properly labeled

10 controls

9 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#gsc-i-id1	text	search	aria-label
#ot-group-id-C0005	checkbox	Social Media Cookies	for/id
#ot-group-id-C0003	checkbox	Functionality Cookies	for/id
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0004	checkbox	Advertising Cookies	for/id
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#vendor-search-handler	text	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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