atlassian.com Accessibility Report

Accessibility audit of atlassian.com — scanned on Feb 20, 2026

Technology
0 /100
D Poor

7 issues found across 3 categories

2 Critical 4 Major 1 Minor

WCAG Compliance Overview

Perceivable 3 issues
Operable 2 issues
Understandable 0 issues
Robust 2 issues

Issues Found

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
2 element(s) affected
  • <button>
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Videos missing captions

Critical

Video content must have captions for deaf and hard-of-hearing users.

WCAG 1.2.2
1 element(s) affected
  • <video> "https://dam-cdn.atl.orangelogic.com/AssetLink/kb8y65md2n1k70"
How to fix

Add closed captions or subtitles to all video content.

Heading levels skip order

Major

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
2 element(s) affected
  • <h5> "Jira" (after h2)
  • <h5> "Jira" (after h2)
How to fix

Restructure headings to follow sequential order. Don't skip from h1 to h3.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
91 element(s) affected
  • id="jira"
  • id="collectionsoftware"
  • id="softwareTitle"
  • id="confluence"
  • id="collectionteamwork"
How to fix

Make each id attribute value unique within the page.

Positive tabindex values

Major

Elements with tabindex > 0 disrupt natural tab order and confuse keyboard users.

WCAG 2.4.3
2 element(s) affected
  • <a tabindex="1">
  • <a tabindex="1">
How to fix

Remove positive tabindex values. Use tabindex="0" or tabindex="-1" only.

Generic link text

Major

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
1 element(s) affected
  • <a href="/collections/teamwork">learn more</a>
How to fix

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Incorrect list structure

Minor

List items must be contained within <ul>, <ol>, or <dl> elements.

WCAG 1.3.1
15 element(s) affected
  • <li> inside <div>
How to fix

Ensure <li> elements are direct children of <ul> or <ol>.

Top Priority Fixes

Here are the most impactful changes atlassian.com should make to improve accessibility:

  1. #1
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

  2. #2
    Videos missing captions Critical

    Add closed captions or subtitles to all video content.

  3. #3
    Duplicate element IDs Major

    Make each id attribute value unique within the page.

Frequently Asked Questions

Is atlassian.com accessible?

atlassian.com scored 35/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is atlassian.com WCAG compliant?

Our scan found 7 accessibility issues on atlassian.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is atlassian.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see atlassian.com's compliance status.

What accessibility issues does atlassian.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for atlassian.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing