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 4 REVIEW 4 FIX

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 ✗

Link & Button Quality

4 issue(s) across 126 links and 9 buttons

REVIEW

4 issue(s) across 126 links and 9 buttons

1 link(s) with no accessible text

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

Got: https://www.thetrevorproject.org

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.thetrevorproject.org/blog/the-trevor-project-condemns-supreme-cou… ("Learn More"); https://www.thetrevorproject.org/press/ ("Learn More")

1 button(s) with no accessible text

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

Got: button.topbar-control-opener (#139 on page)

123 link(s) with descriptive text

126 links

1 empty

2 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.thetrevorproject.org/blog/th…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: The Trevor Project Condemns Supreme Court Decision To Treat Debunked Practice Of Conversion Therapy As Protected Speech
https://www.thetrevorproject.org/press/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Press
https://www.thetrevorproject.org	(empty)	empty	Add link 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.

https://www.thetrevorproject.org

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

Generic link text like 'click here' doesn't describe the destination.

https://www.thetrevorproject.org/blog/the-trevor-project-condemns-supreme-cou… ("Learn More"); https://www.thetrevorproject.org/press/ ("Learn More")

Why this matters

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

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

button.topbar-control-opener (#139 on page)

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

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | The Trevor Project ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 11 fail WCAG AA

REVIEW

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

9 pass 11 fail WCAG AA 8 pass AA only

h1 You deserve a

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

32px · bottom of viewport

h2 The Trevor Project Condemns Supreme Cour…

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Learn and explore with The Trevor Projec…

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Featured Resources

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Be a fundraiser.

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Advocate for change.

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Volunteer your time.

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Work at The Trevor Project.

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Quick Exit

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Reach out to one of our trained counselo…

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Join The Trevor Project's mission for al…

2.34:1

#000000

#62413B

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 You deserve a	2.34:1	3.0:1	#000000	#62413B	Fail
h2 The Trevor Project C…	2.34:1	3.0:1	#000000	#62413B	Fail
h2 Learn and explore wi…	2.34:1	3.0:1	#000000	#62413B	Fail
h2 Featured Resources	2.34:1	3.0:1	#000000	#62413B	Fail
h2 Be a fundraiser.	2.34:1	3.0:1	#000000	#62413B	Fail
h2 Advocate for change.	2.34:1	3.0:1	#000000	#62413B	Fail
h2 Volunteer your time.	2.34:1	3.0:1	#000000	#62413B	Fail
h2 Work at The Trevor P…	2.34:1	3.0:1	#000000	#62413B	Fail
h2 Quick Exit	2.34:1	3.0:1	#000000	#62413B	Fail
h3 Reach out to one of …	2.34:1	3.0:1	#000000	#62413B	Fail
h3 Join The Trevor Proj…	2.34:1	3.0:1	#000000	#62413B	Fail
title The Trevor Project -…	5.55:1	4.5:1	#000000	#E55040	Pass
p You are using an	5.55:1	4.5:1	#000000	#E55040	Pass
strong outdated	5.55:1	3.0:1	#000000	#E55040	Pass
p browser. Please	5.55:1	4.5:1	#000000	#E55040	Pass
a upgrade your browser	5.55:1	4.5:1	#000000	#E55040	Pass
p to improve your expe…	5.55:1	4.5:1	#000000	#E55040	Pass
a Skip to main	5.55:1	4.5:1	#000000	#E55040	Pass
a Donate	5.55:1	4.5:1	#000000	#E55040	Pass
a Reach A Counselor	5.55:1	4.5:1	#000000	#E55040	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

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <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

11 headings

PASS

11 headings

Single H1 present

H1 You deserve a welcoming, loving world.
H2 The Trevor Project Condemns Supreme Court Decision to Treat Debunked Practice of Conversion Therapy as Protected Speech
H3 Reach out to one of our trained counselors.
H2 Learn and explore with The Trevor Project's resource center
H2 Featured Resources
H3 Join The Trevor Project's mission for all young LGBTQ+ lives.
H2 Be a fundraiser.
H2 Advocate for change.
H2 Volunteer your time.
H2 Work at The Trevor Project.
H2 Quick Exit

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

10 decorative image(s) correctly marked

6 image(s) with good alt text

16 images 6 good alt text 10 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: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#newsletter	email	Email Address	for/id
#g-recaptcha-response-100000	textarea	(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

A+

Lighthouse Accessibility Audits

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

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
And so do the people you care about. Here you can reach out to a counselor if y… `div.page-header > div.page-header-inner > div.page-header-content-wrap > p.page-header-desc`
day or night. `div.messaging > div.messaging__container > p.messaging__title > tilt`

These are opportunities to improve the legibility of your content.

○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

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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