Skip to content
https://blender.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Landmark Structure
Action
3 landmarks
FIX
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Warning::
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
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO footer

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

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

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Theme color only
FIX
Theme color only
Info::
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: #ed8f31
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
Info::
2 navigation landmark(s) detected
Info::
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 2 <nav> element(s)
Back to Top
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.
C
Alt Text Quality
Action
6 of 28 images have issues
REVIEW
6 of 28 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
3 decorative image(s) correctly marked
Info::
19 image(s) with good alt text
28 images 19 good alt text 3 decorative 6 missing
IssueCount
missing6 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found — Blender ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA 3 pass AA only
h2 Free and Open Source
1.35:1
#46EBC2
on
#F2F2F3
needs 3.0:1 (large text)
24px · bottom of viewport
a Features
3.47:1
#000000
on
#456394
needs 4.5:1 (normal text)
16px · top of page (header area)
a Download
2.05:1
#000000
on
#274265
needs 4.5:1 (normal text)
16px · top of page (header area)
a Support
1.52:1
#000000
on
#192E46
needs 4.5:1 (normal text)
16px · above the fold
a Get Involved
2.12:1
#000000
on
#294561
needs 4.5:1 (normal text)
16px · above the fold
a About
2.80:1
#000000
on
#29587F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Jobs
2.23:1
#000000
on
#224870
needs 4.5:1 (normal text)
16px · above the fold
a Store
2.18:1
#000000
on
#21476C
needs 4.5:1 (normal text)
16px · above the fold
a Donate
2.04:1
#000000
on
#184368
needs 4.5:1 (normal text)
16px · above the fold
a Features
1.51:1
#000000
on
#1A2C4C
needs 4.5:1 (normal text)
16px · above the fold
a Download
2.17:1
#000000
on
#4D4242
needs 4.5:1 (normal text)
16px · above the fold
a Support
1.98:1
#000000
on
#314050
needs 4.5:1 (normal text)
16px · above the fold
a Get Involved
1.70:1
#000000
on
#133754
needs 4.5:1 (normal text)
16px · mid-page
a About
1.19:1
#000000
on
#061A2C
needs 4.5:1 (normal text)
16px · mid-page

