Skip to content
https://qt.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Heading Hierarchy
Action
91 headings, 5 skip(s)
FIX
91 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Development Framework & Tools
  • H6 Products skipped
  • H6 Qt Framework
  • H6 Qt for MCUs
  • H6 Development Tools
  • H6 Qt Creator IDE
  • H6 Qt Design Studio
  • H6 Figma to Qt
  • H6 More
  • H6 Desktop, Mobile & Web
  • H6 Embedded Devices
  • H6 IAR Platform
  • H3 Software Quality Tools
  • H6 Products skipped
  • H6 Squish
  • H6 Coco
  • H6 Test Center
  • H6 Axivion Static Code Analysis
  • H6 Axivion Architecture Verification
  • H6 More
  • H6 Licensing
  • H6 Axivion for CUDA
  • H3 Industry & Compliance Solutions
  • H6 Industry skipped
  • H6 Automotive
  • H6 Aerospace & Defense
  • H6 Industrial Vehicles
  • H6 Micro-Mobility
  • H6 Consumer Electronics
  • H6 Industrial Automation
  • H6 MedTech
  • H6 Regulations & Standards
  • H6 The EU Cyber Resilience Act (CRA)
  • H6 Quality Standards
  • H6 Accessibility
  • H6 More
  • H6 Cyber Resilience Act (CRA)
  • H6 Software Insights
  • H3 Resources, Support & Services
  • H6 Get Help skipped
  • H6 Contact Us
  • H6 User Portal
  • H6 Support
  • H6 Customer Success
  • H6 Professional Services
  • H6 Partners
  • H6 User Research
  • H6 Resources
  • H6 Software Insights
  • H6 Blog
  • H6 Resource Center
  • H6 Success Stories
  • H6 Documentation
  • H6 Forum
  • H6 Live Events & Webinars
  • H1 Your Software Excellence Begins Here
  • H2 From Design to Deployment—and Back Again
  • H2 Design Shouldn’t Be Lost in Translation
  • H2 Quality Isn’t Optional
  • H2 Built for Speed, Trusted for Scale
  • H2 Compliance Without Compromise
  • H2 Excellence You ExperienceEvery Day, Everywhere
  • H2 You Build the Future.We Build the Tools.
  • H4 Qt Framework skipped
  • H4 Qt for MCUs
  • H4 Qt Development Tools
  • H4 Qt Creator IDE
  • H4 IAR Platform
  • H4 Qt Design Studio
  • H4 Figma to Qt
  • H4 Squish
  • H4 Coco
  • H4 Test Center
  • H4 Axivion Static Code Analysis
  • H4 Axivion Architecture Verification
  • H2 Impact That Speaks for Itself
  • H2 Engineered for Your Industry's Edge
  • H2 From Curiosity to Capability
  • H2 Technology Doesn’t Shape the World.People Like You Do.
  • H2 Privacy Preference Center
  • H3 Your Privacy
  • H3 Performance Cookies
  • H3 Strictly Necessary Cookies
  • H3 Functional Cookies
  • H3 Targeting Cookies
  • H4 Your Privacy
  • H4 Performance Cookies
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✗ Apple Touch Missing
✗ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Qt Group Logo, Link to home page. ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass 2 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Your Software Excell…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Begins Here21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Design Shouldn’t B…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Quality Isn’t Opti…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built for Speed, Tru…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Compliance Without C…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Development Framewor…4.89:13.0:1
#000000
#7A7A7A
Pass
h3 Software Quality Too…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Industry & Complianc…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Resources, Support &21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Services21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Your Privacy21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Performance Cookies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Strictly Necessary C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Functional Cookies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Targeting Cookies21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie List21.00:13.0:1
#000000
#FFFFFF
Pass
title Qt | Tools for Each …5.24:14.5:1
#000000
#7F7F7F
Pass
a Skip to main content5.24:14.5:1
#000000
#7F7F7F
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 24 passed
REVIEW
88

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
From Design to Deployment div.b-columns__column > div.h-wysiwyg-html > h2 > span

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
Qt Framework div.l-item-filtering__items > div.l-item-filtering__item > div.c-item > h4

These are opportunities to improve keyboard navigation in your application.

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
the development and improvement of new services div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > li
delivering advertisements and measuring their effectiveness div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > li
to display personalized content depending on your settings div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > li
to display personalized ads depending on your settings div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > li

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

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
Legal Notice div#hs_menu_wrapper_module_footer_footer_secondary_menu > ul > li.hs-menu-item > a
Cookie Settings div#hs_menu_wrapper_module_footer_footer_secondary_menu > ul > li.hs-menu-item > a
Cookie Settings ul > li.hs-menu-item > a > button#ot-sdk-btn

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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○Identical links have the same purpose.
○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
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Main Navigation" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 49 images OK
PASS
All 49 images OK
Info::
13 decorative image(s) correctly marked
Info::
36 image(s) with good alt text
49 images 36 good alt text 13 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback