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 5 REVIEW 3 FIX

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) 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.

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

Link & Button Quality

30 links, 9 buttons — all OK

REVIEW

30 links, 9 buttons — all OK

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://apps.chrome/getit/acc638ca-7aff-405c-8648-d57276d74d1a"]

6 link(s) open in new tab without warning

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

Got: /help/faq/browser-platform-and-hardware-requirements; https://health.autodesk.com/; /terms; https://www.autodesk.com/company/legal-notices-trademarks; /help/faq; https://www.tinkercad.com/privacy

23 link(s) with descriptive text

30 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/help/faq/browser-platform-and-hardware-…	Learn more about supported dev…	new tab	Add '(opens in new tab)' to text
https://health.autodesk.com/	Server Status	new tab	Add '(opens in new tab)' to text
https://apps.chrome/getit/acc638ca-7aff-…	Add to chromebook	img no alt	Add alt attribute to the image
/terms	Terms of Service	new tab	Add '(opens in new tab)' to text
https://www.autodesk.com/company/legal-n…	Legal & Trademarks	new tab	Add '(opens in new tab)' to text
/help/faq	FAQ	new tab	Add '(opens in new tab)' to text
https://www.tinkercad.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text

32 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://apps.chrome/getit/acc638ca-7aff-405c-8648-d57276d74d1a"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

/help/faq/browser-platform-and-hardware-requirements; https://health.autodesk.com/; /terms; https://www.autodesk.com/company/legal-notices-trademarks; /help/faq; https://www.tinkercad.com/privacy

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

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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'>.

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA 3 pass AA only

div Tinkercad works best on desktops, laptop…

3.66:1

#000000

#1F5BE3

needs 4.5:1 (normal text)

16px · top of page (header area)

a Proceed anyway

3.72:1

#000000

#1E5CE5

needs 4.5:1 (normal text)

16px · top of page (header area)

a Back to website

3.67:1

#000000

#185BE5

needs 4.5:1 (normal text)

16px · above the fold

a Learn more about supported devices.

3.60:1

#000000

#1759E5

needs 4.5:1 (normal text)

16px · above the fold

p At Autodesk, we empower innovators every…

3.32:1

#000000

#1053DF

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Start Tinkering

3.21:1

#000000

#0A51DB

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Join Class

2.93:1

#000000

#0449D6

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p Tinkercad is a free web app for 3D desig…

3.08:1

#000000

#014DDA

needs 4.5:1 (normal text)

16px · above the fold

div Tinker

3.46:1

#000000

#0557E1

needs 4.5:1 (normal text)

16px · above the fold

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Looks like you’re …	4.19:1	3.0:1	#000000	#186CD9	Pass
h2 Tomorrow’s innovat…	3.45:1	3.0:1	#000000	#1356E1	Pass
title Tinkercad	4.59:1	4.5:1	#000000	#1477D1	Pass
div Tinkercad works best…	3.66:1	4.5:1	#000000	#1F5BE3	Fail
a Proceed anyway	3.72:1	4.5:1	#000000	#1E5CE5	Fail
a Back to website	3.67:1	4.5:1	#000000	#185BE5	Fail
a Learn more about sup…	3.60:1	4.5:1	#000000	#1759E5	Fail
p At Autodesk, we empo…	3.32:1	4.5:1	#000000	#1053DF	Fail
a Start Tinkering	3.21:1	4.5:1	#000000	#0A51DB	Fail
a Join Class	2.93:1	4.5:1	#000000	#0449D6	Fail
p Tinkercad is a free …	3.08:1	4.5:1	#000000	#014DDA	Fail
div Tinker	3.46:1	4.5:1	#000000	#0557E1	Fail
a 3D Design	7.00:1	4.5:1	#000000	#6794EA	Pass
a Circuits	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Codeblocks	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a iPad App	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Sim Lab	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Teachers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Classrooms	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Projects	21.00:1	4.5: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.

Heading Hierarchy

4 headings, 1 skip(s)

PASS

4 headings, 1 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.

H1 Looks like you’re using a small screen
H2 Tomorrow’s innovators are made today
H4 Send us feedback skipped
H4 Message sent

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

1 decorative image(s) correctly marked

2 image(s) with good alt text

3 images 2 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	Select language	aria-label
#descriptionField	textarea	Message	for/id

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Tinkercad

192x192 icon present

512x512 icon present

Display mode: minimal-ui

PWA Install Criteria ✓ Installable

Name Tinkercad ✓192×192 icon ✓512×512 icon ✓Start URL /?source=pwa ✓Display Mode minimal-ui ✓

Name Tinkercad Display Mode minimal-ui Background Color #74bde6 Icons 2 icon(s)

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 26 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.

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
Free for everyone `div.home > div.home-bullets > div.home-bullets-item > h3`
Start designing in 3D `div.home-products > div.home-products-item > div.home-products-item-text > h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
`footer#footer > div.footer-kidsafe > div#ksp-seals > a`

Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more about alt text for `object` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-kidsafe > div#ksp-seals > a > object `div.footer-kidsafe > div#ksp-seals > a > object`
div.footer-kidsafe > div#ksp-seals > a > object `div.footer-kidsafe > div#ksp-seals > a > object`

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]` 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.

●Select elements have associated label elements.

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

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

●Touch targets have sufficient size and spacing.

●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

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

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

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

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

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

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