Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Link & Button Quality

Action

3 issue(s) across 14 links and 7 buttons

REVIEW

3 issue(s) across 14 links and 7 buttons

2 link(s) with no accessible text

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

Got: /; /

9 link(s) open in new tab without warning

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

Got: https://newsroom.snap.com/?lang=en-US; https://investor.snap.com/overview/default.aspx?lang=en-US; https://careers.snap.com/?lang=en-US; https://www.snapchat.com/?lang=en-US; https://www.spectacles.com/?lang=en-US; https://ar.snap.com/lens-studio?lang=en-US; https://citizen.snap.com/?utm_source=snap_com&utm_medium=referral&utm_campaig…; https://values.snap.com/privacy/privacy-policy?utm_source=snap_com&utm_medium…; https://www.snap.com/cookie-policy?lang=en-US

1 button(s) with no accessible text

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

Got: button.css-12z3p7m (#199 on page)

3 link(s) with descriptive text

14 links

2 empty

0 generic text

9 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://newsroom.snap.com/?lang=en-US	NEWS	new tab	Add '(opens in new tab)' to text
https://investor.snap.com/overview/defau…	INVESTORS	new tab	Add '(opens in new tab)' to text
https://careers.snap.com/?lang=en-US	CAREERS	new tab	Add '(opens in new tab)' to text
https://www.snapchat.com/?lang=en-US	Snapchat is a visual messaging…	new tab	Add '(opens in new tab)' to text
https://www.spectacles.com/?lang=en-US	Spectacles make computing more…	new tab	Add '(opens in new tab)' to text
https://ar.snap.com/lens-studio?lang=en-…	Lens Studio is a creative tool…	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
https://citizen.snap.com/?utm_source=sna…	CitizenSnap	new tab	Add '(opens in new tab)' to text
https://values.snap.com/privacy/privacy-…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.snap.com/cookie-policy?lang=…	Cookie Policy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

9 links and buttons have descriptive text

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

/; /

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://newsroom.snap.com/?lang=en-US; https://investor.snap.com/overview/default.aspx?lang=en-US; https://careers.snap.com/?lang=en-US; https://www.snapchat.com/?lang=en-US; https://www.spectacles.com/?lang=en-US; https://ar.snap.com/lens-studio?lang=en-US; https://citizen.snap.com/?utm_source=snap_com&utm_medium=referral&utm_campaig…; https://values.snap.com/privacy/privacy-policy?utm_source=snap_com&utm_medium…; https://www.snap.com/cookie-policy?lang=en-US

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

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

button.css-12z3p7m (#199 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

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 13 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 We contribute to hum…	5.32:1	3.0:1	#000000	#808080	Pass
h2 Cookies	5.32:1	3.0:1	#000000	#808080	Pass
h3 Cookies help us:	5.32:1	3.0:1	#000000	#808080	Pass
title We are Snap Inc.	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span NEWS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span INVESTORS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span CAREERS	9.90:1	4.5:1	#000000	#B2B2B2	Pass
div OUR PRODUCTS & SERVI…	5.32:1	4.5:1	#000000	#808080	Pass
p Snapchat is a visual…	5.32:1	4.5:1	#000000	#808080	Pass
p Spectacles make comp…	5.32:1	4.5:1	#000000	#808080	Pass
p Lens Studio is a cre…	5.32:1	4.5:1	#000000	#808080	Pass
a CitizenSnap	5.32:1	4.5:1	#000000	#808080	Pass
a Other Terms & Polici…	5.32:1	4.5:1	#000000	#808080	Pass
a Privacy Policy	5.32:1	4.5:1	#000000	#808080	Pass
a Terms of Service	5.32:1	4.5:1	#000000	#808080	Pass
label Language	5.32:1	4.5:1	#000000	#808080	Pass
button English (US)	5.32:1	4.5:1	#000000	#808080	Pass
button English (US)	5.32:1	4.5:1	#000000	#808080	Pass
p Power this website a…	5.32:1	4.5:1	#000000	#808080	Pass
p Remember your prefer…	5.32:1	4.5:1	#000000	#808080	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.

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 23 passed

REVIEW

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
nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8 `nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8`
nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8 `nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8`
nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8 `nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8`
English (US) `li#2GC85My5nmT83kImSgBtt4 > div.css-1jnci4s > div.sdsm-dropdown-menu > button.sdsm-default`
English (US) `div.modal-header > div.locale-container > div.sdsm-dropdown-menu > button.sdsm-dropdown-button`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.sdsm-footer-bar > ul.css-1wmipba > li > a.css-u550gm `div.sdsm-footer-bar > ul.css-1wmipba > li > a.css-u550gm`

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
nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8 `nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8`
nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8 `nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8`
nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8 `nav.css-1q2lbmy > ul.css-3ityw4 > li > button.css-o1iof8`

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

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

●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

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

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

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

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

3 headings

PASS

3 headings

Single H1 present

H1 We contribute to human progress by empowering people to express themselves, live in the moment, learn about the world, and have fun together.
H2 Cookies
H3 Cookies help us:

A+

Alt Text Quality

1 of 4 images have issues

PASS

1 of 4 images have issues

1 image(s) with generic alt text

3 decorative image(s) correctly marked

4 images 3 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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