Skip to content
https://ibkul.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
7
REVIEW
3
PASS
14
INFO
0
Checks
24
14 PASS 3 REVIEW 7 FIX
F
Heading Hierarchy
Action
88 headings, 6 skip(s)
FIX
88 headings, 6 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: 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 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (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 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 A new name. Same brand. Learn more.
  • H2 Complimentary Shipping on U.S. Orders Over $100
  • H2 New Prints Are In! Shop New Arrivals.
  • H2 A new name. Same brand. Learn more.
  • H2 Complimentary Shipping on U.S. Orders Over $100
  • H4 Women's New Arrivals skipped
  • H4 Men's New Arrivals
  • H4 Kids' Collection
  • H4 IBTravel™ Reversible Travelwear
  • H4 Sale
  • H1 IBKÜL
  • H4 Women's New Arrivals skipped
  • H4 Men's New Arrivals
  • H4 Kids' Collection
  • H2 Made to move.
  • H3 Golf
  • H3 Tennis + Pickleball
  • H3 Fitness + Yoga
  • H3 Equestrian
  • H4 IBTravel™ Reversible Travelwear
  • H2 Playful Prints
  • H3 SHOP THE LATEST PRINTS
  • H4 Courtney
  • H4 Eleanor
  • H4 Robin
  • H4 Yesenia
  • H4 Sale
  • H2 Cool is at our core.
  • H3 Premium lifestyle apparel for sport, resort, travel, and everyday life. Led by patented Icefil® cooling technology and UPF 50+ sun protection.
  • H5 UPF 50+ skipped
  • H5 Iceƒil Cooling
  • H5 Lightweight + Breathable
  • H5 Moisture-Wicking + Quick-Dry
  • H5 4-Way Stretch
  • H5 THE ICEFIL® DIFFERENCE
  • H3 UPF 50+ protectionthat helps cool your skin, too.
  • H2 Find your IBCOOL.
  • H3 Shop new arrivals and customer favorites.
  • H2 Playful Prints
  • H3 Explore the latest in UPF 50+ sun protection with cooling and moisture-wicking tech.
  • H6 NEW ARRIVALS ✨ skipped
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 NEW ARRIVALS ✨
  • H6 Best Seller
  • H6 Best Seller
  • H6 Best Seller
  • H6 Best Seller
  • H6 Best Seller
  • H6 Best Seller
  • H6 Best Seller
  • H6 Best Seller
  • H6 Best Seller
  • H2 Shop By Sport
  • H3 Sun-safe, game-ready activewear for golf, tennis, yoga & more.
  • H5 Golf skipped
  • H5 Tennis + Pickleball
  • H5 Yoga
  • H5 Equestrian
  • H5 Golf
  • H5 Equestrian
  • H5 Yoga
  • H5 Tennis + Pickleball
  • H3 Trusted by Champions. Loved by Legends.
  • H3 Nancy Lopez
  • H3 Madelene Sagström
  • H3 Ann Liguori
  • H3 Hear from Madelene →
  • H2 Customer Love
  • H2 Let customers speak for us
  • H2 Shop the Look
  • H1 About IBCOOL duplicate H1
  • H3 CONTACT US skipped
  • H3 ABOUT IBCOOL
  • H3 CUSTOMER CARE
  • H3 SIGN UP AND SAVE $20
  • H3 Shopping Cart
  • H3 Search our store

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

F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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::
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 Missing
✓ 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
Theme color only
FIX
Theme color only
Info::
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.
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 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
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.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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.
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO (missing!)

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
2 of 4 controls have issues
REVIEW
2 of 4 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="contact[email]" id="ContactSubscribe-7b0bf4c6-3873-4222-b8d6-ce009e710078-email">; <textarea name="note">
Info::
2 control(s) properly labeled
4 controls
2 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#boost-sd__search-widget-init-input-0searchSearch productsaria-label
#boost-sd__search-widget-init-input-1inputWhen autocomplete results are available use up and down arrows to review and enter to selectaria-label
#ContactSubscribe-7b0bf4c6-3873-4222-b8d6-ce009e710078-emailemail(Enter your email)placeholder only
notetextarea(Special instructions for seller)placeholder only

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

<input type="email" name="contact[email]" id="ContactSubscribe-7b0bf4c6-3873-4222-b8d6-ce009e710078-email">; <textarea name="note">

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

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 142 chars
Got: 1 >120-char heading(s)
Info::
22 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 22 all-caps heading(s)
A+
Alt Text Quality
All 169 images OK
PASS
All 169 images OK
Info::
10 decorative image(s) correctly marked
Info::
159 image(s) with good alt text
169 images 159 good alt text 10 decorative
All images have appropriate alt text.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 10 visible text node(s) render at >= 12 CSS pixels
PASS
All 10 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
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 About IBCOOL21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A new name. Same bra…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Complimentary Shippi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 New Prints Are In!21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A new name. Same bra…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Complimentary Shippi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Made to move.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Playful Prints21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Cool is at our core.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Find your IBCOOL.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Playful Prints21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shop By Sport21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Customer Love21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Let customers speak …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shop the Look21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Golf21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Tennis + Pickleball21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Fitness + Yoga21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Equestrian21.00:13.0:1
#000000
#FFFFFF
Pass
h3 SHOP THE LATEST PRIN…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.

A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 27 passed
PASS
95

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
THE ICEFIL® DIFFERENCE div.beae-by34w9xh > div.beae-wbe1gi08 > div.beae-pios1uo1 > h5.beae-block

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
UPF 50+ div.beae-slider-content > div.beae-list-item > div.beae-vcdt94ya > h5.beae-block
NEW ARRIVALS ✨ div.beae-list-item > div.beae-6okawe77 > div.beae-g1o89vfn > h6.beae-block
Golf div.beae-e8u5xbda > div.beae-6y13vrt6 > div.beae-5v9gkeum > h5.beae-block
div.m-footer--accordion > div.m-footer--block > div.m-footer--block-inner > h3.m-accordion--item-button div.m-footer--accordion > div.m-footer--block > div.m-footer--block-inner > h3.m-accordion--item-button

These are opportunities to improve keyboard navigation in your application.

○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○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
○Links are distinguishable without relying on color.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback