Skip to content
https://www.snowflake.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Heading Hierarchy
Action
37 headings, 6 skip(s)
FIX
37 headings, 6 skip(s)
Info::
Single H1 present
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::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
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: H2 → H4 (missing H3)
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.
  • H1 All Your Knowledge. One trusted enterprise agent.
  • H6 JUNE 1-4, 2026 skipped
  • H4 Experience the Future of Enterprise Data at Summit 26
  • H2 Simplify Enterprise Data and AI
  • H5 EASY skipped
  • H4 Bring your data and AI strategies to life
  • H5 CONNECTED
  • H4 Connect your business ecosystem
  • H5 TRUSTED
  • H4 Achieve universal business continuity
  • H6 SNOWFLAKE POSTGRES IS NOW GA skipped
  • H4 Run production-ready Postgres alongside your analytics
  • H2 Streamline your architecture. Smash data silos.
  • H4 Data Engineering skipped
  • H4 Analytics
  • H4 AI
  • H4 Applications & Collaboration
  • H3 The AI Data Cloud
  • H3 Snowflake Intelligence
  • H2 Leading companies lead with Snowflake
  • H2 The SnowflakeEcosystem
  • H4 Snowflake Partner Network skipped
  • H4 Developer Community
  • H2 The Latest from Snowflake
  • H4 The ROI of Gen AI and Agents 2026 skipped
  • H4 Startup 2026: AI Agents Mean Business
  • H4 The Future of AI + Interoperability in Healthcare
  • H4 Snowflake Appoints Jonathan Beaulier as Chief Revenue Officer
  • H4 Snowflake appoints Michel Nader to lead META region, advancing regional AI ambitions
  • H4 Snowflake Launches Project SnowWork, Bringing Outcome-Driven AI to Every Business User
  • H4 BUILD GLOBAL | The Dev Conference for AI & Apps
  • H4 Data for Breakfast
  • H4 Snowflake Summit 26
  • H4 Snowflake Connect: Analytics
  • H4 The Agentic Enterprise: From Strategy to ROI
  • H4 Snowflake Connect: AI Data Cloud
  • H2 Where Data Does More

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

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.
Got: #ffffff
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 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
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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

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 Page not found - Snowflake Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 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 Present
Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Snowflake
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Snowflake 192×192 icon 512×512 icon Start URL Display Mode standalone
Name Snowflake Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
title Snowflake AI Data Cloud
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
p BUILD: The Dev Conference for AI & Apps …
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title Snowflake AI Data Cl…1.00:14.5:1
#000000
#000000
Fail
a Skip to content1.00:14.5:1
#000000
#000000
Fail
p BUILD: The Dev Confe…1.00:14.5:1
#000000
#000000
Fail
p Hear the latest prod…21.00:14.5:1
#000000
#FFFFFF
Pass
a watch now16.25:14.5:1
#000000
#D9E4EB
Pass
a start for free19.37:14.5:1
#000000
#EBF8FC
Pass
span Product19.37:14.5:1
#000000
#EBF8FC
Pass
span Solutions19.37:14.5:1
#000000
#EBF8FC
Pass
span Why Snowflake19.37:14.5:1
#000000
#EBF8FC
Pass
span Resources19.37:14.5:1
#000000
#EBF8FC
Pass
span Developers19.38:14.5:1
#000000
#EBF8FD
Pass
span Pricing19.38:14.5:1
#000000
#EBF8FD
Pass
span The Snowflake Platfo…19.21:14.5:1
#000000
#EAF7FC
Pass
span Develop AI products,…19.14:14.5:1
#000000
#E8F7FC
Pass
span Snowflake Intelligen…18.99:14.5:1
#000000
#E7F6FC
Pass
span NOW GA18.92:14.5:1
#000000
#E5F6FC
Pass
span All your knowledge. …18.77:14.5:1
#000000
#E4F5FC
Pass
span Analytics18.69:14.5:1
#000000
#E2F5FB
Pass
span Data Engineering18.50:14.5:1
#000000
#E0F4FB
Pass
span Applications & Colla…18.36:14.5:1
#000000
#DFF3FC
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 8 failing, 28 passed
REVIEW
78

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
Fanatics Toyota Indeed BlackRock VodafoneZiggo div > div.aem-container > div.snowflake-navigation-container > div.swiper-container
FEATURED NEWS EVENTS WEBINARS div.snowflake-tabs-effect-fade > div.aem-container > div.snowflake-navigation-container > div.swiper-container

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Fanatics div.swiper-container > div#swiper-wrapper-000da879c7c5af98 > span.swiper-slide > span.snowflake-tabs-navigation-item
Toyota div.swiper-container > div#swiper-wrapper-000da879c7c5af98 > span.swiper-slide > span.snowflake-tabs-navigation-item
Indeed div.swiper-container > div#swiper-wrapper-000da879c7c5af98 > span.swiper-slide > span.snowflake-tabs-navigation-item
BlackRock div.swiper-container > div#swiper-wrapper-000da879c7c5af98 > span.swiper-slide > span.snowflake-tabs-navigation-item
VodafoneZiggo div.swiper-container > div#swiper-wrapper-000da879c7c5af98 > span.swiper-slide > span.snowflake-tabs-navigation-item
FEATURED div.swiper-container > div#swiper-wrapper-42dc5856fa410b598 > span.swiper-slide > span.snowflake-tabs-navigation-item
NEWS div.swiper-container > div#swiper-wrapper-42dc5856fa410b598 > span.swiper-slide > span.snowflake-tabs-navigation-item
EVENTS div.swiper-container > div#swiper-wrapper-42dc5856fa410b598 > span.swiper-slide > span.snowflake-tabs-navigation-item
WEBINARS div.swiper-container > div#swiper-wrapper-42dc5856fa410b598 > span.swiper-slide > span.snowflake-tabs-navigation-item

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.snowflake-pushdown-banner-text-white > div.snowflake-pushdown-banner > div.snowflake-pushdown-banner-close > div.snowflake-button-container div.snowflake-pushdown-banner-text-white > div.snowflake-pushdown-banner > div.snowflake-pushdown-banner-close > div.snowflake-button-container
div#container-e412d4c4ca > nav.snowflake-mega-nav-header-inner > div.snowflake-mega-nav-header-buttons-container > div.snowflake-mega-nav-header-mobile-icon div#container-e412d4c4ca > nav.snowflake-mega-nav-header-inner > div.snowflake-mega-nav-header-buttons-container > div.snowflake-mega-nav-header-mobile-icon
div.aem-GridColumn > div#container-747cc5cedd > div.snowflake-button-icon > div.snowflake-button-container div.aem-GridColumn > div#container-747cc5cedd > div.snowflake-button-icon > div.snowflake-button-container

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.

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
START FOR FREE nav.snowflake-mega-nav-header-inner > div.snowflake-mega-nav-header-buttons-container > div.snowflake-button-primary > a.start_for_free_nav
LEARN MORE ABOUT SNOWFLAKE INTELLIGENCE div.cmp-container > div.aem-container > div.snowflake-button-primary > a.snowflake-button-container
DATA AND AI div.left-alignment > div#title-component > h2.snowflake-typographyv2 > span.snowflake-typographyv2
WHY SNOWFLAKE div.cmp-container > div.aem-container > div.snowflake-button-primary > a.snowflake-button-container
VIEW PRICING div.cmp-container > div.aem-container > div.snowflake-button-link > a.style-25
EASY div.left-alignment > div#title-component > h5.snowflake-typographyv2 > span.snowflake-typographyv2
CONNECTED div.left-alignment > div#title-component > h5.snowflake-typographyv2 > span.snowflake-typographyv2
TRUSTED div.left-alignment > div#title-component > h5.snowflake-typographyv2 > span.snowflake-typographyv2
The Snowflake platform is a fully managed service that’s truly easy to use, con… div.text-color-text-04 > div.snowflake-text > span > p
EXPLORE THE SOLUTION div.cmp-container > div.aem-container > div.snowflake-button-primary > a.snowflake-button-container
LEAD WITH SNOWFLAKE div.left-alignment > div#title-component > h2.snowflake-typographyv2 > span.snowflake-typographyv2
VIEW CUSTOMERS div.cmp-container > div.aem-container > div.snowflake-button-secondary > a.snowflake-button-container
Retail & Consumer Goods div.snowflake-text > span > p > a
Watch the video div.snowflake-text > span > p > a
Learn about partners div.cmp-container > div.aem-container > div.snowflake-button-link > a.button_2
Visit the developers center div.cmp-container > div.aem-container > div.snowflake-button-link > a.button_3
Read now article.snowflake-card-v2-advanced-inner > div.snowflake-card-v2-advanced-content > div.snowflake-card-v2-advanced-button > div.snowflake-button-container
Read now article.snowflake-card-v2-advanced-inner > div.snowflake-card-v2-advanced-content > div.snowflake-card-v2-advanced-button > div.snowflake-button-container
Read now article.snowflake-card-v2-advanced-inner > div.snowflake-card-v2-advanced-content > div.snowflake-card-v2-advanced-button > div.snowflake-button-container
SUBSCRIBE NOW form#mktoForm_45871 > div.mktoButtonRow > span.mktoButtonWrap > button.mktoButton
REJECT ALL div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-reject-all-handler
ACCEPT ALL COOKIES div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler

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
JUNE 1-4, 2026 div.snowflake-premium-content-banner-content > div.snowflake-premium-content-banner-eyebrow > div#title-component > h6.snowflake-typographyv2
EASY div.aem-container > div.left-alignment > div#title-component > h5.snowflake-typographyv2
SNOWFLAKE POSTGRES IS NOW GA div.snowflake-premium-content-banner-content > div.snowflake-premium-content-banner-eyebrow > div#title-component > h6.snowflake-typographyv2
Data Engineering div.snowflake-card-v2-advanced-content > div.snowflake-card-v2-advanced-title > div#title-component > h4.snowflake-typographyv2
Snowflake Partner Network div.aem-container > div > div#title-component > h4.snowflake-typographyv2
The ROI of Gen AI and Agents 2026 div.snowflake-card-v2-advanced-content > div.snowflake-card-v2-advanced-title > div#title-component > h4.snowflake-typographyv2

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Country United States Canada United Kingdom Germany France Australia Japan Alan… div.mktoFormRow > div.mktoFieldDescriptor > div.mktoFieldWrap > select#Country

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
Privacy Policy span > ul > li > a
Communication Preferences span > ul > li > a
Cookies Settings span > ul > li > button#ot-sdk-btn
Do Not Share My Personal Information span > ul > li > a
Legal span > ul > li > a

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Statement. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
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.
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.
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
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
No form fields have multiple labels
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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 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
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>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
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
All 83 images OK
PASS
All 83 images OK
Info::
4 decorative image(s) correctly marked
Info::
79 image(s) with good alt text
83 images 79 good alt text 4 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 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="adhoc1" id="adhoc1">
Info::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#Emailemail*for/id
#Companytext*for/id
#Countryselect*for/id
#adhoc1checkbox(none)none

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

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

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