Browse & Analyze

Browse recent website audits and performance trends

Explore technology stacks detected across the web

Side-by-side technology comparisons and market share

Curated technology stacks and the sites that use them

Editorial deep-dives on the state of web performance

Browse and download favicons from analyzed websites

Learn

Common questions about BeaverCheck scores and checks

How we calculate scores across 100+ checks

The story behind BeaverCheck and the team

Practical guides to fix common web performance issues

Migration Guides

Step-by-step guides for moving between web technologies

Definitions for performance, SEO, and web platform terms

Contrast Checker

Check WCAG color contrast ratios between any two colors

Inspect HTTP response headers for any URL

Analyze SSL/TLS certificate details and chain

Look up DNS records for any domain

Redirect Checker

Trace the full redirect chain for any URL

Real-user INP and Core Web Vitals from Google's Chrome UX Report.

RESTful API for programmatic website audits

Embed an auto-updating health score badge on your site

https://toggl.com

Accessibility

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

SCORE

55

GRADE

D

FIX

5

REVIEW

5

PASS

3

INFO

0

Checks

13

3 PASS 5 REVIEW 5 FIX

D

Heading Hierarchy

Action

33 headings, 4 skip(s)

FIX

33 headings, 4 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H3 → H5 (missing H4)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

H1 Where teams and time tracking data meet
H2 The time tracker that achieves 100% user adoption in your team
H4 Calendar View skipped
H4 Track time your way
H4 Automated time tracking
H4 100+ integrations
H4 Calendar View
H4 Track time your way
H4 Automated time tracking
H4 100+ integrations
H3 Want to get team buy-in without the fuss? Let Toggl Track do the talking.
H2 Boost team productivity, profitability, and balance workloads
H3 Increase efficiency and revenue
H4 20% increase in profitability
H3 Ready to see what your data can really do?
H5 For small teams with low budgets skipped
H5 For larger and enterprise teams
H2 Enterprise-grade solutions to scale time tracking with ease
H4 Time tracking without the micromanagement skipped
H4 Custom reporting dashboards and beyond
H4 Fast help and even faster onboarding
H4 Secure and reliable with ISO 27001 certification and SOC 2 Type I compliance
H4 Voted Best Estimated ROI and Grid Leader for Enterprise solutions
H3 See how fast your investment in time tracking can pay off
H2 The time tracker that brings clarity to high-performing teams
H3 For larger and enterprise teams
H2 It's time for less busy work – more profitable work.
H5 Product skipped
H5 Use Cases
H5 Toggl Track vs.
H5 Features
H5 Help
H5 Resources

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

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

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

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

D

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.

D

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.

D

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 ✗

F

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

Search

Skip Link

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.

C

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

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

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

C

Form Accessibility

Action

4 of 9 controls have issues

REVIEW

4 of 9 controls have issues

4 control(s) without accessible label

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

Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

5 control(s) properly labeled

9 controls

5 labeled

0 placeholder only

4 unlabeled

Control	Type	Label	Method
#CybotCookiebotDialogBodyLevelButtonNecessary	checkbox	Necessary	for/id
#CybotCookiebotDialogBodyLevelButtonPreferences	checkbox	Preferences	for/id
#CybotCookiebotDialogBodyLevelButtonStatistics	checkbox	Statistics	for/id
#CybotCookiebotDialogBodyLevelButtonMarketing	checkbox	Marketing	for/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformation	checkbox	Do not sell or share my personal information	for/id
#CybotCookiebotDialogBodyLevelButtonPreferencesInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonStatisticsInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonMarketingInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonNecessaryInline	checkbox	(none)	none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

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

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | Toggl ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

C

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 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 Missing

✓ Multiple Sizes Present

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h1 Where

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

32px · bottom of viewport

h1 and time tracking

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

32px · bottom of viewport

h1 meet

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

32px · bottom of viewport

h2 The time tracker that achieves

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

24px · bottom of viewport

h2 user adoption in your team

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Boost team productivity, profitability,

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

24px · bottom of viewport

h2 balance workloads

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Enterprise-grade solutions to scale time…

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The time tracker that brings

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

24px · bottom of viewport

h2 to high-performing teams

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

24px · bottom of viewport

h2 It's

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

24px · bottom of viewport

h2 for less busy work – more profitable w…

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Want to get team buy-in without the fuss…

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Increase efficiency and revenue

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ready to see what your data can really d…

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

19px · bottom of viewport

h3 See how fast your investment in time tra…

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

19px · bottom of viewport

h3 For larger and enterprise teams

2.08:1

#000000

on

#4D3B57

needs 3.0:1 (large text)

19px · bottom of viewport

a Details

1.20:1

#000000

on

#271031

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Where	2.08:1	3.0:1	#000000	#4D3B57	Fail
h1 and time tracking	2.08:1	3.0:1	#000000	#4D3B57	Fail
h1 meet	2.08:1	3.0:1	#000000	#4D3B57	Fail
h2 The time tracker tha…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h2 user adoption in you…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h2 Boost team productiv…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h2 balance workloads	2.08:1	3.0:1	#000000	#4D3B57	Fail
h2 Enterprise-grade sol…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h2 The time tracker tha…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h2 to high-performing t…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h2 It's	2.08:1	3.0:1	#000000	#4D3B57	Fail
h2 for less busy work �…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h3 Want to get team buy…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h3 Increase efficiency …	2.08:1	3.0:1	#000000	#4D3B57	Fail
h3 Ready to see what yo…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h3 See how fast your in…	2.08:1	3.0:1	#000000	#4D3B57	Fail
h3 For larger and enter…	2.08:1	3.0:1	#000000	#4D3B57	Fail
title Toggl Track: Time Tr…	16.40:1	4.5:1	#000000	#F6DFD2	Pass
a Consent	14.86:1	4.5:1	#000000	#EAD5C9	Pass
a Details	1.20:1	4.5:1	#000000	#271031	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.

A+

Alt Text Quality

1 of 84 images have issues

PASS

1 of 84 images have issues

1 image(s) with generic alt text

1 image(s) with alt text over 125 characters

19 decorative image(s) correctly marked

63 image(s) with good alt text

84 images 63 good alt text 19 decorative 1 generic

Issue	Count
generic	1 image(s)
too long	1 image(s)

A

Link & Button Quality

174 links, 35 buttons — all OK

PASS

174 links, 35 buttons — all OK

48 link(s) open in new tab without warning

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

Got: https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.cloudflare.com/privacypolicy/; https://www.cookiebot.com/goto/privacy-policy/; https://business.safety.google/privacy/; https://www.linkedin.com/legal/privacy-policy; https://www.rudderstack.com/cookie-policy/; https://foundation.wikimedia.org/wiki/Privacy_policy; https://www.cookiebot.com/goto/privacy-policy/; https://legal.hubspot.com/privacy-policy; https://www.linkedin.com/legal/privacy-policy (+38 more)

126 link(s) with descriptive text

174 links

0 empty

0 generic text

