Accessibility

F

Heading Hierarchy

Action

73 headings, 16 skip(s)

FIX

73 headings, 16 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Code and CI/CD, powered by AI and the Atlassian platform
H3 AI throughout the SDLC skipped
H3 Extensible and all-in-one
H3 Platform-wide standards
H2 AI that provides context to code, not just vibes
H2 Migrating to the cloud?
H2 15 million developers build on Bitbucket
H6 1/4 skipped
H3 "The Jira/Bitbucket integration has transformed the way our software teams are able to communicate, work together, and deploy code. It's been an absolute game changer for us."
H5 Nate Van Dusen, Engineering Program Management Director skipped
H6 2/4
H3 "With the integration, it’s possible to link each line of changed code back to a Jira work item, to understand not only what was changed, but why"
H5 Scott Carpenter, Global Cloud Architect skipped
H6 3/4
H3 "Jira and Bitbucket are linked to show details and where the change is in production. It’s traceable, so they know what we’re doing and when we’re deploying."
H5 Kyle Gengler, Senior DevOps Engineer skipped
H6 4/4
H3 "We've gone from one big-bang release every month to 10-20 production deployments per day. We also reduced the average development cycle time from 5.8 days to 2.9 days and the standard deviation from
H5 Roman Bugaev, CTO skipped
H2 Platform-wide AI beyond code generation
H4 Introducing Rovo Dev skipped
H4 AI where you work
H4 AI-powered teams
H4 AI integrations
H2 Security and compliance
H3 Code compliance at scale
H3 Shift-left security integrations
H3 Orchestrate CI/CD organization-wide
H3 Granular access and usage permissions
H2 Integrate Bitbucket with the tools you use
H2 Deliver high quality software. Fast.
H2 Learn more
H3 Migrate to Bitbucket cloud
H3 Scale CI/CD with Bitbucket Pipelines
H3 3X a DevOps Leader
H3 New features on the horizon
H2 Take Bitbucket Cloud for a spin
H2 Power up with Bitbucket Premium
H1 Code & CI/CD, built for teams using Jira duplicate H1
H3 Migrating to cloud? Listen to this webinar on Bitbucket Cloud's enterprise strategy + get migration tips. skipped
H6 PRODUCT FEATURES skipped
H2 Why choose Bitbucket Cloud?
H3 Collaborate across multiple teams
H3 Ship quality code
H3 Automate deployments
H6 watch THE demo skipped
H2 See how Bitbucket Cloud works with Atlassian tools
H6 Secure your code skipped
H2 Collaborate with IT Ops
H2 Secure & compliant
H6 Integrations for every team skipped
H2 Build a DevOps toolchain that works for you
H2 15 million developers from over a million teams love Bitbucket
H6 1 of 4 skipped
H2 “We’ve gone from one big-bang release every month to 10-20 production deployments per day. We also reduced the average development cycle time from 5.8 days to 2.9 days and the standard deviation f
H6 2 of 4 skipped
H2 “The Jira/Bitbucket integration has transformed the way our software teams are able to communicate, work together, and deploy code. It's been an absolute game changer for us.
H6 3 of 4 skipped
H2 “With the integration, it's possible to link each line of changed code back to a Jira issue, to understand not only what was changed, but why.
H6 4 of 4 skipped
H2 “Jira and Bitbucket are linked to show details and where the change is in production. It’s traceable, so they know what we’re doing and when we’re deploying.
H2 Learn more
H3 Need a self-hosted option?
H3 Considering migrating to Bitbucket Cloud?
H3 New features on the horizon
H2 Take Bitbucket Cloud for a spin
H2 Simple plans hosted in the cloud. Priced to scale.
H3 Free
H3 Standard
H3 Premium
H4 Bitbucket
H4 Resources
H4 Connect with us

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

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

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

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

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

D

Form Accessibility

Action

4 of 5 controls have issues

FIX

4 of 5 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <select name="url" id="footer-language-selector">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">; <input type="email" name="et-e3bb2ec9-6479-471c-bdce-76bea62a4c6a" id="et-e3bb2ec9-6479-471c-bdce-76bea62a4c6a">

1 control(s) properly labeled

5 controls

1 labeled

2 placeholder only

2 unlabeled

Control	Type	Label	Method
list_name	text	Keep this field blank	aria-label
#et-e3bb2ec9-6479-471c-bdce-76bea62a4c6a	email	(Email address)	placeholder only
input	text	(Search)	placeholder only
input	submit	(none)	none
#footer-language-selector	select	(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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

F

Link & Button Quality

Action

21 issue(s) across 72 links and 13 buttons

FIX

21 issue(s) across 72 links and 13 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: http://www.atlassian.com/; http://www.atlassian.com/; https://www.atlassian.com

14 link(s) with generic text

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

Got: http://www.atlassian.com/software/bitbucket/features/ai ("Learn more"); https://bitbucket.org/blog/ai ("Learn more"); http://www.atlassian.com/migration/resources/bitbucket-migration-assistant ("Learn more"); http://www.atlassian.com/roadmap/cloud?selectedProduct=bitbucket ("Learn more"); http://www.atlassian.com/software/bitbucket/premium ("Learn more"); http://www.atlassian.com/webinars/software/closer-look-bitbucket-cloud-how-to… ("Learn more"); http://www.atlassian.com/software/jira/bitbucket-integration ("Learn more"); http://www.atlassian.com/software/bitbucket/features/code-review ("Learn more"); /product/features/pipelines ("Learn more"); https://bitbucket.org/blog/a-modern-approach-to-change-management-with-bitbuc… ("Learn more") (+4 more)

