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

2 icon(s) detected

FIX

2 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

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ 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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #161cbb

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 ModePartial Dark Mode

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

Action

7 issue(s) across 129 links and 7 buttons

REVIEW

7 issue(s) across 129 links and 7 buttons

7 link(s) with no accessible text

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

Got: /; /safety; /ads/quests; https://support.discord.com/hc/; /blog; /developers; https://discord.com/

12 link(s) open in new tab without warning

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

Got: https://twitter.com/discord; https://www.instagram.com/discord/; https://www.facebook.com/discord/; https://www.youtube.com/discord; https://www.tiktok.com/@discord; https://discordmerch.com/evergreenfooter; https://x.com/discord; https://www.instagram.com/discord/; https://www.facebook.com/discord/; https://www.youtube.com/discord (+2 more)

110 link(s) with descriptive text

129 links

7 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/safety	(empty)	empty	Add link text or aria-label
/ads/quests	(empty)	empty	Add link text or aria-label
https://support.discord.com/hc/	(empty)	empty	Add link text or aria-label
/blog	(empty)	empty	Add link text or aria-label
/developers	(empty)	empty	Add link text or aria-label
https://discord.com/	(empty)	empty	Add link text or aria-label
https://twitter.com/discord	Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/discord/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/discord/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/discord	Youtube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@discord	Tiktok	new tab	Add '(opens in new tab)' to text
https://discordmerch.com/evergreenfooter	Official 3rd Party Merch	new tab	Add '(opens in new tab)' to text
https://x.com/discord	Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/discord/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/discord/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/discord	Youtube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@discord	Tiktok	new tab	Add '(opens in new tab)' to text
https://discord.com/privacy	More information about your pr…	new tab	Add '(opens in new tab)' to text

117 links and buttons have descriptive text

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

/; /safety; /ads/quests; https://support.discord.com/hc/; /blog; /developers; https://discord.com/

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

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

https://twitter.com/discord; https://www.instagram.com/discord/; https://www.facebook.com/discord/; https://www.youtube.com/discord; https://www.tiktok.com/@discord; https://discordmerch.com/evergreenfooter; https://x.com/discord; https://www.instagram.com/discord/; https://www.facebook.com/discord/; https://www.youtube.com/discord (+2 more)

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

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 | Discord ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA

title Discord - Group Chat That’s All Fun & …

1.04:1

#000000

#020322

needs 4.5:1 (normal text)

16px · top of page (header area)

div Skip to main content

1.06:1

#000000

#04052C

needs 4.5:1 (normal text)

16px · top of page (header area)

a Download

1.09:1

#000000

#060736

needs 4.5:1 (normal text)

16px · top of page (header area)

span 1 of 9

1.14:1

#000000

#080B42

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Group chat that’s …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 find your friends on…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 MAKE YOUR GROUP CHAT…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 stream like you’re…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Hop in when you're f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 See who's around to …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 always have somethin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 wherever YOU GAME, H…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 YOU CAN'T SCROLL	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ANYMORE.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 BETTER GO CHAT.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discord	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Product	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Company	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Policies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Discord - Group Chat…	1.04:1	4.5:1	#000000	#020322	Fail
div Skip to main content	1.06:1	4.5:1	#000000	#04052C	Fail
a Download	1.09:1	4.5:1	#000000	#060736	Fail
span 1 of 9	1.14:1	4.5:1	#000000	#080B42	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

20 landmarks

PASS

20 landmarks

<main> landmark present

15 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H1 Group chat that’s all fun & games
H2 find your friends on discord.
H2 MAKE YOUR GROUP CHATS MORE FUN
H2 stream like you’re in the same room
H2 Hop in when you're free, no need to call
H2 See who's around to chill
H2 always have something to do together
H2 wherever YOU GAME, HANG OUT HERE
H2 YOU CAN'T SCROLL ANYMORE.BETTER GO CHAT.
H3 Product
H3 Company
H3 Resources
H3 Policies
H2 Discord

A+

Alt Text Quality

All 170 images OK

PASS

All 170 images OK

149 decorative image(s) correctly marked

21 image(s) with good alt text

170 images 21 good alt text 149 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 24 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
Privacy Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

These are opportunities to improve the legibility of your content.

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
Privacy Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●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

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

○`[accesskey]` values are unique

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○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

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