48 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cookiebot.com/en/what-is-beh…	Cookiebot by Usercentrics - op…	new tab	Add '(opens in new tab)' to text
https://www.cloudflare.com/privacypolicy…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com/goto/privacy-p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/legal/privacy-p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.rudderstack.com/cookie-polic…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://foundation.wikimedia.org/wiki/Pr…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com/goto/privacy-p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://legal.hubspot.com/privacy-policy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/legal/privacy-p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.apple.com/legal/privacy/en-w…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://legal.hubspot.com/privacy-policy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.rudderstack.com/cookie-polic…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://vimeo.com/privacy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/policy.php/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://support.giphy.com/hc/en-us/artic…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://legal.hubspot.com/privacy-policy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://privacy.microsoft.com/en-US/priv…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.redditinc.com/policies/priva…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.rudderstack.com/cookie-polic…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://twitter.com/en/privacy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.redditinc.com/policies/priva…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://accounts.toggl.com	accounts.toggl.com	new tab	Add '(opens in new tab)' to text
https://apply.hire.toggl.com	apply.hire.toggl.com	new tab	Add '(opens in new tab)' to text
https://apply-next.hire.toggl.com	apply-next.hire.toggl.com	new tab	Add '(opens in new tab)' to text
https://candidate.hire.toggl.com	candidate.hire.toggl.com	new tab	Add '(opens in new tab)' to text
https://community.toggl.com	community.toggl.com	new tab	Add '(opens in new tab)' to text
https://expert.hire.toggl.com	expert.hire.toggl.com	new tab	Add '(opens in new tab)' to text
https://focus.toggl.com	focus.toggl.com	new tab	Add '(opens in new tab)' to text
https://learn.toggl.com	learn.toggl.com	new tab	Add '(opens in new tab)' to text
https://work.toggl.com	work.toggl.com	new tab	Add '(opens in new tab)' to text
https://track.toggl.com	track.toggl.com	new tab	Add '(opens in new tab)' to text
https://toggl.com	toggl.com	new tab	Add '(opens in new tab)' to text
https://plan.toggl.com	plan.toggl.com	new tab	Add '(opens in new tab)' to text
https://hire.toggl.com	hire.toggl.com	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com	Cookiebot	new tab	Add '(opens in new tab)' to text
https://developers.track.toggl.com/	API	new tab	Add '(opens in new tab)' to text
https://support.toggl.com/en/	Support & Knowledge Base	new tab	Add '(opens in new tab)' to text
https://community.toggl.com/	Toggl Community	new tab	Add '(opens in new tab)' to text
https://toggl.com/blog/	Blog	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/toggl/	Visit Toggl's LinkedIn profile	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/toggltrack	Visit Toggl's Instagram profil…	new tab	Add '(opens in new tab)' to text
https://x.com/toggl	Visit Toggl's X (Twitter) prof…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/toggl	Visit Toggl's YouTube profile	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Toggl/	Visit Toggl's Facebook profile	new tab	Add '(opens in new tab)' to text
https://github.com/toggl	Visit Toggl's GitHub profile	new tab	Add '(opens in new tab)' to text

161 links and buttons have descriptive text

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

https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.cloudflare.com/privacypolicy/; https://www.cookiebot.com/goto/privacy-policy/; https://business.safety.google/privacy/; https://www.linkedin.com/legal/privacy-policy; https://www.rudderstack.com/cookie-policy/; https://foundation.wikimedia.org/wiki/Privacy_policy; https://www.cookiebot.com/goto/privacy-policy/; https://legal.hubspot.com/privacy-policy; https://www.linkedin.com/legal/privacy-policy (+38 more)

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

A

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 25 passed

PASS

92

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
Privacy Policies `div#CybotCookiebotDialogBodyContentText > p > a > span`
Show details `div#CybotCookiebotDialogBody > div.CybotCookiebotDialogBodyBottomWrapper > div#CybotCookiebotDialogBodyEdgeMoreDetails > a#CybotCookiebotDialogBodyEdgeMoreDetailsLink`

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
Calendar View `div.css-zoazy8-Wrapper > div.css-lnhwn5-Mobile > div.css-jeyonm-TrackEaseOfUseTabMobile > h4.css-dq1bfg-H4`
For small teams with low budgets `div.css-yimyu5-DoubleCTAContainer > div.css-490dub-CTABoxWrapper > div.css-131lgiy-CTABox > h5.css-3c6rwi-H5`
Time tracking without the micromanagement `div.css-vn9xtc-WhyTrackGrid > div.css-1dzocis-WhyTrackBox > div > h4.css-dq1bfg-H4`
Product `div.css-j3goz1-ProductOnly > div.css-2l6ewq-Lists > div.css-nx96wp-RootList > h5.css-10o1c5y-Title`

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Legal Center Status `section.css-1fefyqh-GlobalFooter > div.css-132zuqc-SizeWrapper > div.css-1s8ykbz-LegalBit > ul.css-dp1dc1-GlobalLinks`

These are opportunities to improve the experience of reading tabular or list data using 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

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

●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

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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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