1 link(s) open in new tab without warning

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

Got: https://play.goconsensus.com/a677ed675

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.close-all (#94 on page); button.mobile-toggle (#101 on page); button.search-open (#173 on page); button.search-close (#188 on page)

54 link(s) with descriptive text

72 links

3 empty

14 generic text

1 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
http://www.atlassian.com/	(empty)	empty	Add link text or aria-label
http://www.atlassian.com/	(empty)	empty	Add link text or aria-label
https://play.goconsensus.com/a677ed675	Watch demo	new tab	Add '(opens in new tab)' to text
http://www.atlassian.com/software/bitbuc…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai
https://bitbucket.org/blog/ai	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Ai
http://www.atlassian.com/migration/resou…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Bitbucket Migration Assistant
http://www.atlassian.com/roadmap/cloud?s…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Cloud?Selectedproduct=Bitbucket
http://www.atlassian.com/software/bitbuc…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Premium
http://www.atlassian.com/webinars/softwa…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Closer Look Bitbucket Cloud How To Migrate
http://www.atlassian.com/software/jira/b…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Bitbucket Integration
http://www.atlassian.com/software/bitbuc…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Code Review
/product/features/pipelines	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Pipelines
https://bitbucket.org/blog/a-modern-appr…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: A Modern Approach To Change Management With Bitbucket And Jira Service Management
http://www.atlassian.com/software/bitbuc…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Cloud Security
http://www.atlassian.com/software/bitbuc…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Data Center
http://www.atlassian.com/migration/resou…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Bitbucket Migration Assistant
http://www.atlassian.com/roadmap/cloud?s…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Cloud?Selectedproduct=Bitbucket
https://www.atlassian.com	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

63 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

http://www.atlassian.com/; http://www.atlassian.com/; https://www.atlassian.com

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

http://www.atlassian.com/software/bitbucket/features/ai ("Learn more"); https://bitbucket.org/blog/ai ("Learn more"); http://www.atlassian.com/migration/resources/bitbucket-migration-assistant ("Learn more"); http://www.atlassian.com/roadmap/cloud?selectedProduct=bitbucket ("Learn more"); http://www.atlassian.com/software/bitbucket/premium ("Learn more"); http://www.atlassian.com/webinars/software/closer-look-bitbucket-cloud-how-to… ("Learn more"); http://www.atlassian.com/software/jira/bitbucket-integration ("Learn more"); http://www.atlassian.com/software/bitbucket/features/code-review ("Learn more"); /product/features/pipelines ("Learn more"); https://bitbucket.org/blog/a-modern-approach-to-change-management-with-bitbuc… ("Learn more") (+4 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.

https://play.goconsensus.com/a677ed675

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.close-all (#94 on page); button.mobile-toggle (#101 on page); button.search-open (#173 on page); button.search-close (#188 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

D

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #0052cc

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 ModePartial Dark Mode

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

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

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Search

Skip Link

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 — Bitbucket ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

B

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

A

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+

Alt Text Quality

1 of 74 images have issues

PASS

1 of 74 images have issues

1 image(s) with generic alt text

3 decorative image(s) correctly marked

70 image(s) with good alt text

74 images 70 good alt text 3 decorative 1 generic

Issue	Count
generic	1 image(s)

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 Code and CI/CD, powe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Code & CI/CD, built …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 AI that provides con…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Migrating to the clo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 15 million developer…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Platform-wide AI bey…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Security and complia…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Integrate Bitbucket …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Deliver high quality…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Learn more	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Take Bitbucket Cloud…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Power up with Bitbuc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Why choose Bitbucket…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 See how Bitbucket Cl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Collaborate with IT …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Secure & compliant	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Build a DevOps toolc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 15 million developer…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 “We’ve gone from…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 “The Jira/Bitbucke…	21.00:1	3.0:1	#000000	#FFFFFF	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 91/100 — 3 failing, 25 passed

PASS

91

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
Remote MCP Server (in beta) `div.component > div.component > p > a`

These are opportunities to improve the legibility of your content.

Navigation

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
AI throughout the SDLC `div.component > div.component__heading-textblock > div.color-head > h3.fnt-wt`
1/4 `div.intra-div > div.component > div.component > h6.fnt-wt`
NATE VAN DUSEN, ENGINEERING PROGRAM MANAGEMENT DIRECTOR `div.column > div.intra-div > div.component > h5.fnt-wt`
Introducing Rovo Dev `div.column > div.component > div.component > h4.fnt-wt`
Bitbucket `div.row > div.column > div.component > h4.fnt-wt`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.header > nav#adg4-global-nav > div.nav-space > a.atlassian-home-link `header.header > nav#adg4-global-nav > div.nav-space > a.atlassian-home-link`
div.row > div.column > div.component > a.component--image__link `div.row > div.column > div.component > a.component--image__link`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

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

●Select elements have associated label elements.

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

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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

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

○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

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

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

○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

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