atlassian.net Accessibility Report

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

Technology
0 /100
C Needs Improvement

6 issues found across 2 categories

5 Major 1 Minor

WCAG Compliance Overview

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

Issues Found

Heading levels skip order

Major

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

WCAG 1.3.1
3 element(s) affected
  • <h5> "Jira" (after h2)
  • <h5> "Jira" (after h2)
  • <h4> "Recommended" (after h1)
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.

Invalid ARIA attributes

Major

ARIA attributes must be valid and used correctly to work with assistive technologies.

WCAG 4.1.2
15 element(s) affected
  • <a aria-labelledby="Learnmore-:R1pl9ddaq: title-:R1pl9ddaq:"> (missing ref)
  • <a aria-labelledby="Learnmore-:R1ql9ddaq: title-:R1ql9ddaq:"> (missing ref)
  • <a aria-labelledby="Learnmore-:R1rl9ddaq: title-:R1rl9ddaq:"> (missing ref)
  • <a aria-labelledby="Learnmore-:R39tdaq: title-:R39tdaq:"> (missing ref)
  • <a aria-labelledby="Learnmore-:R59tdaq: title-:R59tdaq:"> (missing ref)
How to fix

Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

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="/platform">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.net should make to improve accessibility:

  1. #1
    Duplicate element IDs Major

    Make each id attribute value unique within the page.

  2. #2
    Invalid ARIA attributes Major

    Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

  3. #3
    Heading levels skip order Major

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

Frequently Asked Questions

Is atlassian.net accessible?

atlassian.net scored 57/100 (grade C) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is atlassian.net WCAG compliant?

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

Is atlassian.net EAA compliant?

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

What accessibility issues does atlassian.net have?

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

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing