Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 4 REVIEW 2 FIX

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 ✗

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Sorry, We Can’t Find That Page! - 988 Lifeline ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: 988 Lifeline

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name 988 Lifeline ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name 988 Lifeline Display Mode standalone Theme Color #001A4E Background Color #001A4E Icons 2 icon(s)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #001a4e ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA

h2 If you need to talk, the 988 Lifeline is…

1.13:1

#000000

#0A1326

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What to Expect

1.13:1

#000000

#0A1326

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Find Support for a Friend or Loved One

1.13:1

#000000

#0A1326

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get in Touch

1.13:1

#000000

#0A1326

needs 3.0:1 (large text)

24px · bottom of viewport

h2 You are opening a new tab.

1.13:1

#000000

#0A1326

needs 3.0:1 (large text)

24px · bottom of viewport

title 988 Lifeline - If you need emotional sup…

4.20:1

#000000

#0278A0

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 988 Lifeline	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 If you need to talk,…	1.13:1	3.0:1	#000000	#0A1326	Fail
h2 What to Expect	1.13:1	3.0:1	#000000	#0A1326	Fail
h2 Find Support for a F…	1.13:1	3.0:1	#000000	#0A1326	Fail
h2 Get in Touch	1.13:1	3.0:1	#000000	#0A1326	Fail
h2 You are opening a ne…	1.13:1	3.0:1	#000000	#0A1326	Fail
title 988 Lifeline - If yo…	4.20:1	4.5:1	#000000	#0278A0	Fail
a Skip to content	8.24:1	4.5:1	#000000	#62ACC6	Pass
p ¡Los servicios de t…	19.77:1	4.5:1	#000000	#F2F9FF	Pass
a Call	19.77:1	4.5:1	#000000	#F2F9FF	Pass
a Text	19.77:1	4.5:1	#000000	#F2F9FF	Pass
a Chat	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Deaf/HoH	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Menu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Close Menu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Call	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Text	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Chat	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Deaf/HoH	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	21.00:1	4.5: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.

Landmark Structure

17 landmarks

PASS

17 landmarks

<main> landmark present

9 <nav> landmark(s) found

2 of 9 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

6 headings

PASS

6 headings

Single H1 present

H1 988 Lifeline
H2 If you need to talk, the 988 Lifeline is here.
H2 What to Expect
H2 Find Support for a Friend or Loved One
H2 Get in Touch
H2 You are opening a new tab.

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

4 decorative image(s) correctly marked

4 images 4 decorative

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <select name="lang_choice_1" id="lang_choice_1">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search-form-1	search	Search for:	for/id
#lang_choice_1	select	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

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

Link & Button Quality

105 links, 19 buttons — all OK

PASS

105 links, 19 buttons — all OK

8 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.hhs.gov/vulnerability-disclosure-policy/index.html; https://www.instagram.com/988lifeline/; https://www.facebook.com/988lifeline/; https://www.youtube.com/988Lifeline; https://twitter.com/988Lifeline; https://facebook.com/sharer/sharer.php?u=https://988lifeline.org/; https://twitter.com/intent/tweet/?text=988 Lifeline&url=https://988lifeline.org/; https://www.linkedin.com/shareArticle?mini=true&url=https://988lifeline.org/&…

97 link(s) with descriptive text

105 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.hhs.gov/vulnerability-disclo…	Vulnerability Disclosure Polic…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/988lifeline/	See988 LifelineonInstagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/988lifeline/	See988 LifelineonFacebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/988Lifeline	See988 LifelineonYouTube	new tab	Add '(opens in new tab)' to text
https://twitter.com/988Lifeline	See988 LifelineonX	new tab	Add '(opens in new tab)' to text
https://facebook.com/sharer/sharer.php?u…	Share on Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/intent/tweet/?text=9…	Share on Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/shareArticle?mi…	Share on LinkedIn	new tab	Add '(opens in new tab)' to text

116 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.hhs.gov/vulnerability-disclosure-policy/index.html; https://www.instagram.com/988lifeline/; https://www.facebook.com/988lifeline/; https://www.youtube.com/988Lifeline; https://twitter.com/988Lifeline; https://facebook.com/sharer/sharer.php?u=https://988lifeline.org/; https://twitter.com/intent/tweet/?text=988 Lifeline&url=https://988lifeline.org/; https://www.linkedin.com/shareArticle?mini=true&url=https://988lifeline.org/&…

Why this matters

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

Favicon & Branding

7 icon(s) detected

PASS

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 26 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.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English Español `div.header__inner-wrap > div.header__lang-switcher > div.input-container > select#lang_choice_1`

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

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

●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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

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