Skip to content
https://linear.app

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-y3v99c
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://linear.app/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://linear.app/manifest.json

Manifest contains invalid JSON.

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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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.
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #08090a ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Purpose-built for modern teams with AI w…
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Make product operations self-driving
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Define the product direction
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Move work forward across teams and agen…
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Review PRs and agent output
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Understand progress at scale
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Changelog
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built for the future. Available today.
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Faster app launch
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Product
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Features
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Company
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Resources
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Connect
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Legal
1.07:1
#000000
on
#0A0B0C
needs 3.0:1 (large text)
19px · bottom of viewport
title Linear – The system for product develo…
1.05:1
#000000
on
#08090A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content →
1.06:1
#000000
on
#09090A
needs 4.5:1 (normal text)
16px · top of page (header area)
button Product
1.05:1
#000000
on
#08090A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Product
1.05:1
#000000
on
#08090A
needs 4.5:1 (normal text)
16px · top of page (header area)
button Resources
1.05:1
#000000
on
#08090A
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Purpose-built for mo…1.07:13.0:1
#000000
#0A0B0C
Fail
h2 Make product operat…1.07:13.0:1
#000000
#0A0B0C
Fail
h2 Define the product …1.07:13.0:1
#000000
#0A0B0C
Fail
h2 Move work forward a…1.07:13.0:1
#000000
#0A0B0C
Fail
h2 Review PRs and agent…1.07:13.0:1
#000000
#0A0B0C
Fail
h2 Understand progress…1.07:13.0:1
#000000
#0A0B0C
Fail
h2 Changelog1.07:13.0:1
#000000
#0A0B0C
Fail
h2 Built for the future…1.07:13.0:1
#000000
#0A0B0C
Fail
h3 Faster app launch1.07:13.0:1
#000000
#0A0B0C
Fail
h3 Product1.07:13.0:1
#000000
#0A0B0C
Fail
h3 Features1.07:13.0:1
#000000
#0A0B0C
Fail
h3 Company1.07:13.0:1
#000000
#0A0B0C
Fail
h3 Resources1.07:13.0:1
#000000
#0A0B0C
Fail
h3 Connect1.07:13.0:1
#000000
#0A0B0C
Fail
h3 Legal1.07:13.0:1
#000000
#0A0B0C
Fail
title Linear – The syste…1.05:14.5:1
#000000
#08090A
Fail
a Skip to content →1.06:14.5:1
#000000
#09090A
Fail
button Product1.05:14.5:1
#000000
#08090A
Fail
a Product1.05:14.5:1
#000000
#08090A
Fail
button Resources1.05:14.5:1
#000000
#08090A
Fail

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.

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 6 failing, 19 passed
REVIEW
79

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > ul.Header_list__gT80u > li.Header_mobileItem__Prlve > button.Header_mobileMenuTrigger__ignIg div > ul.Header_list__gT80u > li.Header_mobileItem__Prlve > button.Header_mobileMenuTrigger__ignIg
div > header.IssueView_header__sldQv > div.Flex_root__DOQCW > button.SharedViewStyles_buttonBase__MNsrT div > header.IssueView_header__sldQv > div.Flex_root__DOQCW > button.SharedViewStyles_buttonBase__MNsrT
div.IssueView_chatBox__mNYgF > div.IssueView_commentBoxContainer__EA6vv > div.IssueView_commentActions__ximTU > button.IssueView_commentButton__vzh05 div.IssueView_chatBox__mNYgF > div.IssueView_commentBoxContainer__EA6vv > div.IssueView_commentActions__ximTU > button.IssueView_commentButton__vzh05
div.IssueView_chatBox__mNYgF > div.IssueView_commentBoxContainer__EA6vv > div.IssueView_commentActions__ximTU > button.IssueView_commentButton__vzh05 div.IssueView_chatBox__mNYgF > div.IssueView_commentBoxContainer__EA6vv > div.IssueView_commentActions__ximTU > button.IssueView_commentButton__vzh05
div.SlackIssue_slackBoxContainer__e8FUr > div.SlackIssue_slackBox__GIILV > header.SlackIssue_header__NtjDx > button.IconButton_root__vP_d_ div.SlackIssue_slackBoxContainer__e8FUr > div.SlackIssue_slackBox__GIILV > header.SlackIssue_header__NtjDx > button.IconButton_root__vP_d_

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.Layout_container__BVtmP > main.Layout_content__PrPCk > div.LayoutContent_root__ZBUya > a.Logos_logosLink__k61eG div.Layout_container__BVtmP > main.Layout_content__PrPCk > div.LayoutContent_root__ZBUya > a.Logos_logosLink__k61eG

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.

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
1.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0
2.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0
3.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0
4.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0
5.0 div.PageSection_actionWrapper__SpZEC > a.Link_root__cNtak > div.PageSection_action__7OSHK > span.sc-d5151d0-0

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Faster app launch div.SharedViewStyles_wrapperWithSidebar__mgB8H > div > div.IssueView_body___grLQ > h3.sc-d5151d0-0

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Log in Sign up nav.Header_menuRoot__tJRFd > div.Header_innerWrapper__jlvRl > div > ul.Header_list__gT80u

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Log in ul.Header_list__gT80u > div.Header_rightSideWrapper__v4fej > div.Header_buttons__qwTPf > li.Header_buttonItem__crtcc
Sign up ul.Header_list__gT80u > div.Header_rightSideWrapper__v4fej > div.Header_buttons__qwTPf > li.Header_buttonItem__crtcc

These are opportunities to improve the experience of reading tabular or list data using 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
●Image elements have `[alt]` attributes
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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
○`<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
○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.
○Skip links are focusable.
○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.
A
Landmark Structure
15 landmarks
PASS
15 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <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
17 headings, 1 skip(s)
PASS
17 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 The productdevelopmentsystem for teamsand agentsThe product developmentsystem for teams and agentsThe product development system for teams and agents
  • H3 Faster app launch skipped
  • H4 Activity
  • H2 A new species of product tool. Purpose-built for modern teams with AI workflows at its core, Linear sets a new standard for planning and building products.
  • H2 Make product operations self-driving
  • H2 Define the product direction
  • H2 Move work forward across teams and agents
  • H2 Review PRs and agent output
  • H2 Understand progress at scale
  • H2 Changelog
  • H2 Built for the future. Available today.
  • H3 Product
  • H3 Features
  • H3 Company
  • H3 Resources
  • H3 Connect
  • H3 Legal

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Alt Text Quality
All 31 images OK
PASS
All 31 images OK
Info::
17 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
31 images 14 good alt text 17 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#radix-_R_lphbinpfcqlbH2_textAgents Command Menufor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback