Skip to content
https://smore.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
3
REVIEW
3
PASS
7
INFO
0
Checks
13
7 PASS 3 REVIEW 3 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #273c6d
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 ModePartial Dark Mode
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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 Page not found - Smore Custom Styling Navigation Homepage Link Search Form
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name 192×192 icon 512×512 icon Start URL Display Mode standalone
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA
h1 A newsletter builder made for
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
32px · bottom of viewport
h2 school communications with Smore
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to create a newsletter people will…
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why do
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 love Smore?
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Create
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Translate
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Brand
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Collaborate
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Share
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Measure
1.95:1
#000000
on
#273C6D
needs 3.0:1 (large text)
19px · bottom of viewport
a Solutions for Schools
1.95:1
#000000
on
#273C6D
needs 4.5:1 (normal text)
16px · above the fold
a Solutions for Districts
1.95:1
#000000
on
#273C6D
needs 4.5:1 (normal text)
16px · above the fold
a Features
1.95:1
#000000
on
#273C6D
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 A newsletter builder…1.95:13.0:1
#000000
#273C6D
Fail
h2 school communication…1.95:13.0:1
#000000
#273C6D
Fail
h2 Ready to create a ne…1.95:13.0:1
#000000
#273C6D
Fail
h2 Why do1.95:13.0:1
#000000
#273C6D
Fail
h2 love Smore?1.95:13.0:1
#000000
#273C6D
Fail
h3 Create1.95:13.0:1
#000000
#273C6D
Fail
h3 Translate1.95:13.0:1
#000000
#273C6D
Fail
h3 Brand1.95:13.0:1
#000000
#273C6D
Fail
h3 Collaborate1.95:13.0:1
#000000
#273C6D
Fail
h3 Share1.95:13.0:1
#000000
#273C6D
Fail
h3 Measure1.95:13.0:1
#000000
#273C6D
Fail
title Smore Newsletter Bui…15.12:14.5:1
#000000
#FFD587
Pass
a Skip to content15.12:14.5:1
#000000
#FFD587
Pass
span Did you know? Smore …15.12:14.5:1
#000000
#FFD587
Pass
a Find out more.21.00:14.5:1
#000000
#FFFFFF
Pass
a Who We’re For21.00:14.5:1
#000000
#FFFFFF
Pass
a Solutions for Educat…9.46:14.5:1
#000000
#A7AEC0
Pass
a Solutions for School…1.95:14.5:1
#000000
#273C6D
Fail
a Solutions for Distri…1.95:14.5:1
#000000
#273C6D
Fail
a Features1.95:14.5:1
#000000
#273C6D
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
3 landmarks
PASS
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO footer
A
Heading Hierarchy
12 headings, 1 skip(s)
PASS
12 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 A newsletter builder made for schools & districtsSmore users see a 28% improvement in family engagement rates on average!
  • H2 Simplifyschool communications with Smore
  • H3 Create
  • H3 Translate
  • H3 Brand
  • H3 Collaborate
  • H3 Share
  • H3 Measure
  • H2 Ready to create a newsletter people will actually read?
  • H2 Why do educators love Smore?
  • H4 Get started today! skipped
  • H4 Stay Updated

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

A
Alt Text Quality
43 of 218 images have issues
PASS
43 of 218 images have issues
Warning::
43 image(s) with generic alt text
Info::
124 decorative image(s) correctly marked
Info::
51 image(s) with good alt text
218 images 51 good alt text 124 decorative 43 generic
IssueCount
generic43 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Favicon & Branding
12 icon(s) detected
PASS
12 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Present
Manifest Icons Present
Multiple Sizes Present
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 26 passed
PASS
95

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
Sign Up for Free div.hero-inner > div.hero-content > div.hero-btn > a.button
1 million educators in 20,000+ div.hero-inner > div.hero-bottom-text > p > span
Get started in minutes div.section-head > div.section-head-text > p > a
Sign Up div.footer-cta > div.footer-cta-inner > div.footer-cta-btn > a.button

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
Get started today! div.footer-cta > div.footer-cta-inner > div.footer-cta-title > h4.heading-2

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
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
`[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
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.
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
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[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
`<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
`<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.
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