Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 2 REVIEW 8 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Form Accessibility

Action

21 of 33 controls have issues

FIX

21 of 33 controls have issues

20 control(s) without accessible label

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

Got: <input type="text" name="firstname">; <input type="text" name="lastname">; <input type="text" name="emailAddress">; <input type="text" name="phone">; <textarea name="message">; <input type="text" name="firstname">; <input type="text" name="lastname">; <input type="text" name="emailAddress">; <input type="text" name="phone">; <textarea name="message"> (+10 more)

1 control(s) rely on placeholder only

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

Got: <input type="text" name="q" id="tags">

12 control(s) properly labeled

33 controls

12 labeled

1 placeholder only

20 unlabeled

Control	Type	Label	Method
#chck1	checkbox	Tour	for/id
#chck2	checkbox	Products	for/id
#chck3	checkbox	Resources	for/id
#chck4	checkbox	Pricing	for/id
#chck5	checkbox	Features Comparison	for/id
#chck6	checkbox	Solutions	for/id
#chck7	checkbox	Company	for/id
#vendor-search-handler	text	Vendor Search	for/id
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#tags	text	(Site Search)	placeholder only
emailAddress	text	(none)	none
phone	text	(none)	none
message	textarea	(none)	none
firstname	text	(none)	none
lastname	text	(none)	none
emailAddress	text	(none)	none
phone	text	(none)	none
message	textarea	(none)	none
firstname	text	(none)	none
lastname	text	(none)	none
emailAddress	text	(none)	none
phone	text	(none)	none
message	textarea	(none)	none
firstname	text	(none)	none
lastname	text	(none)	none
emailAddress	text	(none)	none
phone	text	(none)	none
message	textarea	(none)	none
firstname	text	(none)	none
lastname	text	(none)	none

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

<input type="text" name="firstname">; <input type="text" name="lastname">; <input type="text" name="emailAddress">; <input type="text" name="phone">; <textarea name="message">; <input type="text" name="firstname">; <input type="text" name="lastname">; <input type="text" name="emailAddress">; <input type="text" name="phone">; <textarea name="message"> (+10 more)

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.

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

Link & Button Quality

Action

8 issue(s) across 170 links and 25 buttons

FIX

8 issue(s) across 170 links and 25 buttons

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /research-suite/?sourceref=home ("Learn more"); /cx/?sourceref=home ("Learn more"); /workforce/?sourceref=home ("Learn more")

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: //www.facebook.com/questionpro; //twitter.com/questionpro; //linkedin.com/company/questionpro; //www.youtube.com/user/QuestionPro; /chat/; https://cookiepedia.co.uk/giving-consent-to-cookies; https://www.cookiepro.com/products/cookie-consent/

