Skip to content
https://rice.edu

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
1
PASS
6
INFO
0
Checks
13
6 PASS 1 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 406, bare page
FIX
HTTP 406, bare page
Warning::
Unexpected status code: HTTP 406
Expected HTTP 404 but received 406. This may confuse search engine crawlers.
Got: HTTP 406
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 406 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
No dark mode signals
FIX
No dark mode signals
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 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.

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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
A
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
3 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
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

A
Heading Hierarchy
34 headings, 1 skip(s)
PASS
34 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Main Nav
  • H1 Rice University
  • H2 Rice alumna plays key role in NASA’s Artemis II lunar mission
  • H2 Rice graduate programs earn strong national rankings in latest US News listing
  • H2 Rice’s Kinder Institute secures future and advances solutions for Houston with $55M Kinder Foundation grant
  • H2 Rice named Official Houston World Cup 2026 Host City Supporter
  • H2 Rice University Gateway Project to connect campus with Rice Village, modernize Rice Stadium
  • H2 Page Link Cards
  • H5 Academics skipped
  • H5 Centers and Institutes
  • H5 Graduate Programs
  • H5 Majors, Minors and Programs
  • H5 Dean of Undergraduates
  • H2 Rice Research
  • H2 RICE MAGAZINE
  • H2 Advancing Discovery Through Interdisciplinary Research
  • H2 TOP RESEARCH FINDINGS
  • H3 Cancer Research
  • H3 SUSTAINABLE FUTURES
  • H3 ENERGY
  • H3 HEALTH INNOVATIONS
  • H3 ARTIFICIAL INTELLIGENCE
  • H3 BUILD THRIVING URBAN COMMUNITIES
  • H2 WHERE OUR RESEARCH DOLLARS GO
  • H3 Research Project Staffing Costs
  • H3 Student Summer Stipends
  • H3 Research Equipment & Supplies
  • H3 Research & Conference Travel
  • H3 SUPPORTING GRADUATE STUDENT RESEARCH
  • H3 Facility Operating Costs
  • H3 Research Data & Computing Infrastructure
  • H3 Administrative Salaries & Expenses
  • H3 Compliance & Safety Costs
  • H2 RICE RESEARCH REVIEW (R3)

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

A+
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
7 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
24 images 17 good alt text 7 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#gsc-i-id1textsearcharia-label
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Rice University21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Main Nav21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rice alumna plays ke…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rice graduate progra…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rice’s Kinder Inst…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rice named Official …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rice University Gate…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Page Link Cards21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Rice Research21.00:13.0:1
#000000
#FFFFFF
Pass
h2 RICE MAGAZINE17.64:13.0:1
#13133E
#FFFFFF
Pass
h2 Advancing Discovery …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 TOP RESEARCH FINDING…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 WHERE OUR RESEARCH D…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 RICE RESEARCH REVIEW…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cancer Research21.00:13.0:1
#000000
#FFFFFF
Pass
h3 SUSTAINABLE FUTURES21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ENERGY21.00:13.0:1
#000000
#FFFFFF
Pass
h3 HEALTH INNOVATIONS21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ARTIFICIAL INTELLIGE…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 BUILD THRIVING URBAN…21.00:13.0:1
#000000
#FFFFFF
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
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 26 passed
PASS
92

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.menu__search > div.search > form > button#search-close div.menu__search > div.search > form > button#search-close
div.container > div.grid-pv > div.js-rice-news > button.slick-prev div.container > div.grid-pv > div.js-rice-news > button.slick-prev
div.container > div.grid-pv > div.js-rice-news > button.slick-next div.container > div.grid-pv > div.js-rice-news > button.slick-next

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
MENTAL HEALTH RESOURCES div.footer__content > div.footer--content-box > nav.footer__menu > a.menu__item

These items highlight common accessibility best practices.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Explore the Winter 2026 Issue (opens in a new window) div.res2-row-some-page-wrapper > div.res2-column-some-page-wrapper > div.green-column > a.responsive-button
○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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●Links are distinguishable without relying on color.
●Links have a discernible name
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○ARIA IDs are unique
○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
○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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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