Skip to content
https://smartsheet.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 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: #ffffff
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
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="search-standalone-submit--297318590">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="search_api_fulltext" id="search-query-297318590">
Info::
3 control(s) properly labeled
5 controls
3 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#edit-lang-dropdown-selectselectSelect your languagefor/id
#edit-lang-dropdown-selectselectSelect your languagefor/id
#edit-lang-dropdown-select--2selectSelect your languagefor/id
#search-query-297318590search(What can we help you find?)placeholder only
#search-standalone-submit--297318590submit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" id="search-standalone-submit--297318590">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="search_api_fulltext" id="search-query-297318590">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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 Present
✓ Multiple Sizes Present
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, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h3 Your Privacy
2.83:1
#000000
on
#184BC3
needs 3.0:1 (large text)
19px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Intelligent Work Man…17.13:13.0:1
#000000
#E6E8ED
Pass
h2 Smarter solutions.17.13:13.0:1
#000000
#E6E8ED
Pass
h2 Greater velocity of …17.13:13.0:1
#000000
#E6E8ED
Pass
h2 Smarter solutions. G…17.13:13.0:1
#000000
#E6E8ED
Pass
h2 Sync your tools, kee…17.13:13.0:1
#000000
#E6E8ED
Pass
h2 Sync your tools, kee…17.13:13.0:1
#000000
#E6E8ED
Pass
h2 Real stories, real i…17.13:13.0:1
#000000
#E6E8ED
Pass
h2 Real stories, real i…17.13:13.0:1
#000000
#E6E8ED
Pass
h2 Security that brings…17.13:13.0:1
#000000
#E6E8ED
Pass
h2 Security that brings…17.13:13.0:1
#000000
#E6E8ED
Pass
h2 News and views17.13:13.0:1
#000000
#E6E8ED
Pass
h3 Your Privacy2.83:13.0:1
#000000
#184BC3
Fail
h3 Projects and portfol…17.13:13.0:1
#000000
#E6E8ED
Pass
h3 Digital and IT17.13:13.0:1
#000000
#E6E8ED
Pass
h3 Operations17.13:13.0:1
#000000
#E6E8ED
Pass
h3 Client delivery17.13:13.0:1
#000000
#E6E8ED
Pass
h3 2025 Gartner® Magic…17.13:13.0:1
#000000
#E6E8ED
Pass
h3 5 Signs your team is…17.13:13.0:1
#000000
#E6E8ED
Pass
h3 Puma17.13:13.0:1
#000000
#E6E8ED
Pass
h3 The 2026 project and…17.13:13.0:1
#000000
#E6E8ED
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 29 passed
REVIEW
80

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
AI AI-powered intelligence Make work management your team’s superpower with S… article > div > div#p-id-777241 > div.slides

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
To Do g > g > g#12764 > g#12740
In Progress g > g > g#12764 > g#12736
Project Progress g > g > g#13388 > g#13517
Project Milestone Progression g > g > g#13388 > g#13504
Budget Consumption g > g#13388 > g > g#13530
Spend by department g > g > g#13388 > g#13543
YTD Totals g > g > g#13388 > g#13556
Remaining g > g#13388 > g > g#13630
YTD Actual g > g#13388 > g > g#13631
$0 g > g > g#13388 > g#13579
$1K g > g > g#13388 > g#13580
$2K g > g > g#13388 > g#13581
$3K g > g > g#13388 > g#13582
$4K g > g > g#13388 > g#13583
Sales g > g > g#13388 > g#13569
Marketing g > g > g#13388 > g#13570
Legal g > g > g#13388 > g#13571
Budgeted g > g#13388 > g > g#13596
$7,900,000 g > g#13388 > g > g#13597
$2,393,942 g > g > g#13388 > g#13598
Actual g > g > g#13388 > g#13600
Remaining g > g > g#13388 > g#13601
$5,506,058 g > g > g#13388 > g#13599
Draft Creation g > g > g#13388 > g#13675
Draft Review g > g > g#13388 > g#13676
Brief and Scope g > g > g#13388 > g#13677
Kickoff g > g > g#13388 > g#13678
Build svg > g > g#12513 > g#12502
Creating your workspace svg > g > g#12513 > g#12530
Build a project plan for a cross-functional initiative. Include tasks, dates, … svg > g > g#12513 > g#12496
What would you like to build? svg > g > g#12513 > g#12501

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.slide-holder > div.arrow-aligner > div.arrow-scroller > button.slide-nav div.slide-holder > div.arrow-aligner > div.arrow-scroller > button.slide-nav
div.slide-holder > div.arrow-aligner > div.arrow-scroller > button.slide-nav div.slide-holder > div.arrow-aligner > div.arrow-scroller > button.slide-nav

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.container > div.static-footer > div.footer-legal > a.privacy-choices div.container > div.static-footer > div.footer-legal > a.privacy-choices

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.

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
ANALYST RECOGNITION div.teaser-content > div.teaser-card-static > div.content-container > p.teaser-eyebrow
AI PULSE div.teaser-content > div.teaser-card-static > div.content-container > p.teaser-eyebrow

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
©2026. All Rights Reserved Smartsheet Inc. div.container > div.static-footer > div.footer-legal > a
Machine Translation Disclaimer div.container > div.static-footer > div.footer-legal > a
Cookie Preferences div.container > div.static-footer > div.footer-legal > a
div.container > div.static-footer > div.footer-legal > a.privacy-choices div.container > div.static-footer > div.footer-legal > a.privacy-choices

These items highlight common accessibility best practices.

○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]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●Select elements have associated label elements.
●`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
●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.
●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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[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
○`<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
○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.
○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.
○Identical links have the same purpose.
○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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A+
Heading Hierarchy
20 headings
PASS
20 headings
Info::
Single H1 present
  • H3 Your Privacy
  • H1 Intelligent Work Management with AI at its core
  • H2 Smarter solutions. Greater velocity of work.
  • H2 Smarter solutions. Greater velocity of work.
  • H3 AI
  • H3 Projects and portfolios
  • H3 Digital and IT
  • H3 Operations
  • H3 Client delivery
  • H2 Sync your tools, keep teams connected
  • H2 Sync your tools, keep teams connected
  • H2 Real stories, real impact
  • H2 Real stories, real impact
  • H2 Security that brings you peace of mind
  • H2 Security that brings you peace of mind
  • H2 News and views
  • H3 2025 Gartner® Magic Quadrant™ Leader
  • H3 5 Signs your team is ready to crush it with AI
  • H3 Puma
  • H3 The 2026 project and portfolio management priorities report
A+
Alt Text Quality
All 150 images OK
PASS
All 150 images OK
Info::
43 decorative image(s) correctly marked
Info::
107 image(s) with good alt text
150 images 107 good alt text 43 decorative
All images have appropriate alt text.
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error 404 | Smartsheet ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback