Skip to content
https://qodeinteractive.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Heading Hierarchy
Action
80 headings, 4 skip(s)
FIX
80 headings, 4 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H6 Qode ThemeForest Themes
  • H6 Resources
  • H6 Querida
  • H6 Zermatt
  • H6 Querida
  • H6 Madelyn
  • H6 Shoshin
  • H6 Breton
  • H2 600+
  • H2 Premium themes
  • H2 Check out our versatile and ever-expanding premium WordPress theme catalogue and find the perfect theme for your website.
  • H2 600+
  • H2 Premium themes
  • H2 Check out our versatile and ever-expanding premium WordPress theme catalogue and find the perfect theme for your website.
  • H6 Zermatt skipped
  • H6 Zermatt
  • H6 Querida
  • H6 Madelyn
  • H6 Shoshin
  • H6 Breton
  • H2 Create better sites with Qi Addons
  • H2 Get the Qi Addons for Elementor plugin, the largest free library of fully flexible custom widgets for Elementor on the market.
  • H2 Create better sites with Qi Addons
  • H2 Get the Qi Addons for Elementor plugin, the largest free library of fully flexible custom widgets for Elementor on the market.
  • H2 FSE perfected. Meet Qi Blocks
  • H2 A powerful Gutenberg-based plugin which gives you an unprecedented number of block editing options.
  • H2 Visit the Qode Magazine , a modern WP publication
  • H2 Creative themes
  • H2 All our themes carry that authentic aesthetic touch we are renowned for.
  • H6 Munich skipped
  • H6 Ametrine
  • H6 Ginevra
  • H6 Grete
  • H6 Lorne
  • H6 Obsius
  • H6 Munich
  • H6 Ametrine
  • H6 Ginevra
  • H6 Grete
  • H2 Bridge Theme
  • H2 Creative Multi-Purpose WordPress Theme
  • H2 Bridge theme - a WP bestseller
  • H2 Bridge theme - a WP bestseller
  • H2 Bridge Theme
  • H2 Creative Multi-Purpose WordPress Theme
  • H2 We bring beauty to WordPress
  • H2 Qi Templates
  • H6 Creative Studio skipped
  • H6 Web Agency
  • H6 Digital Agency
  • H6 Wedding
  • H6 Agency Creative
  • H6 Creative Studio
  • H6 Web Agency
  • H6 Digital Agency
  • H6 Wedding
  • H2 Award-winning premium design
  • H2 The work of 100+ in-house designers & devs turning WP into pure art.
  • H2 750k
  • H2 Customers
  • H2 20+
  • H2 Design awards
  • H2 100+
  • H2 Dedicated pros
  • H2 Award-Winning Premium Design
  • H2 750k
  • H2 Customers
  • H2 20+
  • H2 Design awards
  • H2 100+
  • H2 Dedicated pros
  • H2 Help Center
  • H2 Visit the Qode Help Center where you can browse Knowledge Base articles & contact our support.
  • H6 Company skipped
  • H6 Products
  • H6 WordPress Themes
  • H6 Magazine
  • H6 Community
  • H5 Your Cart
  • H4 Privacy Overview

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

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

B
Form Accessibility
9 of 18 controls have issues
REVIEW
9 of 18 controls have issues
Warning::
9 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input>; <input>; <input type="text" name="user_name">; <input type="password" name="user_password">; <input type="text" name="user_name">; <input type="email" name="user_email">; <input type="password" name="user_password">; <input type="password" name="user_confirm_password">; <input type="text" name="user_login">
Info::
9 control(s) properly labeled
18 controls
9 labeled
9 placeholder only
0 unlabeled
ControlTypeLabelMethod
#wt-cli-checkbox-necessarycheckboxNecessaryaria-label
#wt-cli-checkbox-functionalcheckboxfunctionalaria-label
#wt-cli-checkbox-performancecheckboxperformancearia-label
#wt-cli-checkbox-analyticscheckboxanalyticsaria-label
#wt-cli-checkbox-advertisementcheckboxadvertisementaria-label
#wt-cli-checkbox-otherscheckboxothersaria-label
#user_login_remembermecheckboxRemember mefor/id
#user_register_rememebermecheckboxRemember mefor/id
#newslettercheckboxGet the latest updates, news and discountsfor/id
user_passwordpassword(Password)placeholder only
inputinput(Search...)placeholder only
user_nametext(Username)placeholder only
user_emailemail(Email)placeholder only
user_passwordpassword(Password)placeholder only
user_confirm_passwordpassword(Repeat Password)placeholder only
inputinput(Search...)placeholder only
user_nametext(Username)placeholder only
user_logintext(Enter username or email)placeholder only

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

