Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-epfubc

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.ansible.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.ansible.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

12 landmarks

REVIEW

12 landmarks

<main> landmark present

No <nav> landmark found

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

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

Heading Hierarchy

Action

19 headings, 1 skip(s)

REVIEW

19 headings, 1 skip(s)

No H1 heading found

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

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Ansible Collaborative
H4 A gathering space to build automation skills and success skipped
H3 Looking for the enterprise product?
H2 What is Ansible?
H2 Automate Policy as Code for consistency and compliance
H2 Learn Ansible skills
H3 Documentation
H2 Interactive labs
H2 Ready to move from patchwork to platform?
H2 Ansible collections
H2 Featured collections
H3 middleware_automation
H2 kubernetes.core
H2 community.vmware
H2 Automation adoption
H2 Ansible ecosystem
H3 Ansible Core
H3 Event-Driven Ansible
H3 Developer tools

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

Link & Button Quality

4 issue(s) across 50 links and 0 buttons

REVIEW

4 issue(s) across 50 links and 0 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /en/technologies/management/ansible

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://galaxy.ansible.com/ui/namespaces/middleware_automation/ ("Learn more"); https://galaxy.ansible.com/ui/repo/published/kubernetes/core/ ("Learn more"); https://galaxy.ansible.com/ui/repo/published/community/vmware/ ("Learn more")

46 link(s) with descriptive text

50 links

1 empty

3 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/en/technologies/management/ansible	(empty)	empty	Add link text or aria-label
https://galaxy.ansible.com/ui/namespaces…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Middleware Automation
https://galaxy.ansible.com/ui/repo/publi…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Core
https://galaxy.ansible.com/ui/repo/publi…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Vmware

46 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/en/technologies/management/ansible

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

https://galaxy.ansible.com/ui/namespaces/middleware_automation/ ("Learn more"); https://galaxy.ansible.com/ui/repo/published/kubernetes/core/ ("Learn more"); https://galaxy.ansible.com/ui/repo/published/community/vmware/ ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

h2 Ansible Collaborative

1.07:1

#000000

#0C0C0C

needs 3.0:1 (large text)

24px · mid-page

title Ansible Collaborative

1.30:1

#000000

#212121

needs 4.5:1 (normal text)

16px · top of page (header area)

a Documentation

1.30:1

#000000

#212121

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Ansible Collaborativ…	1.07:1	3.0:1	#000000	#0C0C0C	Fail
h2 What is Ansible?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Automate Policy as C…	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Learn Ansible skills	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Interactive labs	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Ready to move from p…	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Ansible collections	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Featured collections	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 kubernetes.core	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 community.vmware	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Automation adoption	4.64:1	3.0:1	#000000	#EE0000	Pass
h2 Ansible ecosystem	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Looking for the ente…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Documentation	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 middleware_automatio…	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Ansible Core	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Event-Driven Ansible	4.64:1	3.0:1	#000000	#EE0000	Pass
h3 Developer tools	4.64:1	3.0:1	#000000	#EE0000	Pass
title Ansible Collaborativ…	1.30:1	4.5:1	#000000	#212121	Fail
a Documentation	1.30:1	4.5:1	#000000	#212121	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.

A+

Alt Text Quality

All 9 images OK

PASS

All 9 images OK

2 decorative image(s) correctly marked

7 image(s) with good alt text

9 images 7 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 28 passed

PASS

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#pop-outerdiv02966567197286867 > div#pop-div204118946187821535 > div#pop-div308731378467561114 > iframe#pop-frame09927888474996307 `div#pop-outerdiv02966567197286867 > div#pop-div204118946187821535 > div#pop-div308731378467561114 > iframe#pop-frame09927888474996307`

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
A gathering space to build automation skills and success `div.rh-group--layout > div.rh-group-body > div.rh-generic--component > h4`

These are opportunities to improve keyboard navigation in your application.

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
Digital accessibility `div.dx-col-12 > ul.dx-list-none > li.md:dx-inline > a.ansible-footer-link`
Cookie preferences `ul.dx-list-none > li.md:dx-inline > span#teconsent > a#icon-id07416565977803347`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[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

○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

○`<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

○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.

○`<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.

○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.