5 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button (#1101 on page); button (#1113 on page); button (#1125 on page); button (#1137 on page); button.ot-host-box (#1211 on page)

160 link(s) with descriptive text

170 links

0 empty

3 generic text

7 new tab

5 empty buttons

Element	Text	Issue	Suggested Fix
/research-suite/?sourceref=home	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: ?Sourceref=Home
/cx/?sourceref=home	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: ?Sourceref=Home
/workforce/?sourceref=home	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: ?Sourceref=Home
/features/questionpro-ai/?sourceRef=home	Build better studies instantly…	img no alt	Add alt attribute to the image
//www.facebook.com/questionpro	facebook-link	new tab	Add '(opens in new tab)' to text
//twitter.com/questionpro	twitter-link	new tab	Add '(opens in new tab)' to text
//linkedin.com/company/questionpro	linkedin-link	new tab	Add '(opens in new tab)' to text
//www.youtube.com/user/QuestionPro	youtube-link	new tab	Add '(opens in new tab)' to text
/chat/	Live Chat	new tab	Add '(opens in new tab)' to text
https://cookiepedia.co.uk/giving-consent…	More information, Opens in a n…	new tab	Add '(opens in new tab)' to text
https://www.cookiepro.com/products/cooki…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

180 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/research-suite/?sourceref=home ("Learn more"); /cx/?sourceref=home ("Learn more"); /workforce/?sourceref=home ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

//www.facebook.com/questionpro; //twitter.com/questionpro; //linkedin.com/company/questionpro; //www.youtube.com/user/QuestionPro; /chat/; https://cookiepedia.co.uk/giving-consent-to-cookies; https://www.cookiepro.com/products/cookie-consent/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button (#1101 on page); button (#1113 on page); button (#1125 on page); button (#1137 on page); button.ot-host-box (#1211 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Heading Hierarchy

30 headings, 1 skip(s)

REVIEW

30 headings, 1 skip(s)

Multiple H1 headings (11 found)

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

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 AI-Powered insights,backed by real experts.
H1 All your insights, one platform duplicate H1
H1 Surveys & Research duplicate H1
H1 Market research tools for professionals duplicate H1
H1 Customer Experience duplicate H1
H1 Launch and manage a VoC program duplicate H1
H1 Employee Experience duplicate H1
H1 Enhance teams with employee surveys duplicate H1
H2 Trusted by Market Research, CX, and HR teams at leading brands
H2 AI that workswhere you need it
H3 Validate research in minutes, without risking customer privacy.
H3 Video responses. Instant sentiment. No manual analysis.
H3 Your entire report, summarized in one click.
H3 Go from idea to full survey in under 60 seconds.
H3 AI-generated poll questions that boost participation.
H1 Real people. Real answers. Always. duplicate H1
H1 Proven at scale duplicate H1
H1 Stop waiting weeks for insights duplicate H1
H4 Awards & certificates skipped
H5 The Experience Journal
H3 Privacy Preference Center
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Performance Cookies
H4 Functional Cookies
H4 Targeting Cookies
H3 Back Button Back
H3 33Across
H4 host description
H4 View Cookies

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Survey Software - Online Survey Software - Customer Satisfaction Surveys - Employee Survey - Web Survey Software ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

A+

Alt Text Quality

All 36 images OK

PASS

All 36 images OK

2 decorative image(s) correctly marked

34 image(s) with good alt text

36 images 34 good alt text 2 decorative

All images have appropriate alt text.

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)

Element	Ratio	Required	FG	BG	Result
h1 AI-Powered insights,	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 backed by real exper…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 All your insights, o…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Surveys & Research	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Market research tool…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Customer Experience	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Launch and manage a …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Employee Experience	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Enhance teams with e…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Real people. Real an…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Proven at scale	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Stop waiting weeks f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trusted by Market Re…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 AI that works	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 where you need it	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Validate research in…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Video responses. Ins…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Your entire report, …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Go from idea to full…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 AI-generated poll qu…	21.00:1	3.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.

Lighthouse Accessibility Audits

Score 94/100 — 3 failing, 25 passed

PASS

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 FREE `body > div.header-wrapper > div.content-wrapper > a.free-ac-btn`
BOOK A DEMO `section.hero-bg > div.hero-container26 > div.two-btn-26 > a.main-btn-26`
Market research tools for professionals `div.newcontainerm-2 > div.service-products-main-2 > div.containerblocks-2 > h1.h1-products`
PRICING `div.service-products-main-2 > div.containerblocks-2 > div.cta-two-products-2 > a.main-btn-26`
LEARN MORE `div.containerblocks-2 > div.cta-two-products-2 > div.p-learn-2 > a.link`
Launch and manage a VoC program `div.newcontainerm-2 > div.service-products-main-2 > div.containerblocks-2 > h1.h1-products`
LEARN MORE `div.service-products-main-2 > div.containerblocks-2 > a.cta-two-products-2 > div.p-learn-2`
Enhance teams with employee surveys `div.newcontainerm-2 > div.service-products-main-2 > div.containerblocks-2 > h1.h1-products`
LEARN MORE `div.service-products-main-2 > div.containerblocks-2 > a.cta-two-products-2 > div.p-learn-2`
div.white-container26 > section.ai-content > div.hero-container26 > a.main-btn-26 `div.white-container26 > section.ai-content > div.hero-container26 > a.main-btn-26`
div.light-blue-ai > div.text-lightblue > div.two-btn-26 > a.main-btn-26 `div.light-blue-ai > div.text-lightblue > div.two-btn-26 > a.main-btn-26`
TRY FOR FREE `section.hero-bg > div.hero-container26 > div.two-btn-26 > a.main-btn-26`

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
Awards & certificates `div.content-wrapper > div.ft-award-section > div.ft-left-award > h4.ft-sec-title`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.no-js `html.no-js`

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]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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.

●`[accesskey]` values are unique

●`button`, `link`, and `menuitem` elements have accessible names

●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

●`<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

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○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

○Buttons have an accessible name

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○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.

○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.