Skip to content
https://atlassian.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Heading Hierarchy
Action
76 headings, 3 skip(s)
FIX
76 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Featured apps
  • H2 Atlassian Collections
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H2 By Use Case
  • H2 By Team
  • H2 By Size
  • H2 By Industry
  • H3 Rovo
  • H2 Support
  • H2 Resources
  • H2 Featured apps
  • H5 Jira skipped
  • H5 Confluence
  • H5 Jira Service Management
  • H2 Atlassian Collections
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H2 By Use Case
  • H2 By Team
  • H2 By Size
  • H2 By Industry
  • H3 Rovo
  • H2 Featured apps
  • H5 Jira skipped
  • H5 Confluence
  • H5 Jira Service Management
  • H2 Atlassian Collections
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H3 Rovo
  • H2 By Use Case
  • H2 By Team
  • H2 By Size
  • H2 By Industry
  • H3 Rovo
  • H2 Unlock human-AI collaboration at scale
  • H1 Unleash yourhuman+AIhuman+AI superteam
  • H2 Hot off the press: What’s new in AI?
  • H1 The Teamwork platform built for the AI-era duplicate H1
  • H2 Teamwork solutions for high-performing teams
  • H3 Dream it, plan it, launch it
  • H3 Create and organize with AI
  • H3 Deliver service faster
  • H3 Record, share, collaborate
  • H3 Ideate faster than ever
  • H2 Teams across the globe run on Atlassian
  • H2 Empower everyone, on every team
  • H3 Supercharge dev productivity
  • H2 Get started with a template
  • H3 Scrum
  • H3 Bug Tracking
  • H3 DevOps
  • H2 For teams of all sizes
  • H2 Help us shape the future of teamwork
  • H2 Unleash the power of teamworkteamwork
  • H2 Products
  • H2 Resources
  • H2 Learn
  • H2 Manage Preferences
  • H4 Strictly Necessary Cookies skipped
  • H4 Targeting Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H3 Cookie List

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title | Atlassian ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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
h1 Unleash your
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
32px · bottom of viewport
h1 superteam
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
32px · bottom of viewport
h1 The
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
32px · bottom of viewport
h1 platform built for the AI-era
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Featured apps
1.12:1
#000000
on
#101214
needs 3.0:1 (large text)
24px · above the fold
h2 Atlassian Collections
1.11:1
#000000
on
#0F1113
needs 3.0:1 (large text)
24px · mid-page
h2 By Use Case
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 By Team
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 By Size
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 By Industry
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Support
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured apps
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Atlassian Collections
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 By Use Case
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 By Team
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 By Size
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 By Industry
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured apps
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Atlassian Collections
1.31:1
#000000
on
#252117
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Unleash your1.31:13.0:1
#000000
#252117
Fail
h1 superteam1.31:13.0:1
#000000
#252117
Fail
h1 The1.31:13.0:1
#000000
#252117
Fail
h1 platform built for t…1.31:13.0:1
#000000
#252117
Fail
h2 Featured apps1.12:13.0:1
#000000
#101214
Fail
h2 Atlassian Collection…1.11:13.0:1
#000000
#0F1113
Fail
h2 By Use Case1.31:13.0:1
#000000
#252117
Fail
h2 By Team1.31:13.0:1
#000000
#252117
Fail
h2 By Size1.31:13.0:1
#000000
#252117
Fail
h2 By Industry1.31:13.0:1
#000000
#252117
Fail
h2 Support1.31:13.0:1
#000000
#252117
Fail
h2 Resources1.31:13.0:1
#000000
#252117
Fail
h2 Featured apps1.31:13.0:1
#000000
#252117
Fail
h2 Atlassian Collection…1.31:13.0:1
#000000
#252117
Fail
h2 By Use Case1.31:13.0:1
#000000
#252117
Fail
h2 By Team1.31:13.0:1
#000000
#252117
Fail
h2 By Size1.31:13.0:1
#000000
#252117
Fail
h2 By Industry1.31:13.0:1
#000000
#252117
Fail
h2 Featured apps1.31:13.0:1
#000000
#252117
Fail
h2 Atlassian Collection…1.31:13.0:1
#000000
#252117
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.

A
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) 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+
Alt Text Quality
All 67 images OK
PASS
All 67 images OK
Info::
44 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
67 images 23 good alt text 44 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 10 controls have issues
PASS
1 of 10 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::
9 control(s) properly labeled
10 controls
9 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#language-dropdowntextChoose your languagearia-label
#ot-group-id-4checkboxTargeting Cookiesfor/id
#ot-group-id-3checkboxFunctional Cookiesfor/id
#ot-group-id-2checkboxPerformance Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#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
Lighthouse Accessibility Audits
Score 91/100 — 4 failing, 27 passed
PASS
91

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Bug Tracking Seamlessly report, track, and prioritize bugs to address developm… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
DevOps Develop, deploy, and manage applications with an open tools approach T… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide

These are opportunities to improve the usage of ARIA in your application which 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
Watch the full video div._19pkidpf > div.link-wrapper > a#Watchthefullvideo-:r0: > span

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content div._1e0cglyw > nav._11q7cd5j > div._18zrpxbi > a._kqswstnw

These are opportunities to improve keyboard navigation in your application.

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
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Read their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Read their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
See their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Get it free div._kqswh2mm > div._101fkb7n > div._1e0c1txw > a._4cvr1h6o
Read their story. div._101fkb7n > div._1e0c1txw > p._19pkidpf > a._4bfu1r31
○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
●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
●`[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
●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
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[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 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
○No form fields have multiple labels
○`<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
○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.
○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