Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://typeform.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://typeform.com/manifest.json

Manifest contains invalid JSON.

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 ✗

Link & Button Quality

Action

3 issue(s) across 144 links and 17 buttons

REVIEW

3 issue(s) across 144 links and 17 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /templates; https://www.typeform.com/whats-new; /blog

10 link(s) open in new tab without warning

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

Got: https://community.typeform.com/; https://www.typeform.com/agencies; https://www.facebook.com/typeform/; https://www.twitter.com/typeform/; https://www.instagram.com/typeform/; https://www.youtube.com/channel/UC2nRv6J0FsJVePJTLhUDKgg/; https://www.linkedin.com/company/typeform-com/; https://admin.typeform.com/to/dwk6gt/; https://admin.typeform.com/to/dwk6gt/; https://www.onetrust.com/products/cookie-consent/

131 link(s) with descriptive text

144 links

3 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/templates	(empty)	empty	Add link text or aria-label
https://www.typeform.com/whats-new	(empty)	empty	Add link text or aria-label
https://community.typeform.com/	CommunityShare and interact	new tab	Add '(opens in new tab)' to text
/blog	(empty)	empty	Add link text or aria-label
https://www.typeform.com/agencies	Agency directory	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/typeform/	Open Typeform's Facebook accou…	new tab	Add '(opens in new tab)' to text
https://www.twitter.com/typeform/	Open Typeform's Twitter/X acco…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/typeform/	Open Typeform's Instagram acco…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UC2nRv6J…	Open Typeform's YouTube accoun…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/typefor…	Open Typeform's Linkedin accou…	new tab	Add '(opens in new tab)' to text
https://admin.typeform.com/to/dwk6gt/	, opens in a new tab	new tab	Add '(opens in new tab)' to text
https://admin.typeform.com/to/dwk6gt/	, opens in a new tab	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text

148 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/templates; https://www.typeform.com/whats-new; /blog

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://community.typeform.com/; https://www.typeform.com/agencies; https://www.facebook.com/typeform/; https://www.twitter.com/typeform/; https://www.instagram.com/typeform/; https://www.youtube.com/channel/UC2nRv6J0FsJVePJTLhUDKgg/; https://www.linkedin.com/company/typeform-com/; https://admin.typeform.com/to/dwk6gt/; https://admin.typeform.com/to/dwk6gt/; https://www.onetrust.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

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 Typeform Icon ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 Platform

1.36:1

#000000

#2A222B

needs 3.0:1 (large text)

19px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Build forms at the d…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trusted by 95% of th…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The form is only the…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get 3.5x more data w…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trigger action that …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Connect with hundred…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Why Typeform?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cookie consent	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cookie Preference Ce…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cookie Preference Ce…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Platform	1.36:1	3.0:1	#000000	#2A222B	Fail
h3 Tools	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 TEMPLATES	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 What's new	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 TEAMS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 USE CASES	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Plans	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 SUPPORT	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 COMPANY	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 BLOG	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.

Landmark Structure

23 landmarks

PASS

23 landmarks

<main> landmark present

19 <nav> landmark(s) found

1 of 19 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

39 headings

PASS

39 headings

Single H1 present

1 hidden heading(s) (aria-hidden)

H3 Platform
H3 Tools
H3 TEMPLATES
H3 What's new
H3 TEAMS
H3 USE CASES
H3 Plans
H3 SUPPORT
H3 COMPANY
H3 BLOG
H1 Build forms at the drop of a prompt
H2 Trusted by 95% of the Fortune 500
H2 The form is only the beginning
H2 Get 3.5x more data with a form expert
H2 Trigger action that brings in customers
H2 Connect with hundreds of your business-critical tools
H2 Why Typeform?
H3 96%
H3 95%
H3 87%
H3 PRODUCT
H3 Templates
H3 Integrations
H3 Resources
H3 Get to know us
H2 Cookie consent
H2 Cookie Preference Centre
H2 Cookie Preference Centre hidden
H3 Your Privacy
H3 Strictly Necessary Cookies
H3 Analytics Cookies
H3 Advertising and profiling cookies
H3 Functional Cookies
H4 Your Privacy
H4 Strictly Necessary Cookies
H4 Analytics Cookies
H4 Advertising and profiling cookies
H4 Functional Cookies
H3 Cookie List

A+

Alt Text Quality

All 171 images OK

PASS

All 171 images OK

154 decorative image(s) correctly marked

17 image(s) with good alt text

171 images 17 good alt text 154 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 8 controls labeled

PASS

All 8 controls labeled

8 control(s) properly labeled

8 controls

8 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-2	checkbox	Analytics Cookies	for/id
#ot-group-id-4	checkbox	Advertising and profiling cookies	for/id
#ot-group-id-3	checkbox	Functional Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#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
#chkbox-id	checkbox	checkbox label	for/id

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 30 passed

PASS

100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
cookie policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

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

●Background and foreground colors have a sufficient contrast ratio

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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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

○ARIA IDs are unique

○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

○Form elements have associated labels

○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

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

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