Skip to content
https://www.trello.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
1
PASS
6
INFO
0
Checks
13
6 PASS 1 REVIEW 6 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-ettj2j
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
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://www.trello.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://www.trello.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <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.
A
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <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 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
32 headings, 1 skip(s)
PASS
32 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Explore the features that help your team succeed
  • H3 Meet Trello
  • H3 Take a page out of these pre-built Trello playbooks designed for all teams
  • H3 Our product in action
  • H3 Compare plans & pricing
  • H3 Learn & connect
  • H2 Explore the features that help your team succeed
  • H3 Meet Trello
  • H2 Take a page out of these pre-built Trello playbooks designed for all teams
  • H3 Our product in action
  • H3 Compare plans & pricing
  • H2 Learn & connect
  • H3 Helping teams work better, together
  • H1 Capture, organize, and tackle your to-dos from anywhere.
  • H2 Your productivity powerhouse
  • H4 Inbox skipped
  • H4 Boards
  • H4 Planner
  • H4 Inbox
  • H4 Boards
  • H4 Planner
  • H2 From message to action
  • H3 EMAIL MAGIC
  • H3 MESSAGE APP SORCERY
  • H2 Do more with Trello
  • H3 Integrations
  • H3 Automation
  • H3 Card mirroring
  • H3 75% of organizations report that Trello delivers value to their business within 30 days.
  • H3 81% of customers chose Trello for its ease of use.
  • H3 74% of customers say Trello has improved communication with their co-workers and teams.
  • H2 Get started with Trello today

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 13 images OK
PASS
All 13 images OK
Info::
3 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
13 images 10 good alt text 3 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
emailemailEmailaria-label
emailemailEmailaria-label
selectselectSelect a languagearia-label
#g-recaptcha-response-100000textarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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 Capture, organize, a…19.25:13.0:1
#000000
#F4F5F7
Pass
h2 Explore the features…19.25:13.0:1
#000000
#F4F5F7
Pass
h2 Take a page out of t…19.25:13.0:1
#000000
#F4F5F7
Pass
h2 Learn & connect19.25:13.0:1
#000000
#F4F5F7
Pass
h2 Your productivity po…19.25:13.0:1
#000000
#F4F5F7
Pass
h2 Do more with Trello19.25:13.0:1
#000000
#F4F5F7
Pass
h2 Get started with Tre…19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Explore the features…19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Meet Trello19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Take a page out of t…19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Our product in actio…19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Compare plans & pric…19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Learn & connect19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Meet Trello19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Our product in actio…19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Compare plans & pric…19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Helping teams work b…19.25:13.0:1
#000000
#F4F5F7
Pass
h3 EMAIL MAGIC19.25:13.0:1
#000000
#F4F5F7
Pass
h3 MESSAGE APP SORCERY19.25:13.0:1
#000000
#F4F5F7
Pass
h3 Integrations19.25:13.0:1
#000000
#F4F5F7
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 95/100 — 3 failing, 25 passed
PASS
95

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.

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
Inbox div.Carouselstyles__Slide-sc-z6wsqn-3 > button.UiListCarouselstyles__LinkItem-sc-xa0ove-0 > div > h4

These are opportunities to improve keyboard navigation in your application.

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
Dot 2 div.Carouselstyles__Frame-sc-z6wsqn-1 > div.Carouselstyles__Controls-sc-z6wsqn-4 > div.Carouselstyles__Dots-sc-z6wsqn-7 > button.Carouselstyles__Dot-sc-z6wsqn-8
Dot 3 div.Carouselstyles__Frame-sc-z6wsqn-1 > div.Carouselstyles__Controls-sc-z6wsqn-4 > div.Carouselstyles__Dots-sc-z6wsqn-7 > button.Carouselstyles__Dot-sc-z6wsqn-8
Dot 2 div.Carouselstyles__Frame-sc-z6wsqn-1 > div.Carouselstyles__Controls-sc-z6wsqn-4 > div.Carouselstyles__Dots-sc-z6wsqn-7 > button.Carouselstyles__Dot-sc-z6wsqn-8
Dot 3 div.Carouselstyles__Frame-sc-z6wsqn-1 > div.Carouselstyles__Controls-sc-z6wsqn-4 > div.Carouselstyles__Dots-sc-z6wsqn-7 > button.Carouselstyles__Dot-sc-z6wsqn-8

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
Sign up - it’s free! div.grid__StyledColumn-sc-p40pqe-2 > form.UiEmailSignupstyles__Form-sc-9nggyw-0 > div.link-buttonstyles__BxpButton-sc-1utqn26-1 > button
Read the story figure.UiSocialProofstyles__QuoteFigure-sc-fym1cs-4 > figcaption.UiSocialProofstyles__QuoteCaption-sc-fym1cs-3 > div.UiSocialProofstyles__QuoteImageLink-sc-fym1cs-5 > a
Sign up - it’s free! div.grid__StyledColumn-sc-p40pqe-2 > form.UiEmailSignupstyles__Form-sc-9nggyw-0 > div.link-buttonstyles__BxpButton-sc-1utqn26-1 > button
○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
●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.
●Select elements have associated label elements.
●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
●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 are distinguishable without relying on color.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○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.
○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