Skip to content
https://www.gitguardian.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Form Accessibility
Action
4 of 8 controls have issues
FIX
4 of 8 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="book-demo-field-home">; <input type="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email-2" id="email-2">; <input type="email" name="Email-adress-2" id="Email-adress-2">
Info::
4 control(s) properly labeled
8 controls
4 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#iub-toggle-id-1checkboxNecessaryfor/id
#iub-toggle-id-2checkboxFunctionalityfor/id
#iub-toggle-id-4checkboxMeasurementfor/id
#iub-toggle-id-5checkboxMarketingfor/id
#email-2email(Your Company email address)placeholder only
#Email-adress-2email(Email address)placeholder only
#book-demo-field-homesubmit(none)none
inputsubmit(none)none

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

<input type="submit" id="book-demo-field-home">; <input type="submit">

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="email-2" id="email-2">; <input type="email" name="Email-adress-2" id="Email-adress-2">

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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.
C
Landmark Structure
Action
9 landmarks
REVIEW
9 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
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 (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Secure Every Secret. Govern Every NHI.
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
32px · bottom of viewport
h2 600,000+ developers protected | Fortune …
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The GitGuardian Platform
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Monitor and govern your NHIs and secrets
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Detection without remediation is just no…
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Remediate incidents at scale
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Secure your code from the start
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h2 One Platform.
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Every Tool in Your Stack.
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Empower your application security journe…
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Check out some useful resources
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Non-Human Identity & Secrets Security
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Unified Incident Management
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Detailed Incident Investigation
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Prioritized remediation
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enhanced collaboration
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Time-saving automated playbooks
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Custom remediation guidelines
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Shift left with Git hooks
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Comprehensive scanning
1.17:1
#000000
on
#081633
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Secure Every Secret.…1.17:13.0:1
#000000
#081633
Fail
h2 600,000+ developers …1.17:13.0:1
#000000
#081633
Fail
h2 The GitGuardian Plat…1.17:13.0:1
#000000
#081633
Fail
h2 Monitor and govern y…1.17:13.0:1
#000000
#081633
Fail
h2 Detection without re…1.17:13.0:1
#000000
#081633
Fail
h2 Remediate incidents …1.17:13.0:1
#000000
#081633
Fail
h2 Secure your code fro…1.17:13.0:1
#000000
#081633
Fail
h2 One Platform.1.17:13.0:1
#000000
#081633
Fail
h2 Every Tool in Your S…1.17:13.0:1
#000000
#081633
Fail
h2 Empower your applica…1.17:13.0:1
#000000
#081633
Fail
h2 Check out some usefu…1.17:13.0:1
#000000
#081633
Fail
h3 Non-Human Identity &…1.17:13.0:1
#000000
#081633
Fail
h3 Unified Incident Man…1.17:13.0:1
#000000
#081633
Fail
h3 Detailed Incident In…1.17:13.0:1
#000000
#081633
Fail
h3 Prioritized remediat…1.17:13.0:1
#000000
#081633
Fail
h3 Enhanced collaborati…1.17:13.0:1
#000000
#081633
Fail
h3 Time-saving automate…1.17:13.0:1
#000000
#081633
Fail
h3 Custom remediation g…1.17:13.0:1
#000000
#081633
Fail
h3 Shift left with Git …1.17:13.0:1
#000000
#081633
Fail
h3 Comprehensive scanni…1.17:13.0:1
#000000
#081633
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 25 passed
REVIEW
85

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
Accept all div.iubenda-cs-rationale > div.iubenda-cs-opt-group > div.iubenda-cs-opt-group-consent > button.iubenda-cs-accept-btn

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Policy div.footer-2__form-block > form#wf-form-Newsletter-Form > p.footer__privacy-policy-link > a

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
Ari Kalfus div.home__used-by-grid-item > div.home__used-by-grid-item-bottom > div.mobile-t4-small-text-regular > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#wf-form-Newsletter-Form > div.footer-2__form-inner > div.footer__form-button-wrapper > input.footer__form-button form#wf-form-Newsletter-Form > div.footer-2__form-inner > div.footer__form-button-wrapper > input.footer__form-button

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.home__used-by > div.home__used-by-grid > div.home__used-by-grid-item > a.home__used-by-grid-item-link div.home__used-by > div.home__used-by-grid > div.home__used-by-grid-item > a.home__used-by-grid-item-link
div.home__used-by > div.home__used-by-grid > div.home__used-by-grid-item > a.home__used-by-grid-item-link div.home__used-by > div.home__used-by-grid > div.home__used-by-grid-item > a.home__used-by-grid-item-link
div.home__used-by > div.home__used-by-grid > div.home__used-by-grid-item > a.home__used-by-grid-item-link div.home__used-by > div.home__used-by-grid > div.home__used-by-grid-item > a.home__used-by-grid-item-link
div > div.products-cards__slot > div.products-cards__card > a.products-cards__card-link div > div.products-cards__slot > div.products-cards__card > a.products-cards__card-link
div > div.products-cards__slot > div.products-cards__card > a.products-cards__card-link div > div.products-cards__slot > div.products-cards__card > a.products-cards__card-link
div > div.products-cards__slot > div.products-cards__card > a.products-cards__card-link div > div.products-cards__slot > div.products-cards__card > a.products-cards__card-link

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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 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 type="image">` elements have `[alt]` text
○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.
○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.
○Identical links have the same purpose.
○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
Heading Hierarchy
34 headings, 1 skip(s)
PASS
34 headings, 1 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.
  • H1 Secure Every Secret. Govern Every NHI.
  • H2 600,000+ developers protected | Fortune 500 Trust | 1B+ commits scanned daily
  • H4 Ari Kalfus skipped
  • H4 Theo Cusnir
  • H4 Grégory Maitrallain
  • H2 The GitGuardian Platform
  • H3 Non-Human Identity & Secrets Security
  • H2 Monitor and govern your NHIs and secrets
  • H2 Detection without remediation is just noise
  • H2 Remediate incidents at scale
  • H3 Unified Incident Management
  • H3 Detailed Incident Investigation
  • H3 Prioritized remediation
  • H3 Enhanced collaboration
  • H3 Time-saving automated playbooks
  • H3 Custom remediation guidelines
  • H2 Secure your code from the start
  • H3 Shift left with Git hooks
  • H3 Comprehensive scanning
  • H3 Streamlined workflows
  • H3 Continuous improvement
  • H2 One Platform. Every Tool in Your Stack.
  • H2 Empower your application security journey
  • H2 Check out some useful resources
  • H3 Secrets Management Maturity Model
  • H3 The State of Secrets Sprawl
  • H3 Value Calculator
  • H3 ‍Enterprise Buyer’s Guide for Secrets Detection
  • H3 Subscribe to our newsletter
  • H4 Platform
  • H4 Explore
  • H4 Resources
  • H4 Company
  • H4 Connect

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

A
Alt Text Quality
1 of 85 images have issues
PASS
1 of 85 images have issues
Warning::
1 image(s) with generic alt text
Info::
2 image(s) with alt text over 125 characters
Info::
68 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
85 images 14 good alt text 68 decorative 1 generic
IssueCount
generic1 image(s)
too long2 image(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback