Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 1 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-h3zm3i

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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.jira.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.jira.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Link & Button Quality

2 issue(s) across 147 links and 18 buttons

REVIEW

2 issue(s) across 147 links and 18 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /gartner/magic-quadrant-collaborative-work-management ("Learn More")

14 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /software/jira/templates/service-management; /software/jira/templates/service-management; /software/jira/templates/service-management; /blog/announcements/rovo-mcp-gallery; https://investors.atlassian.com; https://www.atlassianfoundation.org/; https://trello.com/home; https://support.atlassian.com/; https://community.atlassian.com/; https://confluence.atlassian.com/kb (+4 more)

1 button(s) with no accessible text

132 link(s) with descriptive text

147 links

0 empty

1 generic text

14 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/software/jira/templates/service-managem…	Jira Service Management templa…	new tab	Add '(opens in new tab)' to text
/software/jira/templates/service-managem…	Jira Service Management templa…	new tab	Add '(opens in new tab)' to text
/software/jira/templates/service-managem…	Jira Service Management templa…	new tab	Add '(opens in new tab)' to text
/gartner/magic-quadrant-collaborative-wo…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Magic Quadrant Collaborative Work Management
/blog/announcements/rovo-mcp-gallery	Learn more about MCP Gallery	new tab	Add '(opens in new tab)' to text
https://investors.atlassian.com	Investor Relations	new tab	Add '(opens in new tab)' to text
https://www.atlassianfoundation.org/	Atlassian Foundation	new tab	Add '(opens in new tab)' to text
https://trello.com/home	Trello	new tab	Add '(opens in new tab)' to text
https://support.atlassian.com/	Technical support	new tab	Add '(opens in new tab)' to text
https://community.atlassian.com/	Atlassian Community	new tab	Add '(opens in new tab)' to text
https://confluence.atlassian.com/kb	Knowledge base	new tab	Add '(opens in new tab)' to text
https://marketplace.atlassian.com/	Marketplace	new tab	Add '(opens in new tab)' to text
https://my.atlassian.com/products/index	My account	new tab	Add '(opens in new tab)' to text
https://support.atlassian.com/contact/	Create support ticket	new tab	Add '(opens in new tab)' to text
https://confluence.atlassian.com/display…	Documentation	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

149 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/gartner/magic-quadrant-collaborative-work-management ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

/software/jira/templates/service-management; /software/jira/templates/service-management; /software/jira/templates/service-management; /blog/announcements/rovo-mcp-gallery; https://investors.atlassian.com; https://www.atlassianfoundation.org/; https://trello.com/home; https://support.atlassian.com/; https://community.atlassian.com/; https://confluence.atlassian.com/kb (+4 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

34 headings

PASS

34 headings

Single H1 present

H2 Teams
H2 Use Cases
H2 Company Size
H2 Teams
H2 Use Cases
H2 Company Size
H2 Teams
H2 Use Cases
H2 Company Size
H1 Focus on outcomes, not admin
H2 Software development
H2 Marketing
H2 Project management
H2 IT
H2 Build your human-AI super team
H3 Atlassian named a Leader in the 2025 Gartner® Magic Quadrant
H2 Where your team and AI come together
H3 Jumpstart planning
H3 Focus on impact
H3 Stay in sync
H2 Meet AI-powered project management
H3 Align work with goals
H3 Plan your project
H3 Automate tedious tasks
H3 Put agents to work
H3 Stay in sync
H3 Learn as you deliver
H3 Bring tools to life with Rovo agents
H2 All your tools, one collection
H2 For teams big and small
H2 No matter what you’re trying to dream up, Jira helps you get it done
H2 Products
H2 Resources
H2 Learn

A+

Alt Text Quality

1 of 31 images have issues

PASS

1 of 31 images have issues

1 image(s) with generic alt text

23 decorative image(s) correctly marked

7 image(s) with good alt text

31 images 7 good alt text 23 decorative 1 generic

Issue	Count
generic	1 image(s)

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 controls have issues

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">

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#autocomplete-4-input	search	Search by Keywords	aria-label
#autocomplete-5-input	search	Search by Keywords	aria-label
#email-uid2	email	Work email*	for/id
#language-dropdown	text	Choose your language	aria-label
#g-recaptcha-response-100000	textarea	(none)	none

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

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)

Element	Ratio	Required	FG	BG	Result
h1 not admin	16.62:1	3.0:1	#101214	#E9F2FE	Pass
h2 Teams	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Use Cases	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Company Size	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Teams	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Use Cases	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Company Size	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Teams	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Use Cases	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Company Size	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Software developme…	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Marketing	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Project management	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Build your human-AI …	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Where your team and …	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Meet AI-powered proj…	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 All your tools, one …	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 For teams big and sm…	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 No matter what you�…	18.60:1	3.0:1	#000000	#E9F2FE	Pass
h2 Products	18.60:1	3.0:1	#000000	#E9F2FE	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 97/100 — 1 failing, 29 passed

PASS

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.

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
Explore goals `div._19pkidpf > div.link-wrapper > a#Exploregoals-:ri: > span`
Explore AI Features `div._19pkidpf > div.link-wrapper > a#ExploreAIFeatures-:rj: > span`
Explore Studio `div._19pkidpf > div.link-wrapper > a#ExploreStudio-:rk: > span`
Explore Agents in Jira `div._19pkidpf > div.link-wrapper > a#ExploreAgentsinJira-:rl: > span`
Explore the Teamwork Graph `div._19pkidpf > div.link-wrapper > a#ExploretheTeamworkGraph-:rm: > span`
Explore all Jira features `div._19pkidpf > div.link-wrapper > a#ExploreallJirafeatures-:rn: > span`
Explore Teamwork Collection `div._19pkidpf > div.link-wrapper > a#ExploreTeamworkCollection-:rp: > span`

These are opportunities to improve the legibility of your content.

○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]` 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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

●No element has a `[tabindex]` value greater than 0

●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

●Elements with visible text labels have matching accessible names.

○`[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

○`[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

○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.