Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FFavicon & BrandingAction1 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CHeading HierarchyAction27 headings, 2 skip(s)REVIEW
- H1 ASU graduate programs among the nation's best
- H3 Find my degree program skipped
- H2 I am a future
- H2 Stories of excellence
- H3 ASU Health facility is bringing new opportunities
- H3 Students advancing AI for personalized learning
- H3 Barrett, The Honors College is creating bright futures
- H3 ASU leaders earning prestigious roles
- H3 Students showcase tech projects at AZ Tech Week
- H3 ASU named a top producer of prestigious Gilman awards
- H4 The ASU difference:
- H1 We are measured not by whom we exclude, but by whom we include and how they succeed duplicate H1
- H3 Experience world-class academics skipped
- H3 Discovery and innovation that serves the public
- H3 Serving all learners at every stage of life
- H2 Carve your path
- H2 One university, many places
- H1 Polytechnic campus duplicate H1
- H1 Tempe campus duplicate H1
- H1 West Valley campus duplicate H1
- H1 Downtown Phoenix campus duplicate H1
- H1 Skysong duplicate H1
- H1 Los Angeles duplicate H1
- H1 Washington D.C. duplicate H1
- H1 Media and Immersive eXperience (MIX) Center duplicate H1
- H2 Reimagining education for everyone
- H3 New programs for all ages
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
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
BForm Accessibility2 of 9 controls have issuesREVIEW
| Control | Type | Label | Method |
|---|---|---|---|
| #edit-location-inperson | radio | In person | for/id |
| #edit-location-online | radio | Online | for/id |
| #edit-search | text | Search by keyword | for/id |
| #edit-interestarea | select | Search by interest area | for/id |
| #edit-interestarea-online | select | Search by interest area (Online) | for/id |
| #edit-standing-undergrad | radio | Undergraduate | for/id |
| #edit-standing-graduate | radio | Graduate | for/id |
| #edit-submit | submit | (none) | none |
| #edit-reset | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" name="op" id="edit-submit">; <input type="submit" name="button_reset" id="edit-reset">
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
BLink & Button Quality4 issue(s) across 69 links and 10 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /academics | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Academics | |||
| /research | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Research | |||
| https://learning.asu.edu/?_gl=1%2A1t7bt2… | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: ? Gl=1%2a1t7bt29%2a Gcl Au%2amti4otizodg1os4xnzc1mtq4o… | |||
| https://asuforyou.asu.edu/ | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Home page | |||
Generic link text like 'click here' doesn't describe the destination.
/academics ("Learn more"); /research ("Learn more"); https://learning.asu.edu/?_gl=1%2A1t7bt29%2A_gcl_au%2AMTI4OTIzODg1OS4xNzc1MTQ… ("Learn more"); https://asuforyou.asu.edu/ ("Learn more")
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
B404 Error PageHTTP 404, custom pageREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 2 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
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 ASU graduate program… | 1.14:1 | 3.0:1 | #000000 | #181311 | Fail |
| h1 Polytechnic campus | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h1 Tempe campus | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h1 West Valley campus | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h1 Downtown Phoenix cam… | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h1 Skysong | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h1 Los Angeles | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h1 Washington D.C. | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h1 Media and Immersive … | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h2 I am a future | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h2 Carve your path | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h2 Reimagining educatio… | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h3 Find my degree progr… | 1.05:1 | 3.0:1 | #000000 | #06080A | Fail |
| h3 ASU Health facility … | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h3 Students advancing A… | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h3 Barrett, The Honors … | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h3 ASU leaders earning … | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h3 Students showcase te… | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h3 ASU named a top prod… | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | Pass |
| h3 Experience world-cla… | 13.62:1 | 3.0:1 | #000000 | #D0D0D0 | 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.
ALandmark Structure8 landmarksPASS
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
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
A+Alt Text QualityAll 30 images OKPASS
A+Lighthouse Accessibility AuditsScore 96/100 — 2 failing, 31 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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Find my degree program div.row > div.layout__region > div.asu-edu-components-find-my-degree-program > h3 |
Experience world-class academics div.content-section > div.content-holder > div.content-bg > h3 |
These are opportunities to improve keyboard navigation in your application.
Tables and lists
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Slide 1 of 6 div.slider-wrapper > section#main-slider > div.glide__track > ul.glide__slides |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.