Skip to content
https://figma.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #ffffff
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Favicon & Branding
14 icon(s) detected
REVIEW
14 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Figma
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Figma ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Figma Display Mode standalone Theme Color #000000 Background Color #000000 Icons 3 icon(s)
A
Landmark Structure
17 landmarks
PASS
17 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
4 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main" MAIN CONTENTINFO footer

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
41 headings
PASS
41 headings
Info::
Single H1 present
  • H2 Use cases
  • H2 Roles
  • H2 Organizations
  • H2 Get started
  • H2 Learn
  • H1 Make anything possible, all in Figma
  • H2 Prompt, code, and design from first idea to final product
  • H2 Bring everyone together with systems that scale
  • H3 Share libraries and design systems across teams.
  • H3 Unlock your team with on-brand templates.
  • H3 Create one source of truth for devs and designers.
  • H2 Ship products, any way you want
  • H3 Turn Figma context into code
  • H3 Publish custom websites—with or without code
  • H3 Ship products faster with AI
  • H2 Explore what people are making
  • H3 Virtual Teleportation Portal App
  • H3 Bubbles Design System
  • H3 Virtual Graffiti Wall
  • H3 Pixel Editor
  • H3 Cursor Images
  • H3 Pattern Generator
  • H3 Flower Catcher
  • H3 Earworm Studio
  • H2 Start with a template. Make just about anything.
  • H3 Websites
  • H3 Social media
  • H3 Mobile apps
  • H3 Presentations
  • H3 Invitations
  • H3 Illustrations
  • H3 Portfolio templates
  • H3 Plugins
  • H3 Web ads
  • H3 Icons
  • H2 Figma Socials
  • H2 Product
  • H2 Plans
  • H2 Use cases
  • H2 Resources
  • H2 Company
A
Alt Text Quality
All 120 images OK
PASS
All 120 images OK
Info::
36 image(s) with alt text over 125 characters
Info::
22 decorative image(s) correctly marked
Info::
62 image(s) with good alt text
120 images 62 good alt text 22 decorative
IssueCount
too long36 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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)
ElementRatioRequiredFGBGResult
h1 Make anything possib…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Use cases21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Roles21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Organizations21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get started21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Learn21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Prompt, code, and de…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bring everyone toget…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ship products, any w…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Start with a templat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Figma Socials21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Product21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Plans21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Use cases21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Share libraries and …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Unlock your team wit…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Create one source of…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Virtual Teleportatio…21.00:13.0: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.

A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 29 passed
PASS
97

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.

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
Masaya Takizawa ul.fig-ge4hzg > li > article > a.fig-9ka48u
Raul Marin Calleja ul.fig-ge4hzg > li > article > a.fig-9ka48u
Seungmee Lee ul.fig-ge4hzg > li > article > a.fig-9ka48u
Ayaneshu Bhardwaj ul.fig-ge4hzg > li > article > a.fig-9ka48u
Gui Seiz ul.fig-ge4hzg > li > article > a.fig-9ka48u
Benjamin Leonard ul.fig-ge4hzg > li > article > a.fig-9ka48u
Nayli C. Naza ul.fig-ge4hzg > li > article > a.fig-9ka48u
Holly Li ul.fig-ge4hzg > li > article > a.fig-9ka48u

These items highlight common accessibility best practices.

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
English div.fig-19c8ja > div.fig-17o2drt > div.fig-79elbk > button.fig-xhgx56
○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
●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
●`[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
●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
●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 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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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 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
○Links are distinguishable without relying on color.
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○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.

Send Feedback