Skip to content
https://cargocollective.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
7
REVIEW
1
PASS
5
INFO
0
Checks
13
5 PASS 1 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ 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
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 68/100 — 4 failing, 9 passed
FIX
68

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
Home span > span.left > span.button-link > span
Cargo is a site builder for designers and artists. Templates (portfolios, prese… div#manager > div#home-page > div.fixed-information > span
[Get started] div#home-page > div.fixed-information > span > button.button-link

These are opportunities to improve the legibility of your content.

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
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img
div.site > a > div.site-preview > img div.site > a > div.site-preview > img

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

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>`
●Buttons have an accessible name
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●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 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
○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
○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
○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.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 — File not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
A+
Heading Hierarchy
2 headings
PASS
2 headings
Info::
Single H1 present
  • H1 CargoSite Builder®
  • H2 Explore Sites →Start →
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 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.
A+
Color Contrast (Screenshot)
16 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.

16 pass
Show all checked elements (16)
ElementRatioRequiredFGBGResult
title Cargo20.47:14.5:1
#000000
#FCFCFC
Pass
span Cargo20.47:14.5:1
#000000
#FCFCFC
Pass
span Templates20.47:14.5:1
#000000
#FCFCFC
Pass
span Community20.47:14.5:1
#000000
#FCFCFC
Pass
span Information20.47:14.5:1
#000000
#FCFCFC
Pass
span Start20.47:14.5:1
#000000
#FCFCFC
Pass
span Login ↗20.47:14.5:1
#000000
#FCFCFC
Pass
a Explore Sites20.47:14.5:1
#000000
#FCFCFC
Pass
span →20.47:14.5:1
#000000
#FCFCFC
Pass
span →20.47:14.5:1
#000000
#FCFCFC
Pass
span 22:30:2020.47:14.5:1
#000000
#FCFCFC
Pass
span Cargo is a site buil…20.47:14.5:1
#000000
#FCFCFC
Pass
span We are interested in…20.47:14.5:1
#000000
#FCFCFC
Pass
span Cargo is a site buil…20.47:14.5:1
#000000
#FCFCFC
Pass
span We are interested in…20.47:14.5:1
#000000
#FCFCFC
Pass
a [more...]20.47:14.5:1
#000000
#FCFCFC
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback