Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

Link & Button Quality

Action

9 issue(s) across 237 links and 45 buttons

FIX

9 issue(s) across 237 links and 45 buttons

1 link(s) with no accessible text

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

6 link(s) with generic text

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

Got: http://circleci.com/blog/smarter-testing/ ("Learn more"); http://circleci.com/blog/smarter-testing/ ("Learn more"); https://circleci.com/blog/introducing-chunk/ ("Learn more"); https://circleci.com/product/mcp/ ("Learn more"); https://circleci.com/blog/platform-toolkit/ ("Learn more"); https://circleci.com/docs/guides/deploy/set-up-rollbacks/ ("Learn more")

10 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://support.circleci.com/hc/en-us/; https://discuss.circleci.com/; https://support.circleci.com/hc/en-us/; https://discuss.circleci.com/; https://support.circleci.com/hc/en-us/; https://discuss.circleci.com/; https://brand.circleci.com/613faff00/p/14ba30-circleci-brand; https://www.linkedin.com/company/circleci; https://github.com/circleci; https://twitch.tv/circleci

2 button(s) with no accessible text

220 link(s) with descriptive text

237 links

1 empty

6 generic text

10 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://support.circleci.com/hc/en-us/	Support portal	new tab	Add '(opens in new tab)' to text
https://discuss.circleci.com/	Discuss forum	new tab	Add '(opens in new tab)' to text
https://support.circleci.com/hc/en-us/	Support portal	new tab	Add '(opens in new tab)' to text
https://discuss.circleci.com/	Discuss forum	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
http://circleci.com/blog/smarter-testing…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Smarter Testing
http://circleci.com/blog/smarter-testing…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Smarter Testing
https://circleci.com/blog/introducing-ch…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Introducing Chunk
https://circleci.com/product/mcp/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Mcp
https://circleci.com/blog/platform-toolk…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Platform Toolkit
https://circleci.com/docs/guides/deploy/…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Set Up Rollbacks
https://support.circleci.com/hc/en-us/	Get support	new tab	Add '(opens in new tab)' to text
https://discuss.circleci.com/	Discuss forum	new tab	Add '(opens in new tab)' to text
https://brand.circleci.com/613faff00/p/1…	CircleCI brand	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/circlec…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://github.com/circleci	GitHub	new tab	Add '(opens in new tab)' to text
https://twitch.tv/circleci	Twitch	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

263 links and buttons have descriptive text

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

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.

http://circleci.com/blog/smarter-testing/ ("Learn more"); http://circleci.com/blog/smarter-testing/ ("Learn more"); https://circleci.com/blog/introducing-chunk/ ("Learn more"); https://circleci.com/product/mcp/ ("Learn more"); https://circleci.com/blog/platform-toolkit/ ("Learn more"); https://circleci.com/docs/guides/deploy/set-up-rollbacks/ ("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

Add '(opens in new tab)' to link text or aria-label.

https://support.circleci.com/hc/en-us/; https://discuss.circleci.com/; https://support.circleci.com/hc/en-us/; https://discuss.circleci.com/; https://support.circleci.com/hc/en-us/; https://discuss.circleci.com/; https://brand.circleci.com/613faff00/p/14ba30-circleci-brand; https://www.linkedin.com/company/circleci; https://github.com/circleci; https://twitch.tv/circleci

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

No banner (header) landmark

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

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

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

59 headings, 2 skip(s)

REVIEW

59 headings, 2 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H2 → H6 (missing H3)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 (empty)
H2 Overview
H2 Features
H2 Integrations
H2 Role
H2 Use case
H2 Company size
H2 Developers
H2 Explore
H2 Community
H2 Benefits
H2 Compare
H2 Company
H2 Overview
H2 Features
H2 Integrations
H2 Role
H2 Use case
H2 Company size
H2 Developers
H2 Explore
H2 Community
H2 Benefits
H2 Compare
H2 Company
H2 Explore
H1 AI code make you nervous?
H2 Trusted by
H2 Confidence in every rollback prompt change test merge
H2 Any app, deployed anywhere, at any scale
H3 Confidence meets AI speed
H3 No-think CI/CD
H3 Scale without compromise
H2 Ship at AI speed, confidently
H2 Join 2mil+ devs
H3 And get that green build feeling
H2 Learn more
H3 2025 State of Software Delivery
H3 CircleCI onboarding toolkit
H3 CircleCI delivers 664% ROI
H1 97% faster test runs duplicate H1
H3 Connect AI tools with the CircleCI MCP Server skipped
H3 Platform Toolkit: Standardize at scale
H3 Recover fast with rollback pipelines
H2 Keep up with the latest releases
H3 Docker Default Updated to Docker 28
H3 Xcode 26.5.0 Beta 1 Available
H3 Xcode 26.4.0 Available
H3 GitHub Enterprise Server integration with CircleCI Cloud now available in Preview
H3 Branch selector bug fixed in Chunk task page
H3 Product Roadmap
H3 Key milestones
H2 >build the future
H6 Product skipped
H6 Hosting options
H6 Solutions
H6 Resources
H6 Pricing
H6 Company

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Form Accessibility

Action

4 of 5 controls have issues

REVIEW

4 of 5 controls have issues

4 control(s) without accessible label

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

Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessary">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferences">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatistics">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketing">

1 control(s) properly labeled

5 controls

1 labeled

0 placeholder only

4 unlabeled

Control	Type	Label	Method
input	search	Search	aria-label
#CybotCookiebotDialogBodyLevelButtonPreferences	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonStatistics	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonMarketing	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonNecessary	checkbox	(none)	none

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 - Page Not Found - CircleCI ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

10 icon(s) detected

REVIEW

10 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Alt Text Quality

All 45 images OK

PASS

All 45 images OK

44 decorative image(s) correctly marked

1 image(s) with good alt text

45 images 1 good alt text 44 decorative

All images have appropriate alt text.

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: CircleCI

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name CircleCI ✓192×192 icon ✓512×512 icon ✓Start URL https://circleci.com/ ✓Display Mode standalone ✓

Name CircleCI Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(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)

Element	Ratio	Required	FG	BG	Result
h1 AI code make you ner…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 97% faster test runs	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Overview	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Features	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Integrations	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Role	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Use case	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Company size	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Developers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Community	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Benefits	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Compare	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Company	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Overview	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Features	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Integrations	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Role	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Use case	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Company size	21.00:1	3.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.

Lighthouse Accessibility Audits

Score 94/100 — 1 failing, 23 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.

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
head > meta `head > meta`

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

●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

●Links are distinguishable without relying on color.

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

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

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