<input>; <input>; <input type="text" name="user_name">; <input type="password" name="user_password">; <input type="text" name="user_name">; <input type="email" name="user_email">; <input type="password" name="user_password">; <input type="password" name="user_confirm_password">; <input type="text" name="user_login">

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

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 Page not found – Qode Interactive Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
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
PREMIUM THEMES rs-layer-wrap.rs-parallax-wrap > rs-layer#slider-1-slide-1-layer-3 > a.qodef-btn > span.qodef-btn-text
ACCEPT span#wt-cli-cookie-banner > div.cli-bar-container > div.cli-bar-btn_container > a#wt-cli-accept-btn

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
Zermatt div.qodef-device-frame-slider-inner > div.qodef-dfs-bottom-section > div.qodef-dfs-item-info > h6.qodef-dfs-item-title
Ametrine div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-content > h6.qodef-iwis-item-title
Web Agency div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-content > h6.qodef-iwis-item-title
Company div.qodef-column-content > div#nav_menu-2 > div.qodef-widget-title-holder > h6.qodef-widget-title

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
div.qodef-position-left > div.qodef-position-left-inner > div.qodef-mobile-menu-opener > a div.qodef-position-left > div.qodef-position-left-inner > div.qodef-mobile-menu-opener > a
div.widget > div.qodef-logged-out-user > div.qodef-logged-out-user-inner > a.qodef-login-opener div.widget > div.qodef-logged-out-user > div.qodef-logged-out-user-inner > a.qodef-login-opener
div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder
div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder
div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder
div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder
div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder div.qodef-mobile-nav-inner > div.qodef-mobile-navigation-bottom-widget-area > div.widget > a.qodef-social-icon-widget-holder
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a div.swiper-wrapper > div.qodef-iwis-item > div.qodef-iwis-item-image > a
div.qodef-edd-side-cart > div.qodef-edd-cart-holder > h5.qodef-edd-cart-title > a.qodef-cart-close div.qodef-edd-side-cart > div.qodef-edd-cart-holder > h5.qodef-edd-cart-title > a.qodef-cart-close

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

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
Artist Portfolio Theme div.qodef-iwis-item > div.qodef-iwis-item-content > p.qodef-iwis-item-subtitle > a
Business div.qodef-iwis-item > div.qodef-iwis-item-content > p.qodef-iwis-item-subtitle > a

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]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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.
`button`, `link`, and `menuitem` elements have accessible names
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 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
No element has a `[tabindex]` value greater than 0
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
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
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
Buttons have an accessible name
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.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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
Alt Text Quality
26 of 554 images have issues
PASS
26 of 554 images have issues
Warning::
26 image(s) with generic alt text
Info::
33 decorative image(s) correctly marked
Info::
495 image(s) with good alt text
554 images 495 good alt text 33 decorative 26 generic
IssueCount
generic26 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)
ElementRatioRequiredFGBGResult
h2 600+21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Premium themes21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Check out our versat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 600+21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Premium themes21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Check out our versat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Create better21.00:13.0:1
#000000
#FFFFFF
Pass
h2 sites with Qi21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Addons21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get the Qi Addons fo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Create better21.00:13.0:1
#000000
#FFFFFF
Pass
h2 sites with Qi21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Addons21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get the Qi Addons fo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 FSE perfected.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meet Qi Blocks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A powerful Gutenberg…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 unprecedented number…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Visit the21.00:13.0:1
#000000
#FFFFFF
Pass
h2 , a modern WP public…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