Skip to content
https://www.sonarqube.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
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.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 PAGE NOT FOUND ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 27 passed
REVIEW
82

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Products SonarQube products SonarQube Cloud Cloud-based static analysis tool fo… nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck
Why Sonar Use cases AI code quality Validate AI code for security and quality D… nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck
Developers For developers Developer hub Learning center Commitment to open sour… nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck
Resources Get started Onboarding hub Learning center Interactive demos Communit… nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1j936iw > div.css-1r874ck
Company Learn about Sonar About Us Our customers Partners Events hub Newsroom C… nav.css-1fp82pj > ul.css-b5wfk1 > li.css-1y53taa > div.css-1r874ck
SonarQube SonarQube Industry leading products SonarQube Server SonarQube Cloud … section.css-mf87fb > div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.css-1nbar7y > section.css-1bavp3g > div.css-psrmlu > div div.css-1nbar7y > section.css-1bavp3g > div.css-psrmlu > div
div.css-1nbar7y > section.css-1d19qss > div.css-p8qmoh > div div.css-1nbar7y > section.css-1d19qss > div.css-p8qmoh > div

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SonarQube SonarQube Industry leading products SonarQube Server SonarQube Cloud … div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw
Download div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw
Docs div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw
Pricing div.css-jlorxn > div.css-17nla5q > ul.css-y25j1f > li.css-10mbhcw

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
SAST div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:0
Taint analysis div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:1
Secrets detection div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:2
IaC scanning div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:3
Advanced SAST div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:4
SCA div.swiper > div.swiper-wrapper > div.swiper-slide > li#tab:R1ak3ah:5

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Control item 0 section.css-1lxt3h6 > div.css-167fs54 > div.css-13n7hpy > button.css-1b2yhzm
Control item 1 section.css-1lxt3h6 > div.css-167fs54 > div.css-13n7hpy > button.css-17t6fdk
Control item 2 section.css-1lxt3h6 > div.css-167fs54 > div.css-13n7hpy > button.css-17t6fdk
Control item 3 section.css-1lxt3h6 > div.css-167fs54 > div.css-13n7hpy > button.css-17t6fdk
Website Terms of Use div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0
Privacy Notice div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0
Cookie Policy div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0
Trust center div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0
Your Privacy Choices div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > button.e1u9akvp0
UK Modern Slavery Act Statement div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > a.e1u9akvp0
Unsubscribe div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > button.e1u9akvp0
Accessibility div.css-1go16d5 > ul.css-6w0507 > li.css-1dsq0w7 > button.e1u9akvp0

These items highlight common accessibility best practices.

○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
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[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.
●`[accesskey]` values are unique
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<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>`).
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`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
○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
○`<frame>` or `<iframe>` elements have a title
○`<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.
○`<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
○Elements with visible text labels have matching accessible names.
○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.
A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

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
Heading Hierarchy
49 headings
PASS
49 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Code verification for the AI era
  • H2 The trust and verification layer for your AI code
  • H3 Quality metrics
  • H3 Security analysis
  • H3 Remediation
  • H3 CI/CD integration
  • H2 Select the perfect SonarQube deployment for you
  • H1 SonarQube Cloud duplicate H1
  • H1 SonarQube Server duplicate H1
  • H2 SonarQube core capabilities
  • H3 Automated code review
  • H3 Static code analysis
  • H3 Developer experience
  • H3 AI Code Assurance
  • H2 Automated code review
  • H2 AI-powered remediation
  • H2 Instant code fixes at your fingertips
  • H2 Developer-led code security
  • H2 Static Application Security Testing (SAST)
  • H2 Taint analysis
  • H2 Secrets Detection
  • H2 Infrastructure as Code (IaC) scanning
  • H2 Advanced SAST
  • H2 Software Composition Analysis (SCA)
  • H2 Trusted by development teams worldwide
  • H2 Code quality and security in your CI/CD workflow
  • H2 Advanced features for the enterprise
  • H3 Compliance & reporting
  • H3 Quality gates & profiles
  • H3 Portfolio & enterprise reporting
  • H2 Build trust into every line of code
  • H2 Frequently asked questions
  • H3 What is SonarQube?
  • H3 How does SonarQube work?
  • H3 What are the key benefits of SonarQube?
  • H3 Is SonarQube a SAST tool?
  • H3 Is SonarQube Open Source?
  • H3 How many programming languages does Sonar support?
  • H3 Can Sonar products analyze AI-generated code?
  • H3 How does SonarQube ensure consistency across teams?
  • H3 Are Sonar products suitable for individuals and enterprises?
  • H3 How does SonarQube detect code quality issues, bugs, and vulnerabilities?
  • H3 How is SonarQube integrated into CI/CD pipelines?
  • H3 What is SonarQube AI CodeFix?
  • H3 How do I enable AI CodeFix in SonarQube?
  • H3 What is vibe coding and how does it differ from traditional coding?
  • H3 How does SonarQube help support vibe coding?
  • H3 Is SonarQube Free?
  • H3 How much does SonarQube cost?

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

A
Alt Text Quality
1 of 93 images have issues
PASS
1 of 93 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
23 decorative image(s) correctly marked
Info::
69 image(s) with good alt text
93 images 69 good alt text 23 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#react-select-54-inputinputSelect your Languagearia-label
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 Code verification fo…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 SonarQube Cloud21.00:13.0:1
#000000
#FFFFFF
Pass
h1 SonarQube Server21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The trust and verifi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Select the perfect S…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SonarQube core capab…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Automated code revie…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI-powered remediati…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Instant code fixes a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Developer-led code s…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Static Application S…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Taint analysis21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Secrets Detection21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Infrastructure as Co…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Advanced SAST21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Software Composition…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted by developme…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Code quality and sec…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Advanced features fo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Build trust into eve…21.00:13.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback