Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 4 REVIEW 3 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Favicon & Branding

8 icon(s) detected

REVIEW

8 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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Doodle

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Doodle ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name Doodle Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #fff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only

h2 This summer, everything changes.

1.77:1

#000000

#0C366F

needs 3.0:1 (large text)

24px · mid-page

h2 universal currency.

1.01:1

#000000

#000201

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Time OS

1.01:1

#000000

#000201

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The product is

1.01:1

#000000

#000201

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our Pact

1.01:1

#000000

#000201

needs 3.0:1 (large text)

24px · bottom of viewport

h2 This is Doodle

1.01:1

#000000

#000201

needs 3.0:1 (large text)

24px · bottom of viewport

h2 This is Time

1.01:1

#000000

#000201

needs 3.0:1 (large text)

24px · bottom of viewport

h3 We built modern work on the assumption t…

1.01:1

#000000

#000201

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Built in Switzerland

1.01:1

#000000

#000201

needs 3.0:1 (large text)

19px · bottom of viewport

title Free online meeting scheduling tool | Do…

1.00:1

#000000

#000001

needs 4.5:1 (normal text)

16px · top of page (header area)

a Log in

1.00:1

#000000

#020000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Sign up

1.00:1

#000000

#010000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Create a Doodle

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span Product

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Industries

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span Resources

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Pricing

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Time Institute

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a Log in

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 This summer, everyth…	1.77:1	3.0:1	#000000	#0C366F	Fail
h2 You ended yesterday	3.00:1	3.0:1	#000000	#33624F	Pass
h2 universal currency.	1.01:1	3.0:1	#000000	#000201	Fail
h2 Time OS	1.01:1	3.0:1	#000000	#000201	Fail
h2 The product is	1.01:1	3.0:1	#000000	#000201	Fail
h2 Our Pact	1.01:1	3.0:1	#000000	#000201	Fail
h2 This is Doodle	1.01:1	3.0:1	#000000	#000201	Fail
h2 This is Time	1.01:1	3.0:1	#000000	#000201	Fail
h3 We built modern work…	1.01:1	3.0:1	#000000	#000201	Fail
h3 Built in Switzerland	1.01:1	3.0:1	#000000	#000201	Fail
title Free online meeting …	1.00:1	4.5:1	#000000	#000001	Fail
a Log in	1.00:1	4.5:1	#000000	#020000	Fail
a Sign up	1.00:1	4.5:1	#000000	#010000	Fail
a Create a Doodle	1.00:1	4.5:1	#000000	#000000	Fail
span Product	1.00:1	4.5:1	#000000	#000000	Fail
span Industries	1.00:1	4.5:1	#000000	#000000	Fail
span Resources	1.00:1	4.5:1	#000000	#000000	Fail
a Pricing	1.00:1	4.5:1	#000000	#000000	Fail
a Time Institute	1.00:1	4.5:1	#000000	#000000	Fail
a Log in	1.00:1	4.5:1	#000000	#000000	Fail

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

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Heading Hierarchy

10 headings

PASS

10 headings

Single H1 present

H1 Meet your partner in Time
H2 This summer, everything changes.
H2 You ended yesterday exhausted.
H3 We built modern work on the assumption that time is a container.
H2 Time is the only universal currency.
H2 Doodle Time OS
H3 Built in Switzerlandtrusted everywhere
H2 The product is agency.
H2 Our Pact
H2 This is Doodle This is Time For All Time.

A+

Alt Text Quality

1 of 20 images have issues

PASS

1 of 20 images have issues

1 image(s) with generic alt text

2 decorative image(s) correctly marked

17 image(s) with good alt text

20 images 17 good alt text 2 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

29 links, 5 buttons — all OK

PASS

29 links, 5 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://www.facebook.com/DoodleAG; https://www.linkedin.com/company/doodle-ag/; https://www.youtube.com/@doodle1310; https://www.instagram.com/doodlescheduling/; https://x.com/doodletweet

24 link(s) with descriptive text

29 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/DoodleAG	Visit us on Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/doodle-…	Visit us on LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@doodle1310	Visit us on YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/doodlescheduli…	Visit us on Instagram	new tab	Add '(opens in new tab)' to text
https://x.com/doodletweet	Visit us on X	new tab	Add '(opens in new tab)' to text

29 links and buttons have descriptive text

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

https://www.facebook.com/DoodleAG; https://www.linkedin.com/company/doodle-ag/; https://www.youtube.com/@doodle1310; https://www.instagram.com/doodlescheduling/; https://x.com/doodletweet

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

Lighthouse Accessibility Audits

Score 94/100 — 1 failing, 22 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.

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
English `div.flex > div.flex > div.order-first > button#base-ui-_R_1feivb_`

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

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

●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

●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 have a discernible name

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

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

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

○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

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

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