slicer.devRecord your own journeyGetting started
6 pages · figma.com · shared view
Audit report
72UX scoreaudited 3d ago
Flow
100
Copy
67
Usability
53
UI
73
A11y
65
Overall review
The experience works, but decision-making, accessibility and clarity need attention in key moments.
Top issues
1UI1 · Figma: The collaborative
Feature demos render as large blank areas
Several feature sections show almost entirely white space where the page markup identifies video regions; only headings and small play controls remain visible. This occurs in the workspace, AI-native canvas, and precision sections.
2Copy1 · Figma: The collaborative
The hero does not explain what the canvas does
The main headline says “The intelligent canvas for infinite creativity,” but no supporting sentence is visible beside it. The collage suggests multiple creative tools without clearly stating the product’s core design, collaboration, development, or AI workflow.
3Usability1 · Figma: The collaborative
The primary hero action skips the demo path
The hero’s prominent action is “Get started,” while the header emphasizes “Get started for free” and “Contact sales.” There is no clearly labeled demo or product-tour action in the captured first screen.
“Get started”
4Copy1 · Figma: The collaborative
The hero drops the “free” qualifier from signup
The header says “Get started for free,” while the equally prominent hero button says only “Get started.” The captured markup points both actions to signup destinations, but their visible wording differs.
5Copy2 · Plans & Pricing | Figma
Plan prices do not say they are per seat
The plan cards show amounts such as “$16/mo,” “$55/mo,” and “$90/mo” beside seat types, while annual billing is indicated separately. The visible pricing does not explicitly state whether each amount is per seat.
All findings
UI
Tiny product icons make seat contents hard to compare
Each paid seat lists included products mainly as a row of small colored icons. Their names appear only in a separate legend above the cards, so readers must repeatedly match icons to labels across a wide layout.
Usability
Annual pricing hides the annual total
Annual billing is selected for Professional and required for Organization and Enterprise, but the cards show only monthly-equivalent amounts such as “$16/mo” and “$55/mo.” No annual total is visible in the primary comparison.
A11y
Text below 12px
Text below 12px
“Seat”
- font size
- 11px
A11y
Heading levels skip a rank
Heading levels skip a rank
“Starter”
Copy
The signup step does not say whether it creates an account
The page is titled “Sign Up for Figma,” but the visible heading only says “Welcome to Figma,” and both actions use the neutral word “Continue.” The screen does not visibly distinguish account creation from signing in.
“Welcome to Figma”
A11y
Text below 12px
Text below 12px
“Email”
- font size
- 11px
A11y
Zooming and scaling must not be disabled
Zooming and scaling must not be disabled
WCAG 1.4.4
Usability
The form asks prospects to choose a plan before sales helps them choose
The introduction says sales can “help you choose the right plan,” but “What Figma plan are you inquiring about?” is shown as a required field. The captured closed dropdown does not reveal whether an unsure option exists.
Copy
The sales form gives no visible follow-up expectation
The captured contact section explains what sales can help with and provides a form, but it does not visibly say what happens after submission or give a response-time expectation.
Usability
Support is offered three times around the sales form
The screen presents “Get product or account support” with a “Get support” link, then “Visit our Support Hub” above the form, and another technical or product support link below it. These routes use different labels despite serving closely related needs.
A11y
A form field is missing a label
A form field is missing a label
WCAG 4.1.2
A11y
Text below 12px
Text below 12px
“Work email address”
- font size
- 11px
- elements affected
- 8
A11y
Heading levels skip a rank
Heading levels skip a rank
“Talk to a member of our sales team”
Usability
The hero offers signup before showing the product
The opening screen explains that Figma supports many design use cases, but the only prominent page action is “Get started.” No demo, product tour, or concrete workflow preview is visible in this decision area.
UI
The AI sections read like link directories
“Build faster with Figma AI” and “Build faster with Figma's agent” present dense four-column lists of similarly styled links, with little visible explanation of how the groups differ or which path is best for a particular goal.
UI
The credit banner covers the next section heading
The fixed green credit announcement sits across the bottom of the desktop viewport and visibly overlaps the “Build faster with Figma AI” heading. A dismiss control is available at the far right.
“AI add-ons now come with 2x more credits on Professional, and 1.6x more on Organization and Enterprise.”
Usability
Runtime failures on page load
Runtime failures on page load
Copy
Link text does not describe its destination
Link text does not describe its destination
“Learn more”
WCAG 2.4.4
A11y
A link has no clear destination
A link has no clear destination
WCAG 2.4.4
Usability
The hero does not lead to a demo
The opening promises a library of on-demand demos, but the hero contains no demo CTA, featured demo, or category links. The first choices appear only after scrolling into Field Notes.
“See Figma in action”
Usability
Specialized Org content comes before the product overview
The first three demos are Field Notes about design systems and Figma Org administration. The broader “Figma platform overview” and “Figma deep dive” appear in the following section.
“Field Notes”
Usability
Demo cards omit viewing time
The visible cards explain each demo’s subject but provide no duration or comparable time commitment near “Watch the demo.”
Usability
The same CTA hides different destinations
Field Notes use “Watch the demo” links to Figma pages, while the Figma and Dev Mode demo cards use the same wording for Vimeo destinations. The visible labels do not distinguish these paths.
Usability
Runtime failures on page load
Runtime failures on page load
A11y
A form field is missing a label
A form field is missing a label
WCAG 4.1.2
A11y
Text below 12px
Text below 12px
“Work email address”
- font size
- 11px
- elements affected
- 8