launchdarkly.com Accessibility Report

Accessibility audit of launchdarkly.com — scanned on Feb 20, 2026

Technology
0 /100
F Critical Issues

9 issues found across 2 categories

3 Critical 6 Major

WCAG Compliance Overview

Perceivable 4 issues
Operable 3 issues
Understandable 0 issues
Robust 2 issues

Issues Found

Images missing alt text

Critical

Images must have alternative text to convey their meaning to screen reader users.

WCAG 1.1.1
10 element(s) affected
  • <img src="https://images.prismic.io/launchdarkly-marketingsite/Z2B9-JbqstJ98k0i_VestiaireC">
  • <img src="https://launchdarkly-marketingsite.cdn.prismic.io/launchdarkly-marketingsite/d29">
  • <img src="https://launchdarkly-marketingsite.cdn.prismic.io/launchdarkly-marketingsite/cbd">
  • <img src="https://launchdarkly-marketingsite.cdn.prismic.io/launchdarkly-marketingsite/Zkl">
  • <img src="https://launchdarkly-marketingsite.cdn.prismic.io/launchdarkly-marketingsite/4c7">
How to fix

Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

Form inputs missing labels

Critical

Form elements must have associated labels so users know what information to enter.

WCAG 1.3.1
1 element(s) affected
  • <input type="checkbox" name="(no name)">
How to fix

Add <label> elements with matching for attributes, or use aria-label.

Videos missing captions

Critical

Video content must have captions for deaf and hard-of-hearing users.

WCAG 1.2.2
4 element(s) affected
  • <video> "(inline)"
  • <video> "(inline)"
  • <video> "(inline)"
  • <video> "(inline)"
How to fix

Add closed captions or subtitles to all video content.

Heading levels skip order

Major

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
2 element(s) affected
  • <h4> "Docs" (after h2)
  • <h6> "David Tieba" (after h2)
How to fix

Restructure headings to follow sequential order. Don't skip from h1 to h3.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
11 element(s) affected
  • id="checkmark_svg__paint0_linear"
How to fix

Make each id attribute value unique within the page.

No skip navigation link

Major

Pages should have a mechanism to bypass repeated navigation blocks.

WCAG 2.4.1
1 element(s) affected
  • No skip navigation link found
How to fix

Add a 'Skip to main content' link as the first focusable element on the page.

Invalid ARIA attributes

Major

ARIA attributes must be valid and used correctly to work with assistive technologies.

WCAG 4.1.2
4 element(s) affected
  • <video role="image">
How to fix

Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Focus indicator not visible

Major

Interactive elements must have visible focus indicators for keyboard users.

WCAG 2.4.7
1 element(s) affected
  • <div style="...outline:none...">
How to fix

Ensure :focus styles are visible. Don't use outline: none without a replacement.

Generic link text

Major

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
6 element(s) affected
  • <a href="/platform/">learn more</a>
  • <a href="/blog/paramount-improves-developer-productivity-100x/">read more</a>
  • <a href="/case-studies/ccp-games/">read more</a>
  • <a href="/case-studies/dior/">read more</a>
  • <a href="/case-studies/climate-bayer/">read more</a>
How to fix

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Top Priority Fixes

Here are the most impactful changes launchdarkly.com should make to improve accessibility:

  1. #1
    Images missing alt text Critical

    Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

  2. #2
    Videos missing captions Critical

    Add closed captions or subtitles to all video content.

  3. #3
    Form inputs missing labels Critical

    Add <label> elements with matching for attributes, or use aria-label.

Frequently Asked Questions

Is launchdarkly.com accessible?

launchdarkly.com scored 7/100 (grade F) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is launchdarkly.com WCAG compliant?

Our scan found 9 accessibility issues on launchdarkly.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is launchdarkly.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see launchdarkly.com's compliance status.

What accessibility issues does launchdarkly.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for launchdarkly.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.