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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: Slides

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name Slides ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode standalone ✓

Name Slides Display Mode standalone Theme Color #444444 Icons 2 icon(s)

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 ✗

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

No <nav> landmark 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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Slides: 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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'>.

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #4a0099 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

h1 Make better presentations

2.66:1

#000000

#3241C1

needs 3.0:1 (large text)

32px · above the fold

h2 Create exceptional slide decks in half t…

2.86:1

#000000

#2F48C6

needs 3.0:1 (large text)

24px · mid-page

title Create and Share Presentations for Free …

1.76:1

#000000

#48039B

needs 4.5:1 (normal text)

16px · top of page (header area)

span Presentations

1.80:1

#000000

#47089E

needs 4.5:1 (normal text)

16px · top of page (header area)

span Templates

1.83:1

#000000

#450DA1

needs 4.5:1 (normal text)

16px · top of page (header area)

span Features

1.86:1

#000000

#4312A4

needs 4.5:1 (normal text)

16px · top of page (header area)

span Teams

1.91:1

#000000

#4117A7

needs 4.5:1 (normal text)

16px · above the fold

span Pricing

1.97:1

#000000

#3F1CAB

needs 4.5:1 (normal text)

16px · above the fold

span Log in

2.03:1

#000000

#3E21AE

needs 4.5:1 (normal text)

16px · above the fold

span Sign up

2.10:1

#000000

#3C26B1

needs 4.5:1 (normal text)

16px · above the fold

span Log in

2.18:1

#000000

#3A2BB4

needs 4.5:1 (normal text)

16px · above the fold

span Sign up

2.27:1

#000000

#3830B7

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Make better presenta…	2.66:1	3.0:1	#000000	#3241C1	Fail
h2 Create exceptional s…	2.86:1	3.0:1	#000000	#2F48C6	Fail
h2 Slides AI	6.74:1	3.0:1	#000000	#6F90E0	Pass
h2 Looking for inspirat…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Try our slide genera…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Meet your new favori…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Present like never b…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Work better, togethe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The best tool for de…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Join over 2 million …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Create and Share Pre…	1.76:1	4.5:1	#000000	#48039B	Fail
span Presentations	1.80:1	4.5:1	#000000	#47089E	Fail
span Templates	1.83:1	4.5:1	#000000	#450DA1	Fail
span Features	1.86:1	4.5:1	#000000	#4312A4	Fail
span Teams	1.91:1	4.5:1	#000000	#4117A7	Fail
span Pricing	1.97:1	4.5:1	#000000	#3F1CAB	Fail
span Log in	2.03:1	4.5:1	#000000	#3E21AE	Fail
span Sign up	2.10:1	4.5:1	#000000	#3C26B1	Fail
span Log in	2.18:1	4.5:1	#000000	#3A2BB4	Fail
span Sign up	2.27:1	4.5:1	#000000	#3830B7	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.

Heading Hierarchy

13 headings, 1 skip(s)

PASS

13 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Make better presentations
H2 Create exceptional slide decks in half the time using intuitive design tools and machine learning. Present remotely or on-site.
H2 Slides AI
H2 Looking for inspiration?Try our slide generator.
H2 Meet your new favorite editor
H2 Present like never before
H2 Work better, together
H2 The best tool for developers
H2 Join over 2 million creators
H4 Tour skipped
H4 Help
H4 Company
H4 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

Alt Text Quality

1 of 3 images have issues

PASS

1 of 3 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with good alt text

3 images 2 good alt text 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

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

46 links, 1 buttons — all OK

PASS

46 links, 1 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://help.slides.com; https://help.slides.com/knowledgebase; https://twitter.com/slides; https://facebook.com/slidesapp

42 link(s) with descriptive text

46 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://help.slides.com	Forum	new tab	Add '(opens in new tab)' to text
https://help.slides.com/knowledgebase	Knowledge Base	new tab	Add '(opens in new tab)' to text
https://twitter.com/slides	Go to Slides' Twitter profile	new tab	Add '(opens in new tab)' to text
https://facebook.com/slidesapp	Go to Slides' Facebook profile	new tab	Add '(opens in new tab)' to text

43 links and buttons have descriptive text

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

https://help.slides.com; https://help.slides.com/knowledgebase; https://twitter.com/slides; https://facebook.com/slidesapp

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

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 25 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.

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
TOUR `footer.global-footer > div.global-footer-links > div.link-group > h4`

These are opportunities to improve keyboard navigation in your application.

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.description-cta-wrapper > div.description-testimonials > div.testimonial-avatars > img `div.description-cta-wrapper > div.description-testimonials > div.testimonial-avatars > 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.

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
Got it `body > div.cc-window > div.cc-compliance > a.cc-btn`

○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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`[accesskey]` values are unique

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

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