slicer.devRecord your own journeyOnboarding entry
7 pages · linear.app · shared view
Audit report
78UX scoreaudited 3d ago
Flow
100
Copy
78
Usability
65
UI
82
A11y
52
Overall review
The experience works, but accessibility, decision-making and clarity need attention in key moments.
Top issues
1Usability1 · Linear – The system for
The hero lacks a task-focused next step
The opening area explains the category and shows a large product preview, but its only prominent action is the global “Sign up” control in the header. The contextual link in the hero is a small “New Loops →” announcement rather than a path to understand or try the core product.
“Sign up”
2Usability1 · Linear – The system for
The product preview is shown without an outcome summary
The hero devotes most of its visual weight to a detailed issue screen involving an agent, activity updates, changed files, and a draft PR. There is no nearby visible caption that summarizes the workflow or tells a new visitor what result this example demonstrates.
3Copy1 · Linear – The system for
The floating “New Loops” link has little context
“New Loops →” appears by itself at the far right of the hero, separated from both the headline and the product preview. The label identifies something as new but does not explain what Loops are or why they relate to the main product promise.
4Copy2 · Linear – Plan and naviga
The hero states a theme but not the product value
The hero shows “Planning and monitoring” and “Plan and navigate from idea to launch,” but provides no supporting sentence explaining what Linear does differently or which planning capabilities are included.
5Usability2 · Linear – Plan and naviga
The hero has no nearby next step
The hero’s main content ends at the headline. The only visible actions are account controls in the global header, while product-specific exploration begins farther down the page.
All findings
A11y
A button has no clear name
A button has no clear name
WCAG 4.1.2
A11y
A link has no clear destination
A link has no clear destination
WCAG 2.4.4
A11y
Text is difficult to read
Text is difficult to read
WCAG 1.4.3
A11y
Text below 12px
Text below 12px
“Opus 5”
- font size
- 11px
- elements affected
- 27
A11y
Small tap target
Small tap target
- width
- 14px
- height
- 14px
- minimum
- 24
- elements affected
- 6
WCAG 2.5.8
A11y
Heading levels skip a rank
Heading levels skip a rank
“Faster app launch”
Usability
The section control looks like a small text label
Beside the Projects introduction, “Projects +” is rendered as a very small, low-emphasis control without explanatory wording. Its purpose is not evident from the static state.
A11y
Text is difficult to read
Text is difficult to read
WCAG 1.4.3
A11y
Text below 12px
Text below 12px
“APP”
- font size
- 10px
Usability
Email hover feedback is barely visible
The recorded hover state for “Continue with email” changes from white to only a very light gray, making the interaction feedback easy to miss.
“Continue with email”
UI
Legal links wrap awkwardly
The narrow consent block breaks “Terms of Service” across lines and crowds both linked document names into a small two-line area.
A11y
Text is difficult to read
Text is difficult to read
WCAG 1.4.3
A11y
Zooming and scaling must not be disabled
Zooming and scaling must not be disabled
WCAG 1.4.4
UI
Large empty card areas reduce browsing density
Each documentation card reserves roughly half its height for a small icon and otherwise empty space. On the first desktop view, only one complete row and part of the next row are visible despite the concise card content.
Copy
The Teams card cuts off its description
The visible Teams card ends with “different types of wor...” while neighboring card descriptions are shown as complete thoughts.
Usability
Web app action overshadows the downloads
Under “Download Linear,” the only prominent hero button is “Open Web app.” The macOS and Windows download actions are smaller and placed farther down the page.
“Open Web app”
Usability
Desktop compatibility details are missing
The complete download page offers separate macOS and Windows downloads but does not show supported operating-system versions, processor architecture, or a link to compatibility requirements.
“Linear Desktop.”
A11y
Text is difficult to read
Text is difficult to read
WCAG 1.4.3
A11y
List structure may confuse screen readers
List structure may confuse screen readers
WCAG 1.3.1
A11y
Heading levels skip a rank
Heading levels skip a rank
“Product”
Copy
The plan-limit link is easy to overlook
The introductory callout says plan details are available “below,” with only that small word acting as the link. The destination is specifically the Team limits section, but the label does not say so.
UI
The product screenshots are too small to explain the interface
Both embedded product screenshots show a large portion of the application scaled into the article column. Most interface labels and controls are too small to read in the captured desktop page.
UI
The light screenshot overwhelms the dark article
The Team documents screenshot is a large, nearly white rectangle within the dark documentation page, while its actual UI details remain small.
Copy
Link text does not describe its destination
Link text does not describe its destination
“here”
WCAG 2.4.4
A11y
A button has no clear name
A button has no clear name
WCAG 4.1.2
A11y
Interactive controls must not be nested
Interactive controls must not be nested
WCAG 4.1.2
Copy
The opening sentence misnames the agreement
The page title says “DPA,” while the opening sentence calls it “This Data Processing DPA.” The visible date label also has an unnecessary space before the colon: “SIGNED: MAY 31, 2025” is the conventional form.
“This Data Processing DPA (“DPA”) supplements the Terms of Service”
Usability
Exhibit C is missing from the contents list
The visible contents list ends with Exhibit A and Exhibit B, although the supplied document content later includes an Exhibit C containing technical and organizational security measures.
Usability
The long agreement has no visible document actions
The captured title and contents area provides section links but no visible way to download, print, or search the agreement.
“DPA”
A11y
Text is difficult to read
Text is difficult to read
WCAG 1.4.3