Skip to content
https://atlassian.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
8
REVIEW
0
PASS
5
INFO
0
Checks
13
5 PASS 8 FIX
D
Heading Hierarchy
Action
66 headings, 4 skip(s)
FIX
66 headings, 4 skip(s)
Info::
Single H1 present
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: H1 → H4 (missing H2)
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 Great outcomes start with Jira
  • H1 Explore Atlassian products
  • H4 Recommended skipped
  • H4 Collections
  • H2 Explore by role
  • H3 Atlassian Cloud Platform
  • H3 Additional resources
  • H3 Marketplace
  • H3 Community
  • H3 Find a partner
  • 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

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

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
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-on2e9p
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
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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://atlassian.net/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://atlassian.net/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::
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.
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 40 images OK
PASS
All 40 images OK
Info::
6 decorative image(s) correctly marked
Info::
34 image(s) with good alt text
40 images 34 good alt text 6 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+
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 Explore Atlassian pr…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Featured apps18.60:13.0:1
#000000
#E9F2FE
Pass
h2 Atlassian Collection…17.94:13.0:1
#000000
#E5EEFA
Pass
h2 By Use Case19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Team19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Size19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Industry19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Support19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Resources19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Featured apps19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Atlassian Collection…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Use Case19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Team19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Size19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Industry19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Featured apps19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Atlassian Collection…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Use Case19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Team19.09:13.0:1
#000000
#F4F4F4
Pass
h2 By Size19.09:13.0:1
#000000
#F4F4F4
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 96/100 — 3 failing, 30 passed
PASS
96

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

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

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
Recommended div._1e1faxbu > div._1e0c1txw > div._1e0c1txw > h4#Recommended-:r23:

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
Atlassian Cookies and Tracking Notice div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●`<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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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.
○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