Skip to content
https://ttu.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Heading Hierarchy
Action
126 headings, 7 skip(s)
FIX
126 headings, 7 skip(s)
Warning::
Multiple H1 headings (25 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H3 Undergraduate skipped
  • H3 International
  • H3 Online
  • H3 Graduate
  • H3 School of Law
  • H3 School of Veterinary Medicine
  • H3 Majors & Colleges
  • H3 Office of Research & Innovation
  • H3 Texas Tech Now - Research
  • H3 Innovation Hub
  • H3 Find Funding
  • H3 Develop & Submit Proposal
  • H3 Research Commercialization
  • H3 Discoveries
  • H3 Map
  • H3 University Student Housing
  • H3 Dining on Campus
  • H3 Raider Safety
  • H3 TechThrive
  • H3 University Recreation
  • H3 Student Engagement
  • H3 Student Resources
  • H3 Athletics
  • H3 Shop Official TTU Gear
  • H3 Ticketing
  • H3 Red Raider Club
  • H3 Texas Tech Facts
  • H3 Our Campus
  • H3 Office of the President
  • H3 Office of the Provost
  • H3 News & Updates
  • H3 History & Traditions
  • H3 University Strategic Plan
  • H3 Academic Catalog
  • H3 Academic Calendar
  • H3 Career Opportunities
  • H3 Organizational Chart
  • H3 Undergraduate
  • H3 International
  • H3 Online
  • H3 Graduate
  • H3 School of Law
  • H3 School of Veterinary Medicine
  • H3 Majors & Colleges
  • H1 SEARCH duplicate H1
  • H3 Suggested Topics skipped
  • H3 Undergraduate
  • H3 International
  • H3 Graduate
  • H3 TTU Online
  • H3 TechAlert
  • H1 (empty)
  • H1 Explore Online Programs duplicate H1
  • H2 Get started on the path to your degree.
  • H1 Ready to Become a Red Raider? duplicate H1
  • H2 Start your journey to Possible right here.
  • H1 State of the University duplicate H1
  • H2 Texas Tech President Lawrence Schovanec reflected on accomplishments and outlined goals for the years ahead.
  • H1 Heroes of One Health duplicate H1
  • H2 Texas Tech research highlights how the health of people, animals, and the environment can impact one another.
  • H1 From Veteran to Veterinarian duplicate H1
  • H2 Jovani Armendariz achieves his dream of becoming a veterinarian.
  • H1 Explore Online Programs duplicate H1
  • H2 Get started on the path to your degree.
  • H1 Ready to Become a Red Raider? duplicate H1
  • H2 Start your journey to Possible right here.
  • H1 State of the University duplicate H1
  • H2 Texas Tech President Lawrence Schovanec reflected on accomplishments and outlined goals for the years ahead.
  • H1 Heroes of One Health duplicate H1
  • H2 Texas Tech research highlights how the health of people, animals, and the environment can impact one another.
  • H1 From Veteran to Veterinarian duplicate H1
  • H2 Jovani Armendariz achieves his dream of becoming a veterinarian.
  • H1 Explore Online Programs duplicate H1
  • H2 Get started on the path to your degree.
  • H3 FROM HERE,
  • H3 IT'S POSSIBLE.™
  • H1 I am a: duplicate H1
  • H1 PROSPECTIVE STUDENT duplicate H1
  • H1 Prospective Student duplicate H1
  • H1 Red Raider duplicate H1
  • H1 Parent duplicate H1
  • H1 Visitor duplicate H1
  • H1 Donor duplicate H1
  • H3 Find My Major skipped
  • H3 Financial Aid
  • H3 Schedule a Tour
  • H3 Apply Now
  • H3 Texas Tech Now
  • H3 Red Raider Athletics
  • H3 Event Calendar
  • H3 President’s Report
  • H3 Campus Visit
  • H3 Texas Tech Parents Association
  • H3 Parent & Family Relations
  • H3 Commencement
  • H3 Explore Texas Tech
  • H2 Featured
  • H3 Campus Art Trail
  • H3 Red Raider Athletics
  • H3 Event Calendar
  • H3 OUT HERE WE’RE ALL IN
  • H2 Featured
  • H3 HUCKABEE COLLEGE ALUMNI RAISE FUNDS TO HONOR FORMER PROFESSORS
  • H3 MURRAY RANDLES’S GENEROSITY OPENS NEW OPPORTUNITIES
  • H4 Your support helps students achieve their dreams, fund pioneering research, support faculty, and so much more
  • H3 @TexasTech
  • H3 @TexasTech
  • H1 We’re Here to help you duplicate H1
  • H3 Texas Tech Now skipped
  • H1 Featured News duplicate H1
  • H4 Read more on Texas Tech Now skipped
  • H5 Texas Tech Grad Student Kortnie Koebel Settles In As Miss Lubbock
  • H4 READ MORE
  • H5 Texas Tech Names James Reecy Vice President...
  • H4 READ MORE
  • H5 Two Well-Timed Ads Led Full-Time Working Mom...
  • H4 READ MORE
  • H4 Read on Texas Tech Now
  • H3 Events
  • H1 DISCOVER WHAT'S HAPPENING duplicate H1
  • H2 Texas Tech University
  • H4 STAY CONNECTED skipped
  • H1 (empty)
  • H2 Texas Tech University
  • H4 Follow Texas Tech University skipped

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

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

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

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

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

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

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #e90802
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 7 <nav> element(s)
Back to Top
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.
B
Landmark Structure
12 landmarks
REVIEW
12 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
7 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 SEARCH3.95:13.0:1
#000000
#646B7E
Pass
h1 I am3.95:13.0:1
#000000
#646B7E
Pass
h1 PROSPECTIVE STUDENT3.95:13.0:1
#000000
#646B7E
Pass
h1 Prospective Student3.95:13.0:1
#000000
#646B7E
Pass
h1 Red Raider3.95:13.0:1
#000000
#646B7E
Pass
h1 Parent3.95:13.0:1
#000000
#646B7E
Pass
h1 Visitor3.95:13.0:1
#000000
#646B7E
Pass
h1 Donor3.95:13.0:1
#000000
#646B7E
Pass
h1 We’re Here to help…3.95:13.0:1
#000000
#646B7E
Pass
h1 Featured News3.95:13.0:1
#000000
#646B7E
Pass
h1 DISCOVER WHAT'S HAPP…3.95:13.0:1
#000000
#646B7E
Pass
h2 Get started on the p…3.95:13.0:1
#000000
#646B7E
Pass
h2 Start your journey t…3.95:13.0:1
#000000
#646B7E
Pass
h2 Texas Tech President…3.95:13.0:1
#000000
#646B7E
Pass
h2 Texas Tech research …3.95:13.0:1
#000000
#646B7E
Pass
h2 Jovani Armendariz ac…3.95:13.0:1
#000000
#646B7E
Pass
h2 Get started on the p…3.95:13.0:1
#000000
#646B7E
Pass
h2 Start your journey t…3.95:13.0:1
#000000
#646B7E
Pass
h2 Texas Tech President…3.95:13.0:1
#000000
#646B7E
Pass
h2 Texas Tech research …3.95:13.0:1
#000000
#646B7E
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.

A
Alt Text Quality
1 of 85 images have issues
PASS
1 of 85 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
83 image(s) with good alt text
85 images 83 good alt text 1 decorative 1 missing
IssueCount
missing1 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

A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#gsc-i-id1textsearcharia-label
#gsc-i-id2textsearcharia-label
#gsc-i-id3textsearcharia-label
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 28 passed
PASS
95

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FROM HERE, section#header > div.ttu-hero__fhip > div.black-bg > h3
FIND MY MAJOR div.ttu-headline-ctas__content > div.ttu-headline-ctas-content__txt > a > h3
Texas Tech Now section.ttu__news > div.ttu-news__top > div.ttu-new-top__title > h3
TEXAS TECH NAMES JAMES REECY VICE PRESIDENT... article > div.ttu-news-titles > div.ttu-news-titles__txt > h5
STAY CONNECTED section.ttu-lim-width > div.ttu-footer__slogan > div.ttu-footer__social > h4

These are opportunities to improve keyboard navigation in your application.

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.row > div.large-9 > section.ttu > a.logo-link div.row > div.large-9 > section.ttu > a.logo-link
div.ttu-headline__ctas > ul > li > a div.ttu-headline__ctas > ul > li > a
div.ttu-headline__ctas > ul > li > a div.ttu-headline__ctas > ul > li > a
div.ttu-headline__ctas > ul > li > a div.ttu-headline__ctas > ul > li > a
div.ttu-headline__ctas > ul > li > a div.ttu-headline__ctas > ul > li > 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.

○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
●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
●`[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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[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 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
○`<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.
○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
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.

Send Feedback