Skip to content
https://calameo.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
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
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: #ffffff
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
29 headings, 2 skip(s)
REVIEW
29 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Personalization
  • H5 Integrations
  • H5 Studio
  • H5 Conversion
  • H5 Multi-Accounts
  • H5 Share
  • H5 Statistics
  • H5 Subscribers
  • H5 Accessibility
  • H5 Get more, right now!
  • H5 Blog
  • H5 Guided tour
  • H5 Help Center
  • H5 Calaméo Mag
  • H5 Case studies
  • H5 Developers
  • H5 From the blog
  • H1 Digital publishing your way
  • H5 Transform your documents into interactive content instantly and for free! skipped
  • H3 Optimize the reading experience
  • H3 Maximize your growth potential
  • H3 Build a strategy on data
  • H3 Explore even more features
  • H2 Shared with Calaméo
  • H3 Recognized by the most innovative companies
  • H3 Digital publishing your way
  • H5 Company skipped
  • H5 Features
  • H5 Resources

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
18 of 22 images have issues
REVIEW
18 of 22 images have issues
Critical::
18 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
4 image(s) with good alt text
22 images 4 good alt text 18 missing
IssueCount
missing18 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 Calaméo - Sorry, this page doesn't exist ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
15 icon(s) detected
REVIEW
15 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Calaméo - Publishing Platform for Docum…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Features
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Digital publishing y…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Shared with Calaméo21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Optimize the reading…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Maximize your growth…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Build a strategy on …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Explore even more fe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Recognized by the mo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Digital publishing …21.00:13.0:1
#000000
#FFFFFF
Pass
title Calaméo - Publishin…1.00:14.5:1
#000000
#000000
Fail
a Features1.00:14.5:1
#000000
#000000
Fail
p Transform your docum…12.47:14.5:1
#000000
#A0CDEF
Pass
p Connect Calaméo to …15.50:14.5:1
#000000
#C6E1F6
Pass
p Make publications th…18.29:14.5:1
#000000
#E5F1FA
Pass
p Generate valuable le…20.42:14.5:1
#000000
#FAFCFE
Pass
p Manage multiple acco…21.00:14.5:1
#000000
#FFFFFF
Pass
p Disseminate your con…21.00:14.5:1
#000000
#FFFFFF
Pass
p Analyze your audienc…21.00:14.5:1
#000000
#FFFFFF
Pass
p Share exclusive cont…21.00:14.5:1
#000000
#FFFFFF
Pass
p Publish accessible c…20.82:14.5:1
#000000
#FEFEFE
Pass
span All features20.62:14.5:1
#000000
#FCFDFE
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.

C
Lighthouse Accessibility Audits
Action
Score 74/100 — 6 failing, 17 passed
REVIEW
74

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header > div.header-container > div.burger > button.btn header > div.header-container > div.burger > button.btn

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.lSSlideWrapper > ul.list-unstyled > li.clone > img div.lSSlideWrapper > ul.list-unstyled > li.clone > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.lslide > img div.lSSlideWrapper > ul.list-unstyled > li.lslide > img
div.lSSlideWrapper > ul.list-unstyled > li.clone > img div.lSSlideWrapper > ul.list-unstyled > li.clone > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.headline > article.embed > div > iframe section.headline > article.embed > div > iframe

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
header > div.header-container > div.tools > a.btn header > div.header-container > div.tools > a.btn
article > div.foot > div.social-brands > a.btn article > div.foot > div.social-brands > a.btn
article > div.foot > div.social-brands > a.btn article > div.foot > div.social-brands > a.btn
article > div.foot > div.social-brands > a.btn article > div.foot > div.social-brands > a.btn
article > div.foot > div.social-brands > a.btn article > div.foot > div.social-brands > a.btn
article > div.foot > div.social-brands > a.btn article > div.foot > div.social-brands > a.btn

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.

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
Transform your documents into interactive content instantly and for free! main > section.headline > article.markup > h5.text-container
Company article > div.head > div.crosslink > h5

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.lSSlideOuter > ul.lSPager > li.active > a
2 div.lSSlideOuter > ul.lSPager > li > a
3 div.lSSlideOuter > ul.lSPager > li > a
4 div.lSSlideOuter > ul.lSPager > li > a
5 div.lSSlideOuter > ul.lSPager > li > a
6 div.lSSlideOuter > ul.lSPager > li > a
7 div.lSSlideOuter > ul.lSPager > li > a
8 div.lSSlideOuter > ul.lSPager > li > a
9 div.lSSlideOuter > ul.lSPager > li > a
10 div.lSSlideOuter > ul.lSPager > li > a
11 div.lSSlideOuter > ul.lSPager > li > a
12 div.lSSlideOuter > ul.lSPager > li > a
13 div.lSSlideOuter > ul.lSPager > li > a
14 div.lSSlideOuter > ul.lSPager > li > a
Safe mode div.foot > ul.tools > li > a.explicit
Contact us div.foot > ul.tools > li > a
Terms of use div.foot > ul.tools > li > a
Privacy div.foot > ul.tools > li > a
Copyright notices div.foot > ul.tools > li > a
Cookie settings div.foot > ul.tools > li > a

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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
○`<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
○Links are distinguishable without relying on color.
○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.
○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
4 landmarks
PASS
4 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 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
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
searchtext(Search...)placeholder only

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

<input type="text" name="search">

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

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

Send Feedback