Skip to content
https://photoshelter.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Alt Text Quality
Action
11 of 68 images have issues
FIX
11 of 68 images have issues
Critical::
11 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
5 image(s) with alt text over 125 characters
Info::
18 decorative image(s) correctly marked
Info::
34 image(s) with good alt text
68 images 34 good alt text 18 decorative 11 missing
IssueCount
missing11 image(s)
too long5 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

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
12 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 12 <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
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | PhotoShelter ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 26 passed
REVIEW
88

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

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
Iris assistant body.home > q-focus-sentinel > div
After Iris assistant body.home > q-focus-sentinel > div
Iris assistant, start div#qualified-multimodal-host > div
Iris 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.

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
Book a Demo div.hero-media__content-wrapper > div.hero-media__content > div.hero-media__buttons > a.button
Take a Tour div.hero-media__content-wrapper > div.hero-media__content > div.hero-media__buttons > a.button
See All Integrations div.acf-innerblocks-container > section#block_5b2787c11e17112d57fd55ba66dcbc6f > div.content-integrations__buttons > a.button
Ready to do more with DAM? div.md:px-8 > div.callout-color-block__content-wrapper > div.max-w-[800px] > h2.mb-0
Book a Demo div.callout-color-block__content-wrapper > div.max-w-[800px] > div.flex > a.button
Take a Tour div.callout-color-block__content-wrapper > div.max-w-[800px] > div.flex > a.button

These are opportunities to improve the legibility of your content.

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.hero-media__content > span.hero-media__bg-wrapper > picture > img.block div.hero-media__content > span.hero-media__bg-wrapper > picture > img.block

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
●`[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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●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
○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
○`<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.
○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.
A+
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
12 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Header Top Navigation" MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
76 headings
PASS
76 headings
Info::
Single H1 present
  • H2 PhotoShelter for Brands
  • H3 Products
  • H3 Digital Asset Management
  • H3 Social Content Distribution
  • H3 UGC Management
  • H3 Features
  • H3 Artificial Intelligence (AI)
  • H3 Real-Time Workflow
  • H3 Analytics
  • H3 Collaboration
  • H3 Video Management
  • H3 Sharing
  • H3 Integrations
  • H3 Social Analytics
  • H3 PhotoShelter for Photographers
  • H3 How to evaluate and select the right DAM
  • H2 Industries
  • H3 Arts, Media, & Entertainment
  • H3 Healthcare
  • H3 Consumer Goods
  • H3 Manufacturing
  • H3 Education
  • H3 Nonprofit
  • H3 Food & Beverage
  • H3 Sports
  • H3 Government
  • H3 Travel & Hospitality
  • H2 Roles
  • H3 CMO
  • H3 Brand & Communications
  • H3 Creative
  • H3 Marketing
  • H3 Social Media
  • H2 Business Size
  • H3 Small & Medium Businesses
  • H3 Enterprise Businesses
  • H3 Individual Photographers
  • H2 Discover
  • H3 Blog
  • H3 Artificial Intelligence (AI)
  • H3 Brand Growth
  • H3 Brand Protection
  • H3 DAM 101
  • H3 PhotoShelter News
  • H3 Product Updates
  • H3 Real-Time Workflow
  • H3 Social Media & Content Distribution
  • H3 Team Productivity
  • H2 Learn
  • H3 Customer Stories
  • H3 Guides & White Papers
  • H3 Webinars & Events
  • H3 DAM Strategy Hub
  • H3 Social Media Strategy Hub
  • H2 Connect
  • H3 Partner Program
  • H3 Community
  • H3 Customer Support
  • H3 Help Center
  • H1 Power Your Workflow with Smarter Digital Asset Management
  • H2 Trusted by thousands of the fastest-growing brands
  • H2 The #1 DAM for marketers and creatives
  • H3 500k+
  • H3 6.7B+
  • H3 ~2,000
  • H2 Grow your brand and get more done
  • H2 AI-powered DAM
  • H2 User-generated content
  • H2 Real-time content distribution
  • H2 Analytics
  • H2 Optimize your workflow with PhotoShelter integrations
  • H2 Why PhotoShelter
  • H3 Team Productivity
  • H3 Brand Growth
  • H3 Brand Protection
  • H2 Ready to do more with DAM?
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Power Your Workflow …19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Industries19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Roles19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Business Size19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Learn19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Connect19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Trusted by thousands…19.91:13.0:1
#000000
#F8F9F9
Pass
h2 The #1 DAM for marke…19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Grow your brand and …19.91:13.0:1
#000000
#F8F9F9
Pass
h2 AI-powered DAM19.91:13.0:1
#000000
#F8F9F9
Pass
h2 User-generated conte…19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Real-time content di…19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Analytics19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Optimize your workfl…19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Why PhotoShelter19.91:13.0:1
#000000
#F8F9F9
Pass
h2 Ready to do more wit…19.91:13.0:1
#000000
#F8F9F9
Pass
h3 Products20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Features20.65:13.0:1
#000000
#FDFDFD
Pass
h3 PhotoShelter for Pho…19.91:13.0:1
#000000
#F8F9F9
Pass
h3 How to evaluate and …19.91:13.0:1
#000000
#F8F9F9
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback