Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

No 192x192 icon

A 192px icon is required for PWA installation.

PWA Install Criteria Not Installable

Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗

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

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

10 landmarks

REVIEW

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

1 of 4 <nav> elements are unlabeled

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

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

Alt Text Quality

2 of 65 images have issues

REVIEW

2 of 65 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image(s) with alt text over 125 characters

5 decorative image(s) correctly marked

55 image(s) with good alt text

65 images 55 good alt text 5 decorative 2 missing

Issue	Count
missing	2 image(s)
too long	3 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

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 Page Not Found | Sprout Social ✓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

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, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h1 Powerful tools for social media manageme…

1.02:1

#000000

#040404

needs 3.0:1 (large text)

32px · above the fold

h2 Own every social media touchpoint

1.02:1

#000000

#040404

needs 3.0:1 (large text)

24px · mid-page

h2 Trusted partnerships and integrations ac…

1.02:1

#000000

#040404

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Launch, run & scale creator campaigns

1.02:1

#000000

#040404

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Drive more impact with your social media…

1.02:1

#000000

#040404

needs 3.0:1 (large text)

24px · bottom of viewport

h3 See why 30,000+ brands scale their socia…

1.02:1

#000000

#040404

needs 3.0:1 (large text)

19px · bottom of viewport

button Solutions

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · top of page (header area)

a Pricing

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · top of page (header area)

button Resources

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

button Log in

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

span Schedule a demo

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

span Try for free

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

span Toggle mobile menu

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

span open

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

span Email address

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · above the fold

span Try free for 30 days

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

span Tour the product

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

p Plan & schedule content

1.02:1

#000000

#040404

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Powerful tools for s…	1.02:1	3.0:1	#000000	#040404	Fail
h2 Own every social med…	1.02:1	3.0:1	#000000	#040404	Fail
h2 Trusted partnerships…	1.02:1	3.0:1	#000000	#040404	Fail
h2 Launch, run & scale …	1.02:1	3.0:1	#000000	#040404	Fail
h2 Drive more impact wi…	1.02:1	3.0:1	#000000	#040404	Fail
h3 See why 30,000+ bran…	1.02:1	3.0:1	#000000	#040404	Fail
title Sprout Social: Socia…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Platform	7.65:1	4.5:1	#000000	#9C9C9C	Pass
button Solutions	1.02:1	4.5:1	#000000	#040404	Fail
a Pricing	1.02:1	4.5:1	#000000	#040404	Fail
button Resources	1.02:1	4.5:1	#000000	#040404	Fail
button Log in	1.02:1	4.5:1	#000000	#040404	Fail
span Schedule a demo	1.02:1	4.5:1	#000000	#040404	Fail
span Try for free	1.02:1	4.5:1	#000000	#040404	Fail
span Toggle mobile menu	1.02:1	4.5:1	#000000	#040404	Fail
span open	1.02:1	4.5:1	#000000	#040404	Fail
span Email address	1.02:1	4.5:1	#000000	#040404	Fail
span Try free for 30 days	1.02:1	4.5:1	#000000	#040404	Fail
span Tour the product	1.02:1	4.5:1	#000000	#040404	Fail
p Plan & schedule cont…	1.02:1	4.5:1	#000000	#040404	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+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 Powerful tools for social media management
H2 Own every social media touchpoint
H2 Trusted partnerships and integrations across leading platforms
H2 Launch, run & scale creator campaigns
H3 See why 30,000+ brands scale their social media with Sprout
H2 Drive more impact with your social media management tool, now.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	email	Email address	none

A+

Link & Button Quality

105 links, 31 buttons — all OK

PASS

105 links, 31 buttons — all OK

105 link(s) with descriptive text

105 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

136 links and buttons have descriptive text

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 26 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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Plan & schedule content Simplify workflows and collaboration to make sure your… `div.mx-auto > div > div.flex > div.dg`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant `body.overflow-y-visible-nm > q-focus-sentinel > div`
After AI assistant `body.overflow-y-visible-nm > q-focus-sentinel > div`
AI assistant, start `div#qualified-multimodal-host > div`
AI assistant, end `div#qualified-multimodal-host > div`

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.

○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

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

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

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

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

○Uses ARIA roles only on compatible elements

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

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