figma.com

Scanned 24 Oct 2026, 04:53 UTC · 1 page scanned · 1440, 390 and 320 px · 1 min 5 s

2 additional pages not scanned

Not scanned (incomplete capture): https://www.figma.com/design-explore/
Not scanned (time limit): https://www.figma.com/build-ship/

Visit site Markdown JSON

77.8 /100

Grade C

3 fail2 warnings13 pass9 not evaluatedof 27 checks

Failing checks (3)

Measured results, suggested fixes, and the evidence saved for each check.

Failing check · Inclusion · C141.2

Content hidden from screen readers can still take focus

9 focusable elements in hidden content

Content hidden from screen readers must not contain links or buttons that still take focus.

Passes when: Hidden and presentational elements do not conflict with focus or accessibility semantics
Fails when: Hidden content remains focusable, or presentation semantics conflict with an accessible role or name

How to fix it

Remove aria-hidden from containers that hold focusable controls, or make those controls unfocusable while hidden (the inert attribute does both).

Saved evidence 3 element records

Element 2www.figma.com/ · 1440 px viewport

html > body > div:nth-of-type(2) > main > section:nth-of-type(7) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > div > div:nth-of-type(2)

Element 344 × 532 px · x 328, y 6514

Element 3www.figma.com/ · 1440 px viewport

html > body > div:nth-of-type(2) > main > section:nth-of-type(7) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > div > div:nth-of-type(3)

Element 344 × 532 px · x 672, y 6514

Element 1www.figma.com/ · 1440 px viewport

No image saved

html > body > div:nth-of-type(2) > main > section:nth-of-type(7) > div > div:nth-of-type(2) > div:nth-of-type(2) > div > div > div:nth-of-type(10)

Element 344 × 532 px · x 3080, y 6514

Failing check · Inclusion · C160.2

A control’s name leaves out the words shown on it

1 name missing its visible label

A control's accessible name should contain the words people see on it.

Passes when: A control’s accessible name contains its visible label
Fails when: A control’s accessible name omits its visible label

How to fix it

Start the aria-label with the visible text, or remove the aria-label so the visible text becomes the name. Voice-control users say what they see.

Saved evidence 1 element record

Element 1www.figma.com/ · 1440 px viewport

#main

Element 1440 × 7036 px · x 0, y 78

Failing check · Inclusion · C170.2

A live region is invalid or covers too much

1 faulty live region

Live regions must be valid and small, never the whole page.

Passes when: Live regions use valid values and a bounded scope
Fails when: A live-region attribute is invalid, the region is page-level, or its area exceeds half the viewport

How to fix it

Put aria-live on the small element that holds the status message, not on body or main, and use a valid value such as polite.

Saved evidence 1 element record

Element 1www.figma.com/ · 1440 px viewport

No image saved

#_R_1an4lubsodqivb_

Element 1360 × 632 px · x 40, y 6402

Warnings (2)

Warning · Visual communication · C006.1

Supporting text doesn’t look quieter than what it supports

3 supporting texts that don't step back

Captions, hints and footnotes should look quieter than the text they support: smaller, lighter or muted.

Passes when: Supporting text has a quieter cue and no stronger visual cue
Warns when: One or two supporting items have no clear hierarchy cue

How to fix it

Make supporting text at least one step quieter than its primary text: about 0.9× the size, 100 lighter in weight, or a muted colour that still meets 4.5:1 contrast. Never make it larger or bolder than what it supports.

Saved evidence 3 element records

Element 1www.figma.com/ · 1440 px viewport

No image saved

html > body > div:nth-of-type(2) > main > section:nth-of-type(6) > div > div > div:nth-of-type(2) > div:nth-of-type(1) > figure > div > figcaption

Element 672 × 54 px · x 41, y 5982

Supporting text compared with primary

Element 1www.figma.com/ · 390 px viewport

No image saved

html > body > div:nth-of-type(2) > main > section:nth-of-type(6) > div > div > div:nth-of-type(2) > div:nth-of-type(1) > figure > div > figcaption

Element 357 × 68 px · x 17, y 5125

Supporting text compared with primary

Element 1www.figma.com/ · 320 px viewport

No image saved

html > body > div:nth-of-type(2) > main > section:nth-of-type(6) > div > div > div:nth-of-type(2) > div:nth-of-type(1) > figure > div > figcaption

Element 287 × 68 px · x 17, y 4897

Supporting text compared with primary

Warning · Interaction · C108.1

Controls have no visible label

7 controls without a visible label

Fields need visible labels, and icon-only buttons should be few and use familiar icons.

Passes when: Fields are visibly identified and standalone icon controls are clear
Warns when: A nonstandard standalone icon control needs a label

How to fix it

Give every field a visible label, since placeholders vanish while typing. Add text to icon-only buttons, or keep them to familiar icons (search, close, menu) with an accessible name and a tooltip.

Saved evidence 3 element records

Element 1www.figma.com/ · 1440 px viewport

html > body > div:nth-of-type(2) > div:nth-of-type(1) > header > div > div > div > a

Element 19 × 28 px · x 40, y 25

Element 2www.figma.com/ · 1440 px viewport

No image saved

html > body > div:nth-of-type(2) > footer > div > div:nth-of-type(1) > a

Element 120 × 44 px · x 60, y 7235

Element 3www.figma.com/ · 1440 px viewport

No image saved

html > body > div:nth-of-type(2) > footer > div > div:nth-of-type(1) > div > ul > li:nth-of-type(1) > a

Element 36 × 36 px · x 60, y 7317

Passed (13)Show

Not evaluated (9)Show

The other 506 rules of the source taxonomy aren’t part of today’s scan. See the methodology.

Score by domain

Visual communication1 of 3 checks to fix83 /100

Information and findability3 checks, all pass100 /100

Functional and interaction support1 of 1 check to fix50 /100

Inclusion and adaptation3 of 10 checks to fix70 /100

Visual expression1 check, all pass100 /100

Transparency and agencyNot measured—

Essential: 77.8 of 100 points, 18 checks · Recommended: none applied · Bonus: none applied

What this doesn’t cover

Aesthetic judgment, brand intent and designer calibration
Text contrast is not measured yet (the vetted contrast rules are not implemented in this pin)
Briefs, specifications, logins and declared design systems
Form submissions, transactions and activated task flows
Closed shadow roots, cross-origin frame contents and other themes
Rules without a vetted implementation or required measurement
Pages or assets refused by robots.txt or the scan limits

How scores are computed: methodology. Is this your site? Ask us to remove this report.