Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 6 REVIEW 5 FIX

Alt Text Quality

Action

2 of 18 images have issues

FIX

2 of 18 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

2 decorative image(s) correctly marked

14 image(s) with good alt text

18 images 14 good alt text 2 decorative 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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

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.

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 ✗

Heading Hierarchy

10 headings

REVIEW

10 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Bag
H3 Culture fit tee in blue $35
H3 Culture fit tee in yellow $35
H3 Culture fit tee in violet $35
H2 Shop apparel
H2 Shop accessories
H2 Shop past collections
H2 100% of profits go to carbon removal
H2 Sign up to be the first to know about new items
H2 Search

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Form Accessibility

2 of 4 controls have issues

REVIEW

2 of 4 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="text">; <input type="email" name="contact[email]" id="newsletter-email-sections--27031286120819__figma_newsletter_signup_pn4gCL">

2 control(s) properly labeled

4 controls

2 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
contact[accepts_marketing]	checkbox		none
#cmdk-input	search	Search	for/id
input	text	(Search)	placeholder only
#newsletter-email-sections--27031286120819__figma_newsletter_signup_pn4gCL	email	(Email)	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

Link & Button Quality

Action

2 issue(s) across 41 links and 241 buttons

REVIEW

2 issue(s) across 41 links and 241 buttons

2 link(s) with no accessible text

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

Got: /collections/apparel; /collections/accessories

12 link(s) open in new tab without warning

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

Got: https://program.tist.org/; /policies/terms-of-service; /policies/privacy-policy; https://x.com/figma; https://www.instagram.com/figma/; https://www.youtube.com/channel/UCQsVmhSa4X-G3lHlUtejzLA; https://www.facebook.com/figmadesign/; https://harperandscott.com; https://www.bcorporation.net/en-us/find-a-b-corp/company/harper-scott; https://harperandscott.com (+2 more)

27 link(s) with descriptive text

41 links

2 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/collections/apparel	(empty)	empty	Add link text or aria-label
/collections/accessories	(empty)	empty	Add link text or aria-label
https://program.tist.org/	Learn more about TIST	new tab	Add '(opens in new tab)' to text
/policies/terms-of-service	TOS	new tab	Add '(opens in new tab)' to text
/policies/privacy-policy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://x.com/figma	Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/figma/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCQsVmhS…	Youtube	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/figmadesign/	Social Media	new tab	Add '(opens in new tab)' to text
https://harperandscott.com	Harper + Scott	new tab	Add '(opens in new tab)' to text
https://www.bcorporation.net/en-us/find-…	Certified B-Corporation	new tab	Add '(opens in new tab)' to text
https://harperandscott.com	Harper + Scott	new tab	Add '(opens in new tab)' to text
https://cdn.shopify.com/s/files/1/0590/0…	CSR policy	new tab	Add '(opens in new tab)' to text
https://figma.com	Figma.com	new tab	Add '(opens in new tab)' to text

268 links and buttons have descriptive text

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

/collections/apparel; /collections/accessories

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://program.tist.org/; /policies/terms-of-service; /policies/privacy-policy; https://x.com/figma; https://www.instagram.com/figma/; https://www.youtube.com/channel/UCQsVmhSa4X-G3lHlUtejzLA; https://www.facebook.com/figmadesign/; https://harperandscott.com; https://www.bcorporation.net/en-us/find-a-b-corp/company/harper-scott; https://harperandscott.com (+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

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 404 Not Found – The Figma Store ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 25 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.

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
©2025 Figma `footer.ftr-footer-wrapper > div.ftr-menu-box > div.ftr-bottom-section > div.ftr-copyright`

These are opportunities to improve the legibility of your content.

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.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`
div.sc-category-card > a.sc-category-link > div.sc-image-container > img `div.sc-category-card > a.sc-category-link > div.sc-image-container > img`

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.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link `div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link`
div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link `div.max-w-screen-2xl > div.sc-cards-wrapper > div.sc-category-card > a.sc-category-link`

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

●Form elements have associated labels

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○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

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

No banner (header) landmark

Skip navigation link present

Search landmark 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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Bag	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop apparel	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop accessories	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shop past collection…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 100% of profits go t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Sign up to be the fi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Search	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Culture fit tee in b…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Culture fit tee in y…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Culture fit tee in v…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title The Figma Store	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a The Figma Store	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a The Figma Store	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Limited Edition	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span New	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Shop All	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Apparel	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Accessories	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Season 4	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.

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