Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

Link & Button Quality

Action

16 issue(s) across 43 links and 4 buttons

FIX

16 issue(s) across 43 links and 4 buttons

14 link(s) with generic text

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

Got: https://yourvisionrealized.sketchup.trimble.com/ ("Learn more"); https://extensions.sketchup.com ("Learn more"); https://3dwarehouse.sketchup.com ("Learn more"); /en/products/scan-essentials ("Learn more"); /en/products/trimble-connect ("Learn more"); https://marketplace.trimble.com ("Learn more"); https://developer.sketchup.com ("Learn more"); /en/plans-and-pricing/sketchup-pro ("Learn more"); /en/plans-and-pricing/sketchup-pro ("Learn more"); https://help.sketchup.com/en/contact-support/technical-question/form ("here") (+4 more)

7 link(s) open in new tab without warning

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

Got: https://www.sketchup.com/blog/en-US/tags/customer-stories; https://learn.trimble.com/learn/public/catalog/view/913; https://www.youtube.com/SketchUp; https://forums.sketchup.com/; https://sketchup.trimble.com/en/resellers; https://accounts.trimble.com/; https://help.sketchup.com/en

2 button(s) with no accessible text

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

Got: button.custom-slick-arrow (#365 on page); button.custom-slick-arrow (#382 on page)

22 link(s) with descriptive text

43 links

0 empty

14 generic text

7 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://yourvisionrealized.sketchup.trim…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Home page
https://www.sketchup.com/blog/en-US/tags…	Customer Stories	new tab	Add '(opens in new tab)' to text
https://extensions.sketchup.com	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Extensions.Sketchup.Com
https://3dwarehouse.sketchup.com	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: 3dwarehouse.Sketchup.Com
/en/products/scan-essentials	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Scan Essentials
/en/products/trimble-connect	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Trimble Connect
https://marketplace.trimble.com	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Marketplace.Trimble.Com
https://developer.sketchup.com	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Developer.Sketchup.Com
/en/plans-and-pricing/sketchup-pro	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Sketchup Pro
/en/plans-and-pricing/sketchup-pro	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Sketchup Pro
https://learn.trimble.com/learn/public/c…	SketchUp Campus	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/SketchUp	SketchUp YouTube channel	new tab	Add '(opens in new tab)' to text
https://forums.sketchup.com/	community forum	new tab	Add '(opens in new tab)' to text
https://help.sketchup.com/en/contact-sup…	here	generic text	Replace with descriptive text
Before: here Suggested: Form
https://sketchup.trimble.com/en/reseller…	SketchUp Partners network	new tab	Add '(opens in new tab)' to text
https://accounts.trimble.com/	Trimble Admin Console	new tab	Add '(opens in new tab)' to text
https://help.sketchup.com/en	Get Support	new tab	Add '(opens in new tab)' to text
	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: Home page
	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: Home page
	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: Home page
	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: Home page
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

24 links and buttons have descriptive text

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

https://yourvisionrealized.sketchup.trimble.com/ ("Learn more"); https://extensions.sketchup.com ("Learn more"); https://3dwarehouse.sketchup.com ("Learn more"); /en/products/scan-essentials ("Learn more"); /en/products/trimble-connect ("Learn more"); https://marketplace.trimble.com ("Learn more"); https://developer.sketchup.com ("Learn more"); /en/plans-and-pricing/sketchup-pro ("Learn more"); /en/plans-and-pricing/sketchup-pro ("Learn more"); https://help.sketchup.com/en/contact-support/technical-question/form ("here") (+4 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.

https://www.sketchup.com/blog/en-US/tags/customer-stories; https://learn.trimble.com/learn/public/catalog/view/913; https://www.youtube.com/SketchUp; https://forums.sketchup.com/; https://sketchup.trimble.com/en/resellers; https://accounts.trimble.com/; https://help.sketchup.com/en

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.custom-slick-arrow (#365 on page); button.custom-slick-arrow (#382 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

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

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

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

9 icon(s) detected

REVIEW

9 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: Trimble Inc

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

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

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

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 1 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Bring your vision to…	3.04:1	3.0:1	#000000	#68555A	Pass
h2 Revolutionize the wa…	4.60:1	3.0:1	#000000	#906E63	Pass
h2 Empowering the peopl…	9.54:1	3.0:1	#000000	#B5ACB6	Pass
h2 See what customers a…	11.11:1	3.0:1	#000000	#FBAD26	Pass
h2 Connected tools. Sea…	11.11:1	3.0:1	#000000	#FBAD26	Pass
h2 Explore the Pro subs…	11.11:1	3.0:1	#000000	#FBAD26	Pass
h2 Find the SketchUp th…	11.11:1	3.0:1	#000000	#FBAD26	Pass
h2 Tools trusted by ind…	11.11:1	3.0:1	#000000	#FBAD26	Pass
h2 Professionals prefer…	11.11:1	3.0:1	#000000	#FBAD26	Pass
h2 You have questions? …	11.11:1	3.0:1	#000000	#FBAD26	Pass
h2 Still have questions…	11.11:1	3.0:1	#000000	#FBAD26	Pass
h3 Landscape Architectu…	7.43:1	3.0:1	#000000	#C29143	Pass
h3 Urban Planning	11.11:1	3.0:1	#000000	#FBAD26	Pass
h3 Architecture	11.11:1	3.0:1	#000000	#FBAD26	Pass
h3 Construction	11.11:1	3.0:1	#000000	#FBAD26	Pass
h3 Interior Design	11.11:1	3.0:1	#000000	#FBAD26	Pass
h3 Landscape Architectu…	11.11:1	3.0:1	#000000	#FBAD26	Pass
h3 Urban Planning	11.11:1	3.0:1	#000000	#FBAD26	Pass
h3 Architecture	11.11:1	3.0:1	#000000	#FBAD26	Pass
h3 Construction	11.11:1	3.0:1	#000000	#FBAD26	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 85/100 — 4 failing, 25 passed

REVIEW

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
div.t2-cart-flyout > div.t2-cart-flyout__panel > div.t2-cart-flyout__header > button.t2-cart-flyout__header__close-btn `div.t2-cart-flyout > div.t2-cart-flyout__panel > div.t2-cart-flyout__header > button.t2-cart-flyout__header__close-btn`

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.

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
EXPLORE THE ECOSYSTEM `div.t2-lo-cards__content > div.t2-lo-cards__primary-content > div.t2-header-area > div.t2-lo-cards__eyebrow`
MONTHLY `div.t2-lo-price-cards__primary-content > div.t2-lo-price-cards-toggle > div.t2-lo-price-card__pill > div#monthly`

These are opportunities to improve the legibility of your content.

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
t2u-chevron-right `div.t2-slider-carousel-wrap > div.slick-slider > div.slick-dots > ul.custom-slick-dots`
ABOUT US Careers Contact Us Privacy Policy ISO/IEC 27001:2013 `section.t2-footer__sector-footer > section.t2-footer__section-wrapper > nav.t2-footer__section > ul.t2-footer__footer-menu`
DEVELOPERS Developer Center SketchUp Ruby API SketchUp SDK Extensions Developer… `section.t2-footer__sector-footer > section.t2-footer__section-wrapper > nav.t2-footer__section > ul.t2-footer__footer-menu`
LEARN Forum Contact Us Blog Campus YouTube `section.t2-footer__sector-footer > section.t2-footer__section-wrapper > nav.t2-footer__section > ul.t2-footer__footer-menu`
EXPLORE Trimble Trimble Construction Trimble Field Technology Visiting Professi… `section.t2-footer__sector-footer > section.t2-footer__section-wrapper > nav.t2-footer__section > ul.t2-footer__footer-menu`
CONNECT WITH US `section.t2-footer__sector-footer > section.t2-footer__section-wrapper > nav.t2-footer__section-social > ul.t2-footer__footer-menu`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li `div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li`
div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li.slick-active `div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li.slick-active`
div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li `div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li`
div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li `div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li`
div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li `div.slick-dots > ul.custom-slick-dots > div.custom-dots-wrapper > li`
Careers `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Contact Us `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Privacy Policy `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
ISO/IEC 27001:2013 `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Developer Center `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
SketchUp Ruby API `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
SketchUp SDK `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Extensions `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Developer Forum `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Forum `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Contact Us `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Blog `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Campus `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
YouTube `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Trimble `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Trimble Construction `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Trimble Field Technology `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Visiting Professionals `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Non-Profit Organizations `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Project Spectrum `nav.t2-footer__section > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__items > li.t2-footer__footer-menu__item`
Visit us on Facebook `nav.t2-footer__section-social > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__social-wrapper > li.t2-footer__footer-menu__social-item`
Visit us on Twitter `nav.t2-footer__section-social > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__social-wrapper > li.t2-footer__footer-menu__social-item`
Visit us on LinkedIn `nav.t2-footer__section-social > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__social-wrapper > li.t2-footer__footer-menu__social-item`
Visit us on TikTok `nav.t2-footer__section-social > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__social-wrapper > li.t2-footer__footer-menu__social-item`
Visit us on Instagram `nav.t2-footer__section-social > ul.t2-footer__footer-menu > div.t2-footer__footer-menu__social-wrapper > li.t2-footer__footer-menu__social-item`

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

●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

●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

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

A+

Landmark Structure

3 landmarks

PASS

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

47 headings, 1 skip(s)

PASS

47 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H6 (missing H3)

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

H1 Bring your vision to life
H2 Revolutionize the way you create
H2 Empowering the people building our world
H3 Landscape Architecture
H3 Urban Planning
H3 Architecture
H3 Construction
H3 Interior Design
H3 Landscape Architecture
H3 Urban Planning
H3 Architecture
H3 Construction
H3 Interior Design
H3 Landscape Architecture
H3 Urban Planning
H2 See what customers are saying
H3 Creativity
H3 Sustainability
H3 Collaboration
H3 Accuracy
H2 Connected tools. Seamless workflow.
H3 Extension Warehouse
H3 3D Warehouse
H3 Scan Essentials
H3 Trimble Connect
H3 Trimble Marketplace
H3 Developer Center
H2 Explore the Pro subscription
H2 Find the SketchUp that best fits your workflow
H2 Tools trusted by industry leaders across the world
H2 Professionals prefer SketchUp
H2 You have questions? We have answers.
H3 What is SketchUp?
H3 What makes SketchUp different?
H3 Where can I find tutorials and learning resources?
H3 Do you offer customer support?
H3 How do I manage my account?
H2 Still have questions? Visit the help center.
H6 Attention skipped
H6 Cart Updated
H6 Attention
H6 Cart Updated
H6 Cart Updated
H6 Cart Updated
H6 Cart Updated
H6 Cart Updated
H6 Cart Updated

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

Alt Text Quality

All 36 images OK

PASS

All 36 images OK

15 image(s) with alt text over 125 characters

21 image(s) with good alt text

36 images 21 good alt text

Issue	Count
too long	15 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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