Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Alt Text Quality

2 of 13 images have issues

REVIEW

2 of 13 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

11 image(s) with good alt text

13 images 11 good alt text 2 missing

Issue	Count
missing	2 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

Link & Button Quality

Action

5 issue(s) across 129 links and 7 buttons

REVIEW

5 issue(s) across 129 links and 7 buttons

2 link(s) with no accessible text

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

Got: a#main-content; https://www.facebook.com/TulaneU

3 button(s) with no accessible text

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

Got: button.h-12 (#94 on page); button.search-close (#97 on page); button#vidbutton

127 link(s) with descriptive text

129 links

2 empty

0 generic text

0 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://www.facebook.com/TulaneU	(empty)	empty	Add link 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

131 links and buttons have descriptive text

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

a#main-content; https://www.facebook.com/TulaneU

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

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

button.h-12 (#94 on page); button.search-close (#97 on page); button#vidbutton

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Make Way for a Parade of Possibilities

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Information for

2.72:1

#000000

#255C4E

needs 3.0:1 (large text)

24px · mid-page

h2 University Info

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Primary Navigation

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Account Login

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Make Way for Your Future at Tulane

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

24px · bottom of viewport

h2 For One's Own

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Quick Links

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 Footer Menu II

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Footer

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Academics

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tulane News

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Social work professor's family-centered�…

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Curiosity drives Hullabaloo editor-in-ch…

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Unified Green initiative to transform up…

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Community Table Talks foster connection …

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tulane graduate turns personal health jo…

2.97:1

#000000

#005AA0

needs 3.0:1 (large text)

19px · bottom of viewport

title Tulane University: Leading Research & Ed…

2.40:1

#000000

#21543F

needs 4.5:1 (normal text)

16px · top of page (header area)

div This site uses cookies and similar techn…

2.40:1

#000000

#21543F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Privacy Notice

1.91:1

#000000

#2C4131

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

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
h1 Make Way for a Parad…	2.97:1	3.0:1	#000000	#005AA0	Fail
h2 Information for	2.72:1	3.0:1	#000000	#255C4E	Fail
h2 University Info	2.97:1	3.0:1	#000000	#005AA0	Fail
h2 Primary Navigation	2.97:1	3.0:1	#000000	#005AA0	Fail
h2 Account Login	2.97:1	3.0:1	#000000	#005AA0	Fail
h2 Make Way for Your Fu…	2.97:1	3.0:1	#000000	#005AA0	Fail
h2 For One's Own	2.97:1	3.0:1	#000000	#005AA0	Fail
h2 Quick Links	2.97:1	3.0:1	#000000	#005AA0	Fail
h2 Footer Menu II	2.97:1	3.0:1	#000000	#005AA0	Fail
h2 Footer	2.97:1	3.0:1	#000000	#005AA0	Fail
h3 Academics	2.97:1	3.0:1	#000000	#005AA0	Fail
h3 Tulane News	2.97:1	3.0:1	#000000	#005AA0	Fail
h3 Social work professo…	2.97:1	3.0:1	#000000	#005AA0	Fail
h3 Curiosity drives Hul…	2.97:1	3.0:1	#000000	#005AA0	Fail
h3 Unified Green initia…	2.97:1	3.0:1	#000000	#005AA0	Fail
h3 Community Table Talk…	2.97:1	3.0:1	#000000	#005AA0	Fail
h3 Tulane graduate turn…	2.97:1	3.0:1	#000000	#005AA0	Fail
title Tulane University: L…	2.40:1	4.5:1	#000000	#21543F	Fail
div This site uses cooki…	2.40:1	4.5:1	#000000	#21543F	Fail
a Privacy Notice	1.91:1	4.5:1	#000000	#2C4131	Fail

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 Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

17 headings, 1 skip(s)

PASS

17 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

H2 Information for
H2 University Info
H2 Primary Navigation
H2 Account Login
H1 Make Way for a Parade of Possibilities
H3 Academics skipped
H2 Make Way for Your Future at Tulane
H2 For One's Own
H2 Quick Links
H3 Tulane News
H3 Social work professor's family-centered…
H3 Curiosity drives Hullabaloo editor-in-chief’s…
H3 Unified Green initiative to transform uptown campus
H3 Community Table Talks foster connection and…
H3 Tulane graduate turns personal health journey into…
H2 Footer Menu II
H2 Footer

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

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="q" id="edit-keys">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-keys	search	(Search here ...)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | Tulane University ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 25 passed

PASS

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
ACADEMICS `div > div.paragraph > div.max-w-[700px] > h3.should-inherit`

These are opportunities to improve keyboard navigation in your application.

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
div#block-footerlogoandtext > div.tulane-logo-svg-text-block > div.col-span-1 > img `div#block-footerlogoandtext > div.tulane-logo-svg-text-block > div.col-span-1 > img`
div#block-footerlogoandtext > div.tulane-logo-svg-text-block > div.col-span-2 > img `div#block-footerlogoandtext > div.tulane-logo-svg-text-block > div.col-span-2 > img`

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
READ MORE NEWS `div.layout__region > div.views-element-container > div > button.btn-tulane`
READ MORE NEWS `div.views-element-container > div > button.btn-tulane > a`
504-865-5000 `div.text-sm > div > p > a`

These items highlight common accessibility best practices.

○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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[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

○ARIA IDs are unique

○No form fields have multiple labels

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

○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

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

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

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