Skip to content
https://slideserve.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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
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
No dark mode signals
FIX
No dark mode signals
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 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
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::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
39 headings, 3 skip(s)
REVIEW
39 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H5 (missing H4)
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.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Upload and Share Presentations Documents E-Books Videos I
  • H2 All in one marketing tool for your digital content
  • H3 Top on SlideServe
  • H5 2026 Grammy Awards: Fashion, Moments & Winners skipped
  • H5 Greenland: An Island of Ice
  • H5 Horses Purified by Fire 2026
  • H3 Trending Contents
  • H5 2026 Grammy Awards: Fashion, Moments & Winners skipped
  • H5 Frozen Niagara Falls Draws Tourists
  • H5 Nationwide anti-ICE Protests
  • H5 2026 Celebrities at Paris Couture
  • H5 Minneapolis Streets Respond to Another Deadly ICE Encounter
  • H5 Winter Storm Hits Several Major Cities Across the US
  • H5 Greenland: An Island of Ice
  • H5 Deadly Wildfires Rage in Southern Chile
  • H3 Improve your Content Marketing with SlideServe
  • H3 Explore Featured Topics
  • H3 Featured Contents
  • H5 America in 2024 skipped
  • H5 Best photos of the moon in 2024
  • H5 Stunning images of the northern lights
  • H5 Notting Hill Carnival 2024
  • H5 The worst hurricanes in American history
  • H5 South Fork Fire forces evacuations in New Mexico
  • H5 British classic car lovers 'Race The Wave'
  • H5 Word whizzes at the Scripps Spelling Bee
  • H5 Freddie Mercury, Paul Newman items up for auction
  • H5 Strawberry Moon dazzles in night sky
  • H5 Space tapestry
  • H5 Horses purified by fire
  • H5 The life and death of Gaddafi
  • H5 Turkey's Camel wrestling festival
  • H5 Mobile World Congress
  • H5 Thailand's magic tattoo festival
  • H5 60 years of NASA missions
  • H5 'The Lionesses': Kenya's elite all-female ranger unit
  • H5 The surreal Northern Lights
  • H5 Myanmar monk offers temple sanctuary for threatened snakes
  • H3 Top SlideServe Influencers

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

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 404 error. Page Not Found. ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h2 All in one marketing tool for your digit…
1.27:1
#000000
on
#09212E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Top on SlideServe
1.27:1
#000000
on
#09212E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Trending Contents
1.27:1
#000000
on
#09212E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Improve your
1.27:1
#000000
on
#09212E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 with SlideServe
1.27:1
#000000
on
#09212E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Explore Featured Topics
1.27:1
#000000
on
#09212E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Featured Contents
1.27:1
#000000
on
#09212E
needs 3.0:1 (large text)
19px · bottom of viewport
title Upload and Share Documents Presentations…
1.27:1
#000000
on
#09212E
needs 4.5:1 (normal text)
16px · top of page (header area)
span Browse
1.27:1
#000000
on
#09212E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Recent Presentations
1.00:1
#000000
on
#010001
needs 4.5:1 (normal text)
16px · top of page (header area)
a Recent Articles
1.01:1
#000000
on
#010102
needs 4.5:1 (normal text)
16px · top of page (header area)
a Content Topics
1.01:1
#000000
on
#010101
needs 4.5:1 (normal text)
16px · above the fold
a Updated Contents
1.17:1
#000000
on
#171717
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Featured Contents
1.32:1
#000000
on
#212222
needs 4.5:1 (normal text)
16px · above the fold
a PowerPoint Templates
1.39:1
#000000
on
#262626
needs 4.5:1 (normal text)
16px · above the fold
span Create
1.05:1
#000000
on
#060809
needs 4.5:1 (normal text)
16px · above the fold
a Presentation
1.20:1
#000000
on
#191A1A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Article
1.09:1
#000000
on
#0D0F11
needs 4.5:1 (normal text)
16px · above the fold
a Survey
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Upload and Share11.58:13.0:1
#000000
#F4B62F
Pass
h2 All in one marketing…1.27:13.0:1
#000000
#09212E
Fail
h3 Top on SlideServe1.27:13.0:1
#000000
#09212E
Fail
h3 Trending Contents1.27:13.0:1
#000000
#09212E
Fail
h3 Improve your1.27:13.0:1
#000000
#09212E
Fail
h3 with SlideServe1.27:13.0:1
#000000
#09212E
Fail
h3 Explore Featured Top…1.27:13.0:1
#000000
#09212E
Fail
h3 Featured Contents1.27:13.0:1
#000000
#09212E
Fail
title Upload and Share Doc…1.27:14.5:1
#000000
#09212E
Fail
span Browse1.27:14.5:1
#000000
#09212E
Fail
a Recent Presentations1.00:14.5:1
#000000
#010001
Fail
a Recent Articles1.01:14.5:1
#000000
#010102
Fail
a Content Topics1.01:14.5:1
#000000
#010101
Fail
a Updated Contents1.17:14.5:1
#000000
#171717
Fail
a Featured Contents1.32:14.5:1
#000000
#212222
Fail
a PowerPoint Templates1.39:14.5:1
#000000
#262626
Fail
span Create1.05:14.5:1
#000000
#060809
Fail
a Presentation1.20:14.5:1
#000000
#191A1A
Fail
a Article1.09:14.5:1
#000000
#0D0F11
Fail
a Survey1.13:14.5:1
#000000
#131313
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.

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 navigation" 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+
Alt Text Quality
All 53 images OK
PASS
All 53 images OK
Info::
9 decorative image(s) correctly marked
Info::
44 image(s) with good alt text
53 images 44 good alt text 9 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtextSearcharia-label
qsearchSearcharia-label
A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 26 passed
PASS
98

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
2026 Grammy Awards: Fashion, Moments & Winners div.card > a > div.card-body > h5.card-title
2026 Grammy Awards: Fashion, Moments & Winners div.card > a > div.card-body > h5.card-title
America in 2024 div.card > a > div.card-body > h5.card-title

These are opportunities to improve keyboard navigation in your application.

○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
●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.
●ARIA attributes are used as specified for the element's role
●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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[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
○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.
○`<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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback