Skip to content
https://launchdarkly.com

Accessibility

· 12 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
6
PASS
2
INFO
0
Checks
12
2 PASS 6 REVIEW 4 FIX
D
Form Accessibility
Action
6 of 6 controls have issues
FIX
6 of 6 controls have issues
Critical::
5 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">; <input type="checkbox" id="activate-menu">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="EmailInput">
6 controls
0 labeled
1 placeholder only
5 unlabeled
ControlTypeLabelMethod
EmailInputemail(Email address)placeholder only
#CybotCookiebotDialogBodyLevelButtonPreferencescheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticscheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingcheckbox(none)none
#activate-menucheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessarycheckbox(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessary">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferences">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatistics">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketing">; <input type="checkbox" id="activate-menu">

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

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

<input type="email" name="EmailInput">

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

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: #405bff
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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
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.
B
Heading Hierarchy
66 headings, 2 skip(s)
REVIEW
66 headings, 2 skip(s)
Info::
Single H1 present
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 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Set cookie preference
  • H1 Move at AI speed. Stay in control.
  • H2 Where features and AI control start.
  • H3 Safely get features and agents to the right users.
  • H3 See what's happening in real time.
  • H3 Learn and improve continuously.
  • H3 Watch to learn how it all works.
  • H3 Built for developers.
  • H3 Backed by data.
  • H3 Trusted in production.
  • H3 Learn how the best dev teams ship fast, and stay in control.
  • H2 Say goodbye to 2am fire drills.
  • H2 84%
  • H2 48%
  • H2 63%
  • H2 11 quadrillion
  • H2 Copy,paste,go.
  • H4 Docs skipped
  • H4 Demo Project
  • H4 Discord
  • H2 Build like the best.
  • H3 Paramount improves developer productivity 100X.
  • H3 6-7
  • H3 CCP Games creates self-serve experimentation.
  • H3 Increased
  • H3 Dior shortens time to market from 15 minutes to instant updates.
  • H3 < Zero
  • H3 Bayer’s digital farming arm improves reliability for critical apps.
  • H3 Improved
  • H3 HP standardizes and scales releases with LaunchDarkly.
  • H3 98%
  • H2 We’ve got receipts.
  • H6 David Tieba skipped
  • H6 Artie Lee
  • H6 Nick Herring
  • H6 Nathan Gray
  • H6 Justin Cataldo
  • H6 Manjari Ranganathan
  • H6 Rema Morgan-Aluko
  • H6 Sebastien Thibaud
  • H6 Greg Ratner
  • H6 Riley Duncan
  • H6 David Tieba
  • H6 Artie Lee
  • H6 Nick Herring
  • H6 Nathan Gray
  • H6 Justin Cataldo
  • H6 Manjari Ranganathan
  • H6 Rema Morgan-Aluko
  • H6 Sebastien Thibaud
  • H6 Greg Ratner
  • H6 Riley Duncan
  • H6 David Tieba
  • H6 Artie Lee
  • H6 Nick Herring
  • H6 Nathan Gray
  • H6 Justin Cataldo
  • H6 Manjari Ranganathan
  • H6 Rema Morgan-Aluko
  • H6 Sebastien Thibaud
  • H6 Greg Ratner
  • H6 Riley Duncan
  • H3 Try out some flags on Toggle.
  • H4 enable-toggle-thumbs-up
  • H4 swap-shoe-color
  • H2 Move at AI speed.Stay in control.

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
Alt Text Quality
Action
31 of 307 images have issues
REVIEW
31 of 307 images have issues
Critical::
30 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
275 image(s) with good alt text
307 images 275 good alt text 1 decorative 1 generic 30 missing
IssueCount
missing30 image(s)
generic1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | LaunchDarkly ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
18 icon(s) detected
REVIEW
18 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
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 28 passed
REVIEW
87

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
/ / div.styles-module--slideItem--40ae7 > div.styles-module--quoteContainer--5e366 > div.styles-module--quote--8cab0 > p.styles-module--quoteSlashes--c8341
©2026 Catamorphic Co. footer.styles-module--footer--df195 > div.styles-module--container--f7e03 > div.styles-module--socialMedia--ee6bc > p.styles-module--copyright--1d439

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
Docs div.styles-module--linkBoxes--5d678 > a.styles-module--linkBox--78baf > div > h4
David Tieba span.styles-module--linkBlock--4d82c > div.styles-module--quoteContainer--e6aa4 > div > h6

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
span.styles-module--linkBlock--4d82c > div.styles-module--quoteContainer--e6aa4 > div.styles-module--imgContainer--aac1b > img.vestiaire-collective span.styles-module--linkBlock--4d82c > div.styles-module--quoteContainer--e6aa4 > div.styles-module--imgContainer--aac1b > img.vestiaire-collective

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.header-nav > nav.styles-module--nav--73dba > div.styles-module--navInner--8e961 > input#activate-menu header.header-nav > nav.styles-module--nav--73dba > div.styles-module--navInner--8e961 > input#activate-menu

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.

○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
●Buttons have an accessible name
●`[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
●`[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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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 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
○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
○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.
○Identical links have the same purpose.
○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
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 NAV "Main" MAIN CONTENTINFO footer

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

A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Feature Flag & Toggle Management | LaunchDarkly
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Feature Flag & Toggle Management | LaunchDarkly ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Feature Flag & Toggle Management | LaunchDarkly Display Mode standalone Theme Color #405BFF Background Color #191919 Icons 8 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback