Skip to content
https://quantcast.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

D
Heading Hierarchy
Action
32 headings, 3 skip(s)
FIX
32 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
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.
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 The Ad Platform Built for Performance Marketers
  • H4 Trusted By skipped
  • H2 Why do you need Quantcast DSP?
  • H3 Meet Your Next Customer with Autonomous Advertising
  • H2 (empty)
  • H2 Leader in G2’s Demand-Side Platform Category
  • H4 Our customers consistently highlight how Quantcast helps them: skipped
  • H4 Funcom Levels Up with 57% More Video Views, 10% Lower CPV
  • H4 SodaStream Bubbles Up 107% Conversion Lift with 19% Lower CPA
  • H4 Travel Texas Gains an Edge with 84% Lift Among High-Awareness Audiences
  • H4 17% Higher Ad Recall for Starbucks with Focused Creative Messaging
  • H4 Yokohama Achieves 61% Lower CPA and 356% More Store Visits
  • H4 United Airlines Campaign Soars to 77% More Efficient CPA and 27% Higher Awareness
  • H4 88% Above Goal: MBNA Delivers More Approvals at Lower CPA
  • H4 Real-Time Insights Drive 23% Awareness Lift for Copalli Rum
  • H4 Funcom Levels Up with 57% More Video Views, 10% Lower CPV
  • H4 SodaStream Bubbles Up 107% Conversion Lift with 19% Lower CPA
  • H4 Travel Texas Gains an Edge with 84% Lift Among High-Awareness Audiences
  • H4 17% Higher Ad Recall for Starbucks with Focused Creative Messaging
  • H4 Yokohama Achieves 61% Lower CPA and 356% More Store Visits
  • H4 United Airlines Campaign Soars to 77% More Efficient CPA and 27% Higher Awareness
  • H4 88% Above Goal: MBNA Delivers More Approvals at Lower CPA
  • H4 Real-Time Insights Drive 23% Awareness Lift for Copalli Rum
  • H4 Funcom Levels Up with 57% More Video Views, 10% Lower CPV
  • H4 SodaStream Bubbles Up 107% Conversion Lift with 19% Lower CPA
  • H4 Travel Texas Gains an Edge with 84% Lift Among High-Awareness Audiences
  • H4 17% Higher Ad Recall for Starbucks with Focused Creative Messaging
  • H4 Yokohama Achieves 61% Lower CPA and 356% More Store Visits
  • H1 Maximize ROI Across Every Channel duplicate H1
  • H6 Company skipped
  • H6 Resources
  • H6 Subscribe to our newsletter for the latest news & information

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Alt Text Quality
Action
6 of 259 images have issues
REVIEW
6 of 259 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
6 decorative image(s) correctly marked
Info::
247 image(s) with good alt text
259 images 247 good alt text 6 decorative 6 missing
IssueCount
missing6 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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Quantcast ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 The Ad Platform Built for Performance Ma…
1.10:1
#000000
on
#001216
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Maximize ROI Across Every Channel
1.10:1
#000000
on
#001216
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Why do you need Quantcast DSP?
1.10:1
#000000
on
#001216
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Leader in G2’s Demand-Side Platform Ca…
1.10:1
#000000
on
#001216
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Meet Your Next Customer with Autonomous …
1.10:1
#000000
on
#001216
needs 3.0:1 (large text)
19px · bottom of viewport
title Quantcast | DSP Platform | DSP Programma…
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · top of page (header area)
span Book a Demo
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · top of page (header area)
span Platform
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · top of page (header area)
span How it Works
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · top of page (header area)
span Overview
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · above the fold
span AI Suite
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · above the fold
span Audience Graph
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · above the fold
span Channels
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · above the fold
span CTV
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · above the fold
span Audio
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · above the fold
span Video
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · above the fold
span Display
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · above the fold
span Mobile
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · above the fold
span Native
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · mid-page
span Capabilities
1.10:1
#000000
on
#001216
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The Ad Platform Buil…1.10:13.0:1
#000000
#001216
Fail
h1 Maximize ROI Across …1.10:13.0:1
#000000
#001216
Fail
h2 Why do you need Quan…1.10:13.0:1
#000000
#001216
Fail
h2 Leader in G2’s Dem…1.10:13.0:1
#000000
#001216
Fail
h3 Meet Your Next Custo…1.10:13.0:1
#000000
#001216
Fail
title Quantcast | DSP Plat…1.10:14.5:1
#000000
#001216
Fail
span Book a Demo1.10:14.5:1
#000000
#001216
Fail
span Platform1.10:14.5:1
#000000
#001216
Fail
span How it Works1.10:14.5:1
#000000
#001216
Fail
span Overview1.10:14.5:1
#000000
#001216
Fail
span AI Suite1.10:14.5:1
#000000
#001216
Fail
span Audience Graph1.10:14.5:1
#000000
#001216
Fail
span Channels1.10:14.5:1
#000000
#001216
Fail
span CTV1.10:14.5:1
#000000
#001216
Fail
span Audio1.10:14.5:1
#000000
#001216
Fail
span Video1.10:14.5:1
#000000
#001216
Fail
span Display1.10:14.5:1
#000000
#001216
Fail
span Mobile1.10:14.5:1
#000000
#001216
Fail
span Native1.10:14.5:1
#000000
#001216
Fail
span Capabilities1.10:14.5:1
#000000
#001216
Fail

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 86/100 — 4 failing, 20 passed
REVIEW
86

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Funcom Levels Up with 57% More Video Views, 10% Lower CPV Technology div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
SodaStream Bubbles Up 107% Conversion Lift with 19% Lower CPA Food & Beverage div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Travel Texas Gains an Edge with 84% Lift Among High-Awareness Audiences Travel … div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
17% Higher Ad Recall for Starbucks with Focused Creative Messaging Food & Bever… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Yokohama Achieves 61% Lower CPA and 356% More Store Visits Automotive div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Travel Texas Gains an Edge with 84% Lift Among High-Awareness Audiences Travel … div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
17% Higher Ad Recall for Starbucks with Focused Creative Messaging Food & Bever… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Yokohama Achieves 61% Lower CPA and 356% More Store Visits Automotive div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
United Airlines Campaign Soars to 77% More Efficient CPA and 27% Higher Awarene… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
88% Above Goal: MBNA Delivers More Approvals at Lower CPA Finance div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Real-Time Insights Drive 23% Awareness Lift for Copalli Rum Food & Beverage div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Funcom Levels Up with 57% More Video Views, 10% Lower CPV Technology div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
SodaStream Bubbles Up 107% Conversion Lift with 19% Lower CPA Food & Beverage div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Travel Texas Gains an Edge with 84% Lift Among High-Awareness Audiences Travel … div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
17% Higher Ad Recall for Starbucks with Focused Creative Messaging Food & Bever… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Yokohama Achieves 61% Lower CPA and 356% More Store Visits Automotive div.slick-slider > div.slick-list > div.slick-track > div.slick-slide

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.

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
Trusted By div.builder-block > div._container_4qrmh_12 > div._textContainer_4qrmh_23 > h4._text_4qrmh_23
Our customers consistently highlight how Quantcast helps them: div._container_wtcj5_12 > div._panelContainer_wtcj5_29 > div._container_1c0u0_12 > h4._schemeDarkBlueText_fwe0h_222
Company div._container_b5xxs_12 > div._panelContainer_fwe0h_181 > div > h6._linksHeader_3taj9_20

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.builder-blocks > div.builder-block > div._panelContainer_fwe0h_181 > img._bgImage_1dm9h_39 div.builder-blocks > div.builder-block > div._panelContainer_fwe0h_181 > img._bgImage_1dm9h_39
div.builder-blocks > div.builder-block > div._panelContainer_fwe0h_181 > img._bgImage_1dm9h_39 div.builder-blocks > div.builder-block > div._panelContainer_fwe0h_181 > img._bgImage_1dm9h_39
div._container_1c0u0_12 > div._schemeDarkestBlueText_fwe0h_288 > p > img div._container_1c0u0_12 > div._schemeDarkestBlueText_fwe0h_288 > p > img
div._container_1c0u0_12 > div._schemeDarkestBlueText_fwe0h_288 > p > img div._container_1c0u0_12 > div._schemeDarkestBlueText_fwe0h_288 > p > img
div._container_1c0u0_12 > div._schemeDarkestBlueText_fwe0h_288 > p > img div._container_1c0u0_12 > div._schemeDarkestBlueText_fwe0h_288 > p > img
div._container_1c0u0_12 > div._schemeDarkestBlueText_fwe0h_288 > p > img div._container_1c0u0_12 > div._schemeDarkestBlueText_fwe0h_288 > p > img

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●ARIA IDs are unique
●No form fields have multiple labels
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
○`[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
○`<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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○Tables have different content in the summary attribute and `<caption>`.
○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
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" name="expressConsent" id="expressConsent">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#Emailemail*for/id
#Countryselect*for/id
#expressConsentcheckbox(none)none

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

<input type="checkbox" name="expressConsent" id="expressConsent">

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

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

Send Feedback