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 3 REVIEW 5 FIX

Link & Button Quality

Action

8 issue(s) across 91 links and 12 buttons

FIX

8 issue(s) across 91 links and 12 buttons

2 link(s) with generic text

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

Got: /features/ai/?click_source=logged_element&page_location=real_creative_freedom&element_text=learn_more ("Learn more"); /features/ai/?click_source=logged_element&page_location=real_creative_freedom&element_text=learn_more ("Learn more")

2 image-only link(s) without alt text

6 button(s) with no accessible text

87 link(s) with descriptive text

91 links

0 empty

2 generic text

0 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
/?click_source=logged_element&page_locat…	Prezi homepage	img no alt	Add alt attribute to the image
/features/ai/?click_source=logged_elemen…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: ?Click Source=Logged Element&Page Location=Real Creative Freedom&Element Text=Learn More
/features/ai/?click_source=logged_elemen…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: ?Click Source=Logged Element&Page Location=Real Creative Freedom&Element Text=Learn More
/?click_source=logged_element&page_locat…	Prezi Homepage	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

93 links and buttons have descriptive text

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

/features/ai/?click_source=logged_element&page_location=real_creative_freedom&element_text=learn_more ("Learn more"); /features/ai/?click_source=logged_element&page_location=real_creative_freedom&element_text=learn_more ("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

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

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

Landmark Structure

Action

8 landmarks

REVIEW

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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.

Page Structure — as a screen reader sees it

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | Prezi ✓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

A+

Heading Hierarchy

39 headings

PASS

39 headings

Single H1 present

H1 Better presentations, faster with AI
H2 Business
H2 Educators
H2 Students
H2 Build memorable presentations for modern teams and schools with Prezi’s AI presentation tool.
H2 Prezi has set the standard for amazing presentations for 15 years. Now, we’re redefining the future of presenting with AI.
H2 Prezi has set the standard for amazing presentations for 15 years. Now, we’re redefining the future of presenting with AI.
H3 From idea to presentation, effortlessly
H3 Design with AI
H3 Expert advice
H3 Visualize anything
H3 Everything you need to create what you want
H3 Transform content
H3 Show it perfectly
H3 Design beautifully
H3 Stand out from the crowd
H3 Engage audiences
H3 Move in any order
H3 Present anywhere
H2 Real presenters win with Prezi
H3 4 out of 5
H3 3 out of 4
H3 91%
H2 See why our customers love us
H2 See why our customers love us
H2 The future of AI-first presentations is here.
H2 Frequently asked questions
H3 What is Prezi’s AI presentation maker?
H3 How does Prezi's AI presentation designer work?
H3 Can Prezi create a PowerPoint (PPT) with AI?
H3 Can I turn an existing document into a presentation with AI?
H3 Is Prezi a free AI presentation tool?
H3 How is Prezi different from other AI presentation generators?
H3 What types of presentations can I create with Prezi AI?
H3 Does Prezi AI help with slide structure and talking points?
H3 Can I edit the AI-generated presentation?
H3 Is Prezi good for creating slide decks with AI for teams?
H3 What should I include in a prompt for the best AI presentation results?
H3 Is Prezi AI suitable for beginners who are new to presentation design?

A+

Alt Text Quality

All 80 images OK

PASS

All 80 images OK

1 image(s) with alt text over 125 characters

2 decorative image(s) correctly marked

77 image(s) with good alt text

80 images 77 good alt text 2 decorative

Issue	Count
too long	1 image(s)

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <textarea name="Title" id="ai-title">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#ai-title	textarea	(Ask Prezi to)	placeholder only

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

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

A+

Color Contrast (Screenshot)

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Better presentations…	20.04:1	3.0:1	#000000	#F8FECC	Pass
h2 Business	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Educators	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Students	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Build memorable pres…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Prezi has set the st…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Prezi has set the st…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Real presenters win …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 See why our customer…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 See why our customer…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The future of AI-fir…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Frequently asked que…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 From idea to present…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Design with AI	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Expert advice	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Visualize anything	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Everything you need …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Transform content	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Show it perfectly	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Design beautifully	21.00:1	3.0:1	#000000	#FFFFFF	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.

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 27 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.

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.section-header > div.max-width-xxlarge > a.button-new > div`
Try Prezi for free `div.container-small > div.cta_component > a.button-new > div`

These are opportunities to improve the legibility of your content.

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

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

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

●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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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 are contained by their required parent element

○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

○Links are distinguishable without relying on color.

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

○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

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

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