Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Link & Button Quality

1 issue(s) across 208 links and 25 buttons

REVIEW

1 issue(s) across 208 links and 25 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /pdf-alternative

29 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://blog.flipsnack.com; https://help.flipsnack.com; https://academy.flipsnack.com/; /flipbook; /catalog; https://www.capterra.com/p/176854/Flipsnack/; https://www.g2.com/products/flipsnack/reviews?qs=pros-and-cons; https://www.softwareadvice.com/retail/flipsnack-profile/reviews/; https://www.getapp.com/marketing-software/a/flipsnack/; https://sourceforge.net/software/product/Flipsnack/ (+19 more)

178 link(s) with descriptive text

208 links

1 empty

0 generic text

29 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://blog.flipsnack.com	Blog	new tab	Add '(opens in new tab)' to text
https://help.flipsnack.com	Help Center	new tab	Add '(opens in new tab)' to text
https://academy.flipsnack.com/	Flipsnack Academy	new tab	Add '(opens in new tab)' to text
/flipbook	Flipbook Hub	new tab	Add '(opens in new tab)' to text
/catalog	Catalog Hub	new tab	Add '(opens in new tab)' to text
/pdf-alternative	(empty)	empty	Add link text or aria-label
https://www.capterra.com/p/176854/Flipsn…	Flipsnack rating 4.6 out of 5 …	new tab	Add '(opens in new tab)' to text
https://www.g2.com/products/flipsnack/re…	Flipsnack rating 4.7 out of 5 …	new tab	Add '(opens in new tab)' to text
https://www.softwareadvice.com/retail/fl…	Flipsnack rating 4.6 out of 5 …	new tab	Add '(opens in new tab)' to text
https://www.getapp.com/marketing-softwar…	Flipsnack rating 4.6 out of 5 …	new tab	Add '(opens in new tab)' to text
https://sourceforge.net/software/product…	Flipsnack rating 4.9 out of 5 …	new tab	Add '(opens in new tab)' to text
https://www.flipsnack.com/security	security standards	new tab	Add '(opens in new tab)' to text
https://www.flipsnack.com/accessibility	accessible flipbooks	new tab	Add '(opens in new tab)' to text
https://www.flipsnack.com/online-design-…	Flipsnack’s Design Studio	new tab	Add '(opens in new tab)' to text
https://www.flipsnack.com/templates/	editable flipbook templates	new tab	Add '(opens in new tab)' to text
https://legal.flipsnack.com/terms-of-ser…	Terms	new tab	Add '(opens in new tab)' to text
https://legal.flipsnack.com/privacy-poli…	Privacy	new tab	Add '(opens in new tab)' to text
https://developers.flipsnack.com	Developers	new tab	Add '(opens in new tab)' to text
https://blog.flipsnack.com	Blog	new tab	Add '(opens in new tab)' to text
https://help.flipsnack.com	Help	new tab	Add '(opens in new tab)' to text
https://academy.flipsnack.com/	Flipsnack Academy	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/app/flipsnack-mag…	iOS	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Android	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/FlipsnackOffici…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/flipsnack/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/flipsnack	Youtube	new tab	Add '(opens in new tab)' to text
https://twitter.com/Flipsnack	Twitter	new tab	Add '(opens in new tab)' to text
https://pinterest.com/flipsnack/	Pinterest	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/flipsna…	Linkedin	new tab	Add '(opens in new tab)' to text
https://accessibility-widget.pages.dev	Open Accessibility Menu	new tab	Add '(opens in new tab)' to text

203 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/pdf-alternative

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://blog.flipsnack.com; https://help.flipsnack.com; https://academy.flipsnack.com/; /flipbook; /catalog; https://www.capterra.com/p/176854/Flipsnack/; https://www.g2.com/products/flipsnack/reviews?qs=pros-and-cons; https://www.softwareadvice.com/retail/flipsnack-profile/reviews/; https://www.getapp.com/marketing-software/a/flipsnack/; https://sourceforge.net/software/product/Flipsnack/ (+19 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Flipsnack - You don't have access ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 Make flipbooks. Engage. Convert

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Need inspiration? Browse through real fl…

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Meet Flipsnack: the #1 flipbook maker on…

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why Flipsnack as your flipbook maker?

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Design and publish in one flipbook app

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Rated the #1 flipbook maker.

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 By real users

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How to make a flipbook online

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Flipsnack for every team

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Flipbooks that power business growth

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How global brands use Flipsnack

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Flipbook software that scales with you

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Experience the full power of Flipsnack

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Integrate Flipsnack with the tools you u…

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Enterprise-grade security you can trust

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Frequently asked questions

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Create an engaging flipbook online

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Easy to use

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Top-rated support

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Enterprise ready

1.76:1

#000000

#43342A

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Make flipbooks. Enga…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Need inspiration? Br…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Meet Flipsnack: the …	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Why Flipsnack as you…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Design and publish i…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Rated the #1 flipboo…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 By real users	1.76:1	3.0:1	#000000	#43342A	Fail
h2 How to make a flipbo…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Flipsnack for every …	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Flipbooks that power…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 How global brands us…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Flipbook software th…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Experience the full …	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Integrate Flipsnack …	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Enterprise-grade sec…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Frequently asked que…	1.76:1	3.0:1	#000000	#43342A	Fail
h2 Create an engaging f…	1.76:1	3.0:1	#000000	#43342A	Fail
h3 Easy to use	1.76:1	3.0:1	#000000	#43342A	Fail
h3 Top-rated support	1.76:1	3.0:1	#000000	#43342A	Fail
h3 Enterprise ready	1.76:1	3.0:1	#000000	#43342A	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.

Landmark Structure

22 landmarks

PASS

22 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

Heading Hierarchy

68 headings, 1 skip(s)

PASS

68 headings, 1 skip(s)

Single H1 present

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H6 Overview
H6 Solutions
H6 Industries
H6 Features
H6 Make with Flipsnack
H6 Examples
H6 Learn
H6 More resources
H6 Customer Stories
H6 What Customers Say
H6 Featured Reads
H1 Make flipbooks. Engage. Convert
H2 Need inspiration? Browse through real flipbook examples
H2 Meet Flipsnack: the #1 flipbook maker on the market
H2 Why Flipsnack as your flipbook maker?
H3 Easy to use
H3 Top-rated support
H3 Enterprise ready
H2 Design and publish in one flipbook app
H2 Rated the #1 flipbook maker.By real users
H2 How to make a flipbook online
H3 1. Upload PDF
H3 2. Enhance PDF
H3 3. Publish & Share
H3 4. Analyze
H2 Flipsnack for every team
H3 HR & internal comms
H3 Learning & Development
H3 Marketing
H3 Sales
H3 Education
H2 Flipbooks that power business growth
H2 How global brands use Flipsnack
H2 Flipbook software that scales with you
H3 For individuals
H3 For teams
H2 Experience the full power of Flipsnack
H3 Accessibility
H3 Mobile
H3 Engage
H3 Sell
H3 Brand
H3 Share publicly
H3 Track
H2 Integrate Flipsnack with the tools you use
H3 Adobe InDesign
H3 Zapier
H3 MLS
H3 Custom email providers
H3 Google Analytics
H3 Google Tag Manager
H2 Enterprise-grade security you can trust
H2 Frequently asked questions
H3 1. Is Flipsnack free to use?
H3 2. Is Flipsnack safe and reliable?
H3 3. Is Flipsnack accessible?
H3 4. How easy is Flipsnack to work with?
H3 5. What is Flipsnack used for?
H3 6. What is a flipbook?
H3 7. What are the advantages of using flipbooks?
H3 8. How to make a PDF flip like a book?
H3 9. Can you create a flipbook from scratch with Flipsnack?
H3 10. How to convert PDF to flipbook for free?
H2 Create an engaging flipbook online
H3 This website uses cookies
H6 Essentials skipped
H6 Performance
H6 Advertising

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

Alt Text Quality

1 of 163 images have issues

PASS

1 of 163 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

28 decorative image(s) correctly marked

134 image(s) with good alt text

163 images 134 good alt text 28 decorative 1 missing

Issue	Count
missing	1 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

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#fileInput	file	Upload PDF	aria-label
#performance	checkbox	performance checkbox	aria-label
#advertising	checkbox	advertising checkbox	aria-label

A+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 30 passed

PASS

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
This website uses cookies The cookies we use on Flipsnack's website help us pr… `body.page-home > div#cookieNotification`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
4.6/5 `div.col-lg-6 > div.row > div.col-6 > a.ratings-card`
4.7/5 `div.col-lg-6 > div.row > div.col-6 > a.ratings-card`
4.6/5 `div.col-lg-6 > div.row > div.col-4 > a.ratings-card`
4.6/5 `div.col-lg-6 > div.row > div.col-4 > a.ratings-card`
4.9/5 `div.col-lg-6 > div.row > div.col-4 > a.ratings-card`

○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

●`[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

●`[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

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[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 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.

○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.

○Image elements do not have `[alt]` attributes that are redundant text.

○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.

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