Skip to content
https://carrd.co

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 footer

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

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
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 Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
2 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 2 <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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title File not found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light only
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta light only ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only
h1 Carrd
2.55:1
#000000
on
#514879
needs 3.0:1 (large text)
32px · mid-page
h2 Log In
2.27:1
#000000
on
#2A4582
needs 3.0:1 (large text)
24px · top of page (header area)
h2 Sign Up
2.25:1
#000000
on
#2A4482
needs 3.0:1 (large text)
24px · above the fold
h2 Documentation
2.21:1
#000000
on
#294381
needs 3.0:1 (large text)
24px · above the fold
h2 Changelog
2.24:1
#000000
on
#31437F
needs 3.0:1 (large text)
24px · above the fold
h2 Go Pro!
2.37:1
#000000
on
#3C467E
needs 3.0:1 (large text)
24px · above the fold
h2 Contact
2.38:1
#000000
on
#43457C
needs 3.0:1 (large text)
24px · mid-page
h2 pretty much anything
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Simple
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Responsive
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Free
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Optional: Go Pro!
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sound good?
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Custom Domains
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
19px · bottom of viewport
h3 More Sites
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Forms
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Widgets + Embeds
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Site Analytics
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
19px · bottom of viewport
h3 No Branding
2.69:1
#000000
on
#654771
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Carrd2.55:13.0:1
#000000
#514879
Fail
h2 Log In2.27:13.0:1
#000000
#2A4582
Fail
h2 Sign Up2.25:13.0:1
#000000
#2A4482
Fail
h2 Documentation2.21:13.0:1
#000000
#294381
Fail
h2 Changelog2.24:13.0:1
#000000
#31437F
Fail
h2 Go Pro!2.37:13.0:1
#000000
#3C467E
Fail
h2 Contact2.38:13.0:1
#000000
#43457C
Fail
h2 Build one-page sites…3.09:13.0:1
#000000
#6B517B
Pass
h2 pretty much anything2.69:13.0:1
#000000
#654771
Fail
h2 Simple2.69:13.0:1
#000000
#654771
Fail
h2 Responsive2.69:13.0:1
#000000
#654771
Fail
h2 Free2.69:13.0:1
#000000
#654771
Fail
h2 Optional: Go Pro!2.69:13.0:1
#000000
#654771
Fail
h2 Sound good?2.69:13.0:1
#000000
#654771
Fail
h3 Custom Domains2.69:13.0:1
#000000
#654771
Fail
h3 More Sites2.69:13.0:1
#000000
#654771
Fail
h3 Forms2.69:13.0:1
#000000
#654771
Fail
h3 Widgets + Embeds2.69:13.0:1
#000000
#654771
Fail
h3 Site Analytics2.69:13.0:1
#000000
#654771
Fail
h3 No Branding2.69:13.0:1
#000000
#654771
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.

C
Lighthouse Accessibility Audits
Action
Score 73/100 — 4 failing, 10 passed
REVIEW
73

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
Choose a Starting Point div.content > ul.action-list > li > a.button
Choose a Starting Point section#cta > ul.action-list > li > a.button
Home footer.site-footer > ul.menu-list > li > a
Terms footer.site-footer > ul.menu-list > li > a
Privacy footer.site-footer > ul.menu-list > li > a
Contact footer.site-footer > ul.menu-list > li > a
© Carrd Inc. All rights reserved. body#website > footer.site-footer > p.copyright

These are opportunities to improve the legibility of your content.

Names and labels

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
body#website > header.site-header > nav > a body#website > header.site-header > nav > a

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.

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` 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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○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.
○`[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.
○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+
Heading Hierarchy
19 headings
PASS
19 headings
Info::
Single H1 present
  • H2 Log In
  • H2 Sign Up
  • H2 Documentation
  • H2 Changelog
  • H2 Go Pro!
  • H2 Contact
  • H1 Carrd
  • H2 Build one-page sites for pretty much anything
  • H2 Simple
  • H2 Responsive
  • H2 Free
  • H2 Optional: Go Pro!
  • H3 Custom Domains
  • H3 More Sites
  • H3 Forms
  • H3 Widgets + Embeds
  • H3 Site Analytics
  • H3 No Branding
  • H2 Sound good?
A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
10 image(s) with good alt text
10 images 10 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback