Skip to content
https://formstack.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
45
GRADE
F
FIX
8
REVIEW
1
PASS
4
INFO
0
Checks
13
4 PASS 1 REVIEW 8 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Warning::
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
BANNER header MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

D
Form Accessibility
Action
4 of 13 controls have issues
FIX
4 of 13 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="query" id="search-2">
Info::
9 control(s) properly labeled
13 controls
9 labeled
1 placeholder only
3 unlabeled
ControlTypeLabelMethod
#osano-cm-dialog-toggle--category_MARKETINGcheckboxnone
#osano-cm-dialog-toggle--category_PERSONALIZATIONcheckboxnone
#osano-cm-dialog-toggle--category_ANALYTICScheckboxnone
#firstname-1877169c-26b5-4239-8a75-018a635a1053textFirst name*for/id
#lastname-1877169c-26b5-4239-8a75-018a635a1053textLast name*for/id
#email-1877169c-26b5-4239-8a75-018a635a1053emailEmail*for/id
#company-1877169c-26b5-4239-8a75-018a635a1053textCompany name*for/id
#customer_survey_company_size__c-1877169c-26b5-4239-8a75-018a635a1053selectCompany Size*for/id
#what_can_we_help_you_with_today_-1877169c-26b5-4239-8a75-018a635a1053selectWhat can we help you with today?*for/id
#search-2search(Search)placeholder only
inputsubmit(none)none
#g-recaptcha-responsetextarea(none)none
inputsubmit(none)none

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

<input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit">

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="query" id="search-2">

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
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
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
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Not Found Custom Styling Navigation Homepage Link Search Form
A
Heading Hierarchy
20 headings
PASS
20 headings
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H3 Modernize the patient consent process with Formstack and Welnfuse
  • H1 Forms, Docs, and Sign.Designed to Work Together.
  • H1 Build Smarter Forms. Create Better Documents. Capture Every Signature. duplicate H1
  • H1 Simplify everything from Data Capture to Signature. duplicate H1
  • H1 Forms, Docs, and Sign. Designed to Work Together. duplicate H1
  • H1 Progress Shouldn’t Wait on Paperwork. duplicate H1
  • H2 Save hours with the world's easiest-to-use forms builder.
  • H3 Foster rapid innovation
  • H3 Seamless system integration
  • H3 Maintain clean data
  • H3 We go beyond forms
  • H2 Get up and running in minutes
  • H3 Start a free 14-day trial
  • H3 See Formstack in action
  • H3 Talk with our Sales Team
  • H3 Formstack Academy
  • H2 Integrate Formstack with your business tools
  • H2 Partner with Formstack
  • H2 Take control of your data with Formstack
  • H2 Talk to Sales

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Alt Text Quality
1 of 107 images have issues
PASS
1 of 107 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 image(s) with alt text over 125 characters
Info::
75 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
107 images 30 good alt text 75 decorative 1 missing
IssueCount
missing1 image(s)
too long1 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

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 Forms, Docs, a…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Build Smarter Forms.…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Capture Every Signat…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Simplify everything …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Forms, Docs, and Sig…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Designed to Work Tog…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Progress Shouldn’t21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Wait on Paperwork.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Save hours with the …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get up and running i…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Integrate Formstack …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Partner with Formsta…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 data with Formstack21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Talk to Sales21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Modernize the patien…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Foster rapid innovat…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Seamless system inte…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Maintain clean data21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We go beyond forms21.00:13.0:1
#000000
#FFFFFF
Pass
h3 14-day trial21.00:13.0:1
#000000
#FFFFFF
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
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 26 passed
PASS
91

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
AI assistant body > q-focus-sentinel > div
After AI assistant body > 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.

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
Forms div.footer-right > div.footer-column > a.footer-link > div
Documents div.footer-right > div.footer-column > a.footer-link > div
Sign div.footer-right > div.footer-column > a.footer-link > div
Formstack Suite div.footer-right > div.footer-column > a.footer-link > div
Forms for Salesforce div.footer-right > div.footer-column > a.footer-link > div
Docs for Salesforce div.footer-right > div.footer-column > a.footer-link > div
Integrations div.footer-right > div.footer-column > a.footer-link > div
Pricing div.footer-right > div.footer-column > a.footer-link > div
Resource Center div.footer-right > div.footer-column > a.footer-link > div
Templates div.footer-right > div.footer-column > a.footer-link > div
Blog div.footer-right > div.footer-column > a.footer-link > div
Site Map div.footer-right > div.footer-column > a.footer-link > div
Help Center div.footer-right > div.footer-column > a.footer-link > div
Find a Partner div.footer-right > div.footer-column > a.footer-link > div
Release Notes div.footer-right > div.footer-column > a.footer-link > div
Developers and API div.footer-right > div.footer-column > a.footer-link > div
Documents API div.footer-right > div.footer-column > a.footer-link > div
System Status div.footer-right > div.footer-column > a.footer-link > div
Report Abuse div.footer-right > div.footer-column > a.footer-link > div
About Us div.footer-right > div.footer-column > a.footer-link > div
Partner Program div.footer-right > div.footer-column > a.footer-link > div
Careers div.footer-right > div.footer-column > a.footer-link > div
Cookie Preferences div.footer-right > div.footer-column > div.w-embed > a.footer-link
Security div.footer-right > div.footer-column > a.footer-link > div
Legal Notices div.footer-bottom > div.footer-bottom-container > a.footer-link > div
CCPA div.footer-bottom-container > div.footer-bottom-right > a.footer-link > div
Legal div.footer-bottom-container > div.footer-bottom-right > a.footer-link > div.footer-link
Trust Center div.footer-bottom-container > div.footer-bottom-right > a.footer-link > div

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div > iframe.chilipiper-frame body > div > iframe.chilipiper-frame

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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
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
`[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
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.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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.
Identical links have the same purpose.
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