Accessibility

D

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

Heading Hierarchy

Action

26 headings, 4 skip(s)

FIX

26 headings, 4 skip(s)

Multiple H1 headings (8 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

H1 Interactive HTML5 Flipping Book Publishing Platform
H3 for Magazines, Catalogs, Brochures and more skipped
H3 Read, upload, and share publications
H3 Convert your PDF into an interactive HTML5 flipbook in minutes.
H1 AnyFlip is trusted by 217,962+ publishers worldwide duplicate H1
H1 How it Works duplicate H1
H3 Learn about AnyFlip in 3 minutes skipped
H1 Engaging & Interactive Page Flipping Examples Created by AnyFlip duplicate H1
H1 Built-In Embedded Bookshelf in Your Website duplicate H1
H1 AnyFlip Main Features duplicate H1
H4 Convert your PDF into an interactive, enjoyable digital flip book in minutes. Create your digital magazines, catalogs, brochures, reports, newsletters and other marketing content with modern interacti skipped
H4 Custom Domain
H4 Publication Download
H4 Publication Protection
H4 Google Analytics Integration
H4 Cloud Hosting Service
H4 Online Bookshelf
H4 Table of Contents
H4 Magazine Subscription
H4 Social Media Sharing
H1 Easily create the most stunning digital publications and share them with the world online duplicate H1
H1 Our customers have a lot to say about us duplicate H1
H4 We really value our customers and their opinions, we welcome feedback and act on feature requests. skipped
H4 SECURE
H4 100% CLEAN
H4 SUPPORT SERVICE

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

D

Link & Button Quality

Action

6 issue(s) across 77 links and 1 buttons

FIX

6 issue(s) across 77 links and 1 buttons

4 link(s) with no accessible text

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

Got: /; https://www.capterra.com/p/210554/AnyFlip/reviews/; https://www.g2.com/products/anyflip/reviews; https://twitter.com/any_flip

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /example/ ("Learn More")

18 link(s) open in new tab without warning

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

Got: /explore?#latest; /community/; https://mangoanimate.com/ai; https://mangoanimate.com/ai/talking-photo; https://mangoanimate.com/ai/video-face-swap; https://mangoanimate.com/ai/avatars; https://mangoanimate.com/ai/talking-animals; https://mangoanimate.com/ai/talking-cartoon; https://mangoanimate.com/products/ai; https://mangoanimate.com/ (+8 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.nav-toggle (#74 on page)

54 link(s) with descriptive text

77 links

4 empty

1 generic text

18 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://www.capterra.com/p/210554/AnyFli…	(empty)	empty	Add link text or aria-label
https://www.g2.com/products/anyflip/revi…	(empty)	empty	Add link text or aria-label
/example/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Example
/explore?#latest	Latest Flips	new tab	Add '(opens in new tab)' to text
/community/	Community	new tab	Add '(opens in new tab)' to text
https://twitter.com/any_flip	(empty)	empty	Add link text or aria-label
https://mangoanimate.com/ai	Mango AI	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/ai/talking-phot…	Talking Photo	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/ai/video-face-s…	Video Face Swap	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/ai/avatars	AI Avatars	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/ai/talking-anim…	Talking Animals	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/ai/talking-cart…	Talking Cartoon	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/products/ai	AI Video Generator	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/	AI Animation Generator	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/ai/video-enhanc…	AI Video Enhancer	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/ai/video-cartoo…	Video Cartoonizer	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/ai/singing-phot…	Singing Photos	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/products/wm	Whiteboard Animation Software	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/products/am	Animation Maker	new tab	Add '(opens in new tab)' to text
https://mangoanimate.com/blog/	Mango Animate Blog	new tab	Add '(opens in new tab)' to text
https://www.flipbuilder.com/	Flipbook Software	new tab	Add '(opens in new tab)' to text
https://fliphtml5.com/	Flipbook Maker	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

54 links and buttons have descriptive text

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

/; https://www.capterra.com/p/210554/AnyFlip/reviews/; https://www.g2.com/products/anyflip/reviews; https://twitter.com/any_flip

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

Generic link text like 'click here' doesn't describe the destination.

/example/ ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

/explore?#latest; /community/; https://mangoanimate.com/ai; https://mangoanimate.com/ai/talking-photo; https://mangoanimate.com/ai/video-face-swap; https://mangoanimate.com/ai/avatars; https://mangoanimate.com/ai/talking-animals; https://mangoanimate.com/ai/talking-cartoon; https://mangoanimate.com/products/ai; https://mangoanimate.com/ (+8 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

Icon-only buttons need an aria-label so screen readers can announce them.

button.nav-toggle (#74 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

F

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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 62/100 — 9 failing, 13 passed

FIX

62

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
div.nav-bar > div.container > div.nav-bar-collapse > button.nav-toggle `div.nav-bar > div.container > div.nav-bar-collapse > button.nav-toggle`

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.af-main > div.af-home-ad > div.af-home-ad-inner > img `div.af-main > div.af-home-ad > div.af-home-ad-inner > img`
div.af-home-about-inner > div.af-home-about-video > div.img-container > img `div.af-home-about-inner > div.af-home-about-video > div.img-container > img`
ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img `ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img`
ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img `ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img`
ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img `ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img`
ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img `ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img`
ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img `ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img`
ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img `ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img`
ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img `ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img`
ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img `ul.af-home-example-panel > li.af-home-explames-demo > div > img.af-home-explames-demo-img`
li.col-sm-4 > div.feature-icon > div.img-container > img `li.col-sm-4 > div.feature-icon > div.img-container > img`
li.col-sm-4 > div.feature-icon > div.img-container > img `li.col-sm-4 > div.feature-icon > div.img-container > img`
li.col-sm-4 > div.feature-icon > div.img-container > img `li.col-sm-4 > div.feature-icon > div.img-container > img`
li.col-sm-4 > div.feature-icon > div.img-container > img `li.col-sm-4 > div.feature-icon > div.img-container > img`
li.col-sm-4 > div.feature-icon > div.img-container > img `li.col-sm-4 > div.feature-icon > div.img-container > img`
li.col-sm-4 > div.feature-icon > div.img-container > img `li.col-sm-4 > div.feature-icon > div.img-container > img`
li.col-sm-4 > div.feature-icon > div.img-container > img `li.col-sm-4 > div.feature-icon > div.img-container > img`
li.col-sm-4 > div.feature-icon > div.img-container > img `li.col-sm-4 > div.feature-icon > div.img-container > img`
li.col-sm-4 > div.feature-icon > div.img-container > img `li.col-sm-4 > div.feature-icon > div.img-container > 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
div.af-home-bookcase > div.af-home-bookcase-inner > div.bookcase-container > iframe `div.af-home-bookcase > div.af-home-bookcase-inner > div.bookcase-container > 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
div.container > div.nav-bar-collapse > div.af-left > a.nav-logo-link `div.container > div.nav-bar-collapse > div.af-left > a.nav-logo-link`
`div.af-home-banner-down > div.af-home-banner-down-left > div.evaluate > a`
div.af-home-banner-down > div.af-home-banner-down-left > div.evaluate > a `div.af-home-banner-down > div.af-home-banner-down-left > div.evaluate > a`
div.af-bottom-col > div.contact-social > div.social-networks > a.af-bottom-twitter-share `div.af-bottom-col > div.contact-social > div.social-networks > a.af-bottom-twitter-share`

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.

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
Learn More `div.af-home-explames > div.af-home-explames-case > a > div.af-home-explames-more`
GET STARTED NOW FOR FREE `body.en > div.af-main > div.af-home-online > div.af-home-online-btn`
Read More Reviews `div.af-main > div.af-home-customers > a > div.af-home-customers-btn`
--Kate `div.user-1 > div.desc-content > div.desc-info > span.customer-name`
--Bill `div.user-2 > div.desc-content > div.desc-info > span.customer-name`
--Matt `div.user-3 > div.desc-content > div.desc-info > span.customer-name`

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
for Magazines, Catalogs, Brochures and more `div.sh5-table-centered > div.af-home-banner-inner > div.af-home-banner-title > h3`
Learn about AnyFlip in 3 minutes `div.af-home-about > div.af-home-about-inner > div.af-home-about-title > h3`
Convert your PDF into an interactive, enjoyable digital flip book in minutes. C… `div.af-main > div.af-home-features > div.af-home-features-title > h4`
We really value our customers and their opinions, we welcome feedback and act o… `div.af-main > div.af-home-customers > div.af-home-customers-title > h4`

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Burda Style UA BBC Wildlife Magazine Home Spirit Catalog World Trav… `div.af-main > div.af-home-explames > div.af-home-explames-case > ul.af-home-example-panel`

These are opportunities to improve the experience of reading tabular or list data using 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-*]` 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

●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

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

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

●Touch targets have sufficient size and spacing.

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

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

C

Alt Text Quality

Action

23 of 31 images have issues

REVIEW

23 of 31 images have issues

23 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 decorative image(s) correctly marked

6 image(s) with good alt text

31 images 6 good alt text 2 decorative 23 missing

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

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) without accessible label

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

Got: <input type="text">; <input type="text">

2 controls

0 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
input	text	(none)	none
input	text	(none)	none

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

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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA

title Free Flip Book Maker; PDF to HTML5 Page …

1.37:1

#000000

on

#252525

needs 4.5:1 (normal text)

16px · top of page (header area)

a Quick Upload

1.37:1

#000000

on

#252525

needs 4.5:1 (normal text)

16px · top of page (header area)

a Explore

1.37:1

#000000

on

#252525

needs 4.5:1 (normal text)

16px · top of page (header area)

a Features

1.33:1

#000000

on

#242224

needs 4.5:1 (normal text)

16px · top of page (header area)

a Support

1.28:1

#000000

on

#241E22

needs 4.5:1 (normal text)

16px · above the fold

a Contact Us

1.23:1

#000000

on

#231920

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Interactive HTML5	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h1 Flipping Book Publis…	19.95:1	3.0:1	#000000	#F9F9F9	Pass
h1 AnyFlip is trusted b…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 publishers worldwide	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 How it Works	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Engaging & Interacti…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Built-In Embedded Bo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 AnyFlip Main Feature…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Easily create the mo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Our customers have a…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 for Magazines, Catal…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Read, upload, and sh…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Convert your PDF int…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Learn about AnyFlip …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Free Flip Book Maker…	1.37:1	4.5:1	#000000	#252525	Fail
a Quick Upload	1.37:1	4.5:1	#000000	#252525	Fail
a Explore	1.37:1	4.5:1	#000000	#252525	Fail
a Features	1.33:1	4.5:1	#000000	#242224	Fail
a Support	1.28:1	4.5:1	#000000	#241E22	Fail
a Contact Us	1.23:1	4.5:1	#000000	#231920	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.