Skip to content
https://shutterfly.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title Photo Books, Cards, Prints, Wall Art, Gifts, Wedding | Shutterfly ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Skip links" SEARCH MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

B
Heading Hierarchy
37 headings
REVIEW
37 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Today's Deals
  • H2 More Deals
  • H2 Shop by category
  • H2 Announcements
  • H2 Party Invitations
  • H2 Thank You Cards
  • H2 What's new, right now.
  • H2 Create something custom—right from your camera roll.
  • H2 Relive cozy, sunny, and snowy adventures.
  • H2 Beautifully made, built to last.
  • H2 Bring your happy place home.
  • H2 Hold onto great memories.
  • H2 Elevate your space with custom wall art.
  • H2 Canvas Prints
  • H2 Metal Prints
  • H2 Framed Prints
  • H2 Save the Dates
  • H2 Wedding Invitations
  • H2 Wedding Photo Books
  • H2 These free, helpful services make creating even more fun.
  • H2 Free Address Book Service
  • H2 Free Address Printing
  • H2 Free 24-Hour Photo Book Designer Service
  • H2 1-Hour Print Pickup
  • H2 Send Life Updates with Custom Greeting Cards
  • H2 Create Unique Personalized Gifts for Loved Ones
  • H2 Custom Home Decor and Wall Art to Decorate Your Space
  • H2 Make Photo Books & Order Prints for Cherished Memories
  • H2 Experience the Shutterfly Difference
  • H3 Create your way
  • H3 100% happiness guaranteed
  • H3 Quality you can see
  • H3 (empty)
  • H2 HELP
  • H2 RESOURCES
  • H2 CORPORATE
  • H2 PRODUCTS & SERVICES

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Today's Deals3.05:13.0:1
#000000
#585B58
Pass
h2 More Deals3.05:13.0:1
#000000
#585B58
Pass
h2 Shop by category3.05:13.0:1
#000000
#585B58
Pass
h2 Announcements3.05:13.0:1
#000000
#585B58
Pass
h2 Party Invitations3.05:13.0:1
#000000
#585B58
Pass
h2 Thank You Cards3.05:13.0:1
#000000
#585B58
Pass
h2 What's new, right no…3.05:13.0:1
#000000
#585B58
Pass
h2 Create something cus…3.05:13.0:1
#000000
#585B58
Pass
h2 Relive cozy, sunny, …3.05:13.0:1
#000000
#585B58
Pass
h2 Beautifully made, bu…3.05:13.0:1
#000000
#585B58
Pass
h2 Bring your happy pla…3.05:13.0:1
#000000
#585B58
Pass
h2 Hold onto great memo…3.05:13.0:1
#000000
#585B58
Pass
h2 Elevate your space w…3.05:13.0:1
#000000
#585B58
Pass
h2 Canvas Prints3.05:13.0:1
#000000
#585B58
Pass
h2 Metal Prints3.05:13.0:1
#000000
#585B58
Pass
h2 Framed Prints3.05:13.0:1
#000000
#585B58
Pass
h2 Save the Dates3.05:13.0:1
#000000
#585B58
Pass
h2 Wedding Invitations3.05:13.0:1
#000000
#585B58
Pass
h2 Wedding Photo Books3.05:13.0:1
#000000
#585B58
Pass
h2 These free, helpful …3.05:13.0:1
#000000
#585B58
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
Alt Text Quality
All 99 images OK
PASS
All 99 images OK
Info::
8 image(s) with alt text over 125 characters
Info::
7 decorative image(s) correctly marked
Info::
84 image(s) with good alt text
99 images 84 good alt text 7 decorative
IssueCount
too long8 image(s)
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
#autocomplete-inputtextautocomplete-inputaria-label
#autocomplete-inputtextautocomplete-inputaria-label
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 31 passed
PASS
94

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
DEALS div.isNonCMSPage > button.sfly-lib-deals-button > span.sfly-lib-z-10 > span.deals-text

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.sfly-lib-no-underline > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link div > div.sfly-lib-no-underline > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link
div.sfly-lib-grid > div.sfly-lib-flex > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link div.sfly-lib-grid > div.sfly-lib-flex > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link
div.sfly-lib-grid > div.sfly-lib-flex > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link div.sfly-lib-grid > div.sfly-lib-flex > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link
div.sfly-lib-grid > div.sfly-lib-flex > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link div.sfly-lib-grid > div.sfly-lib-flex > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link
div.sfly-lib-grid > div.sfly-lib-flex > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link div.sfly-lib-grid > div.sfly-lib-flex > div.sfly-lib-flex > a.sfly-lib-anchor-dummy-link

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.

○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]`s are contained by their required parent element
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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.
●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
●ARIA IDs are unique
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○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>`.
○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.

Send Feedback