1 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)
ElementRatioRequiredFGBGResult
h1 Blender 5.13.30:13.0:1
#000000
#6B5D4E
Pass
h2 Free and Open Source1.35:13.0:1
#46EBC2
#F2F2F3
Fail
h2 Part of the industry4.32:13.0:1
#0066FF
#F2F2F3
Pass
h2 It’s about people.5.09:13.0:1
#9300FF
#F2F2F3
Pass
title Blender - The Free a…21.00:14.5:1
#000000
#FFFFFF
Pass
span Toggle navigation21.00:14.5:1
#000000
#FFFFFF
Pass
a Features3.47:14.5:1
#000000
#456394
Fail
a Download2.05:14.5:1
#000000
#274265
Fail
a Support1.52:14.5:1
#000000
#192E46
Fail
a Get Involved2.12:14.5:1
#000000
#294561
Fail
a About2.80:14.5:1
#000000
#29587F
Fail
a Jobs2.23:14.5:1
#000000
#224870
Fail
a Store2.18:14.5:1
#000000
#21476C
Fail
a Donate2.04:14.5:1
#000000
#184368
Fail
a Features1.51:14.5:1
#000000
#1A2C4C
Fail
a Download2.17:14.5:1
#000000
#4D4242
Fail
a Support1.98:14.5:1
#000000
#314050
Fail
a Get Involved1.70:14.5:1
#000000
#133754
Fail
a About1.19:14.5:1
#000000
#061A2C
Fail
a Jobs4.90:14.5:1
#000000
#927181
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 21 passed
REVIEW
85

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
Blender Foundation section > ul > li > a
Blender Institute section > ul > li > a
Blender Studio section > ul > li > a
License section > ul > li > a
Logo & Trademark section > ul > li > a
Credits section > ul > li > a
Privacy Policy section > ul > li > a
Code of Conduct section > ul > li > a
People section > ul > li > a
Jobs section > ul > li > a
Latest Blender section > ul > li > a
Blender LTS section > ul > li > a
Previous Versions section > ul > li > a
Experimental Builds section > ul > li > a
Source Code section > ul > li > a
Requirements section > ul > li > a
Benchmark section > ul > li > a
Flamenco section > ul > li > a
Add-ons section > ul > li > a
Themes section > ul > li > a
Get Started section > ul > li > a
Projects section > ul > li > a
Docs section > ul > li > a
Blog section > ul > li > a
Forum section > ul > li > a
YouTube section > ul > li > a
Python API section > ul > li > a
Films section > ul > li > a
Training section > ul > li > a
Tools & Pipeline section > ul > li > a
Manual section > ul > li > a
Community section > ul > li > a
FAQ section > ul > li > a
Documentation section > ul > li > a
Education section > ul > li > a
Press Releases section > ul > li > a
User Stories section > ul > li > a
One-time Donation section > ul > li > a.text-center
Artistic freedom starts with Blender The Free and Open Source 3D Creation Suite body.ps-homepage > footer.footer-note
The Free and Open Source 3D Creation Suite body.ps-homepage > footer.footer-note > span

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.page-card-list > li.feature-item > div.feature-image > img ul.page-card-list > li.feature-item > div.feature-image > img
ul.page-card-list > li.feature-item > div.feature-image > img ul.page-card-list > li.feature-item > div.feature-image > img
ul.page-card-list > li.feature-item > div.feature-image > img ul.page-card-list > li.feature-item > div.feature-image > img
ul.page-card-list > li.feature-item > div.feature-image > img ul.page-card-list > li.feature-item > div.feature-image > img
ul.page-card-list > li.feature-item > div.feature-image > img ul.page-card-list > li.feature-item > div.feature-image > img
ul.page-card-list > li.feature-item > div.feature-image > img ul.page-card-list > li.feature-item > div.feature-image > img

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About div.row > div.col-6 > section > a.sitemap-title
Blender Foundation section > ul > li > a
Blender Institute section > ul > li > a
Blender Studio section > ul > li > a
License section > ul > li > a
Logo & Trademark section > ul > li > a
Credits section > ul > li > a
Privacy Policy section > ul > li > a
Code of Conduct section > ul > li > a
People section > ul > li > a
Jobs section > ul > li > a
Blender Network div.container > div.row > div.col-6 > a.sitemap-title
Download div.row > div.col-6 > section > a.sitemap-title
Latest Blender section > ul > li > a
Blender LTS section > ul > li > a
Previous Versions section > ul > li > a
Experimental Builds section > ul > li > a
Source Code section > ul > li > a
Requirements section > ul > li > a
Benchmark section > ul > li > a
Flamenco section > ul > li > a
Extensions div.row > div.col-6 > section > a.sitemap-title
Add-ons section > ul > li > a
Themes section > ul > li > a
Developers div.row > div.col-6 > section > a.sitemap-title
Get Started section > ul > li > a
Projects section > ul > li > a
Docs section > ul > li > a
Blog section > ul > li > a
Forum section > ul > li > a
YouTube section > ul > li > a
Python API section > ul > li > a
Blender Studio div.row > div.col-6 > section > a.sitemap-title
Films section > ul > li > a
Training section > ul > li > a
Tools & Pipeline section > ul > li > a
Support div.row > div.col-6 > section > a.sitemap-title
Manual section > ul > li > a
Community section > ul > li > a
FAQ section > ul > li > a
Get Involved div.row > div.col-6 > section > a.sitemap-title
Documentation section > ul > li > a
Education section > ul > li > a
News div.row > div.col-6 > section > a.sitemap-title
Press Releases section > ul > li > a
User Stories section > ul > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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
●`[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
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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+
Heading Hierarchy
7 headings
PASS
7 headings
Info::
Single H1 present
  • H1 Blender 5.1
  • H2 Latest News
  • H2 Blender Development
  • H2 Blender Studio
  • H2 Free and Open Source
  • H2 Part of the industry
  • H2 It’s about people.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
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.

Send Feedback