Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DHeading HierarchyAction37 headings, 1 skip(s)FIX
- H1 (empty)
- H1 (empty)
- H4 Info For skipped
- H4 Resources
- H4 Info For
- H4 Resources
- H3 (empty)
- H2 (empty)
- H2 (empty)
- H2 SUMMER CLASSES
- H2 News
- H3 Study: How Can Grocers Cut Food Waste? Discounts, Displays Matter
- H3 Neuroscience Students Win Goldwater Scholarships
- H3 Protein Engineering Method May Lead To More Exact Treatments of Diseases
- H3 Most Vital Key for This Choir Is Creating Harmony in Connections
- H2 Campus Features
- H2 Explore Our Campus
- H2 Housing & Campus Life
- H2 International Appeal
- H2 Athletics & Recreation
- H2 You Are Welcome Here
- H2 Roadmap 2030
- H3 Charting UT Dallas’ Course Together
- H2 Events
- H3 Microsoft AI Skills Day
- H3 Comet Cents: Financing a Home
- H3 Comet Tennis
- H3 A Shared Goal: The 2026 World Cup and North America Unity
- H3 Springapalooza
- H2 Fast Facts
- H2 My UTD
- H2 UTD Campaign
- H3 New Dimensions
- H2 Contact
- H2 Copyright Information
- H2 Stay Connected with UT Dallas
- H2 Resources
A page should have only one H1. Multiple H1s dilute the document outline.
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.
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.
Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.
Source: WCAG 2.4.6
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BAlt Text Quality2 of 21 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 2 image(s) |
Images without alt text are invisible to screen readers.
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
BLink & Button Quality2 issue(s) across 122 links and 7 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.utdallas.edu/ | (empty) | empty | Add link text or aria-label |
| https://www.utdallas.edu/ | (empty) | empty | Add link text or aria-label |
| https://www.utsystem.edu/ | UT System, new tab | new tab | Add '(opens in new tab)' to text |
| https://veterans.portal.texas.gov/ | Texas Veterans Portal, new tab | new tab | Add '(opens in new tab)' to text |
Links without text are announced as raw URLs by screen readers.
https://www.utdallas.edu/; https://www.utdallas.edu/
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.utsystem.edu/; https://veterans.portal.texas.gov/
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
B404 Error PageHTTP 404, custom pageREVIEW
BFavicon & Branding4 icon(s) detectedREVIEW
BWeb ManifestValid manifestREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 12 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
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 Explore Our Campus | 2.45:1 | 3.0:1 | #000000 | #4C4C4C | Fail |
| h2 Fast Facts | 2.45:1 | 3.0:1 | #000000 | #4C4C4C | Fail |
| h2 Contact | 2.45:1 | 3.0:1 | #000000 | #4C4C4C | Fail |
| h2 Copyright Informatio… | 2.45:1 | 3.0:1 | #000000 | #4C4C4C | Fail |
| h2 Stay Connected with … | 2.45:1 | 3.0:1 | #000000 | #4C4C4C | Fail |
| h2 Resources | 2.45:1 | 3.0:1 | #000000 | #4C4C4C | Fail |
| h3 Charting UT Dallas… | 2.45:1 | 3.0:1 | #000000 | #4C4C4C | Fail |
| h3 New Dimensions | 2.45:1 | 3.0:1 | #000000 | #4C4C4C | Fail |
| title The University of Te… | 6.98:1 | 4.5:1 | #000000 | #E87500 | Pass |
| a Skip to main content | 3.76:1 | 4.5:1 | #000000 | #9B570E | Fail |
| h4 Info For | 1.41:1 | 3.0:1 | #000000 | #2E261D | Fail |
| a Students | 1.51:1 | 4.5:1 | #000000 | #362929 | Fail |
| a Faculty & Staff | 4.64:1 | 4.5:1 | #000000 | #857271 | Pass |
| a Alumni | 1.42:1 | 4.5:1 | #000000 | #2A2538 | Fail |
| a Family & Visitors | 4.66:1 | 4.5:1 | #000000 | #7B7579 | Pass |
| a DFW Community | 14.87:1 | 4.5:1 | #000000 | #E2D7D1 | Pass |
| h4 Resources | 15.65:1 | 3.0:1 | #000000 | #E5DDD6 | Pass |
| a Galaxy Login | 12.44:1 | 4.5:1 | #000000 | #CAC7C0 | Pass |
| a eLearning | 15.58:1 | 4.5:1 | #000000 | #E3DDD6 | Pass |
| a CourseBook | 12.96:1 | 4.5:1 | #000000 | #DBC7C2 | 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+Landmark Structure5 landmarksPASS
A+Form AccessibilityAll 1 controls labeledPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #wp-block-search__input-1 | search | Search | for/id |
A+Lighthouse Accessibility AuditsScore 96/100 — 2 failing, 26 passedPASS
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
MENU div.tmenu-search > section#mobile-main-nav > button.navbar-toggler > span.menu-word |
These are opportunities to improve the legibility of your content.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
MENU div.col-sm-12 > div.tmenu-search > section#mobile-main-nav > button.navbar-toggler |
ROADMAP 2030 SITE div.wp-block-columns > div.wp-block-column > p#block_b147ef8ab02d1beb27575da99c97aa6e > a |