Skip to content
https://anaconda.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
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.
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::
40 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 40 <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
Heading Hierarchy
Action
47 headings, 3 skip(s)
REVIEW
47 headings, 3 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 → 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.
  • H4 ANACONDA PLATFORM
  • H4 FOR DEVELOPERS
  • H4 PLATFORM BENEFITS
  • H4 PLATFORM & LICENSING
  • H4 CAPABILITIES
  • H4 INDUSTRIES
  • H4 SERVICES & SUPPORT
  • H4 FOR USERS
  • H4 MEET US
  • H4 ARTICLES
  • H4 SUPPORT
  • H4 ABOUT US
  • H4 PRESS
  • H4 CONTACT
  • H4 CAREERS
  • H4 ANACONDA PLATFORM
  • H4 FOR DEVELOPERS
  • H4 PLATFORM BENEFITS
  • H4 PLATFORM & LICENSING
  • H4 CAPABILITIES
  • H4 INDUSTRIES
  • H4 SERVICES & SUPPORT
  • H4 FOR USERS
  • H4 MEET US
  • H4 ARTICLES
  • H4 SUPPORT
  • H4 ABOUT US
  • H4 PRESS
  • H4 CONTACT
  • H4 CAREERS
  • H1 Trusted Foundationfor Enterprise AI
  • H6 ANACONDA PLATFORM skipped
  • H2 Accelerate Intelligence at Enterprise Scale
  • H3 Anaconda Core
  • H3 AI Catalyst
  • H2 Millions Rely on Anaconda to Advance Their AI Initiatives
  • H2 The State of Data Science & AI Report
  • H2 Struggling to move AI from pilot to production? You're not alone.
  • H2 Additional Resources for Your AI Journey
  • H6 News & Insights skipped
  • H6 Learning Courses
  • H6 Reports & Guides
  • H2 Accelerate AI with Open Source Today
  • H6 Company skipped
  • H6 Products
  • H6 Customers
  • H6 Popular

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Anaconda ✓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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
h1 Trusted Foundation
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
32px · bottom of viewport
h1 for Enterprise AI
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Accelerate Intelligence at Enterprise Sc…
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Millions Rely on Anaconda to Advance The…
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The State of Data Science & AI Report
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Struggling to move AI from pilot to prod…
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Additional Resources for Your AI Journey
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Accelerate AI with Open Source Today
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Anaconda Core
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 AI Catalyst
1.07:1
#000000
on
#0B0B0B
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Trusted Foundation1.07:13.0:1
#000000
#0B0B0B
Fail
h1 for Enterprise AI1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Accelerate Intellige…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Millions Rely on Ana…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 The State of Data Sc…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Struggling to move A…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Additional Resources…1.07:13.0:1
#000000
#0B0B0B
Fail
h2 Accelerate AI with O…1.07:13.0:1
#000000
#0B0B0B
Fail
h3 Anaconda Core1.07:13.0:1
#000000
#0B0B0B
Fail
h3 AI Catalyst1.07:13.0:1
#000000
#0B0B0B
Fail
title Advance AI with Open…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
a Products21.00:14.5:1
#000000
#FFFFFF
Pass
h4 ANACONDA PLATFORM21.00:13.0:1
#000000
#FFFFFF
Pass
a Platform Overview19.72:14.5:1
#000000
#EEFBF2
Pass
span Enterprise Python an…20.37:14.5:1
#000000
#F7FDF9
Pass
a Anaconda Core19.05:14.5:1
#000000
#E4F9EB
Pass
span Python package manag…21.00:14.5:1
#000000
#FFFFFF
Pass
a Anaconda AI Catalyst21.00:14.5:1
#000000
#FFFFFF
Pass
span AI development suite21.00:14.5: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.

B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 23 passed
REVIEW
83

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

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.mega-menu-toggle > div.mega-toggle-blocks-right > div#mega-toggle-block-1 > span.mega-toggle-label div.mega-menu-toggle > div.mega-toggle-blocks-right > div#mega-toggle-block-1 > span.mega-toggle-label

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
ANACONDA PLATFORM div.e-con-inner > div.elementor-element > div.elementor-widget-container > h6.elementor-heading-title
News & Insights div.elementor-element > div.elementor-element > div.elementor-widget-container > h6.elementor-heading-title
Company div.elementor-element > div.elementor-element > div.elementor-widget-container > h6.elementor-heading-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.elementor-element > div.elementor-element > div.elementor-widget-container > a div.elementor-element > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
body.home > meta body.home > meta

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 nav.elementor-nav-menu--main > ul#menu-1-79e96f3 > li.menu-item > a.elementor-item
Terms of Use nav.elementor-nav-menu--main > ul#menu-1-79e96f3 > li.menu-item > a.elementor-item

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●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
●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
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 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
○Form elements have associated labels
○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.
○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
Landmark Structure
43 landmarks
PASS
43 landmarks
Info::
<main> landmark present
Info::
40 <nav> landmark(s) found
Warning::
5 of 40 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "ANACONDA PLATFORM" MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A
Alt Text Quality
3 of 16 images have issues
PASS
3 of 16 images have issues
Warning::
3 image(s) with filename as alt text
Info::
9 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
16 images 4 good alt text 9 decorative 3 generic
IssueCount
filename3 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback