Skip to content
https://www.clojure.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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 (missing!)

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

D
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Clojure - Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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
No dark mode signals
FIX
No dark mode signals
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 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
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::
1 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 1 <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
Heading Hierarchy
Action
24 headings, 1 skip(s)
REVIEW
24 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 The Clojure Programming Language
  • H3 Learn More
  • H4 Rationale
  • H4 Getting Started
  • H4 Reference
  • H4 Guides
  • H4 Community
  • H3 Companies Succeeding with Clojure
  • H3 Features
  • H4 Dynamic Development
  • H4 Functional Programming
  • H4 LISP
  • H4 Runtime Polymorphism
  • H4 Concurrent Programming
  • H4 Hosted on the JVM
  • H3 News
  • H3 Upcoming Events
  • H3 Nubank
  • H6 Community skipped
  • H6 Legal
  • H6 Documentation
  • H6 Updates
  • H6 ETC
  • H6 Code

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="searchType" id="searchType">; <input type="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="q">
3 controls
0 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#qtext(Search clojure.org reference, guides, and API)placeholder only
#searchTypeselect(none)none
inputsubmit(none)none

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

<select name="searchType" id="searchType">; <input type="submit">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q" id="q">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA
title Clojure
2.76:1
#000000
on
#2451A0
needs 4.5:1 (normal text)
16px · top of page (header area)
div Clojure
2.76:1
#000000
on
#2451A0
needs 4.5:1 (normal text)
16px · top of page (header area)
a Overview
2.76:1
#000000
on
#2451A0
needs 4.5:1 (normal text)
16px · top of page (header area)
a Reference‍
2.76:1
#000000
on
#2451A0
needs 4.5:1 (normal text)
16px · top of page (header area)
a API
2.76:1
#000000
on
#2451A0
needs 4.5:1 (normal text)
16px · above the fold
a Releases
2.76:1
#000000
on
#2451A0
needs 4.5:1 (normal text)
16px · above the fold
a Guides
2.76:1
#000000
on
#2451A0
needs 4.5:1 (normal text)
16px · above the fold
a Community
2.76:1
#000000
on
#2451A0
needs 4.5:1 (normal text)
16px · above the fold
a Dev
2.80:1
#000000
on
#2452A1
needs 4.5:1 (normal text)
16px · above the fold
a News
2.76:1
#000000
on
#2351A1
needs 4.5:1 (normal text)
16px · above the fold
a
2.76:1
#000000
on
#2351A1
needs 4.5:1 (normal text)
16px · above the fold
option clojure.org
2.76:1
#000000
on
#2351A1
needs 4.5:1 (normal text)
16px · above the fold
option ask.clojure.org
2.76:1
#000000
on
#2351A1
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 The Clojure Programm…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Learn More21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Companies Succeeding…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Features21.00:13.0:1
#000000
#FFFFFF
Pass
h3 News21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Upcoming Events21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Nubank21.00:13.0:1
#000000
#FFFFFF
Pass
title Clojure2.76:14.5:1
#000000
#2451A0
Fail
div Clojure2.76:14.5:1
#000000
#2451A0
Fail
a Overview2.76:14.5:1
#000000
#2451A0
Fail
a Reference‍2.76:14.5:1
#000000
#2451A0
Fail
a API2.76:14.5:1
#000000
#2451A0
Fail
a Releases2.76:14.5:1
#000000
#2451A0
Fail
a Guides2.76:14.5:1
#000000
#2451A0
Fail
a Community2.76:14.5:1
#000000
#2451A0
Fail
a Dev2.80:14.5:1
#000000
#2452A1
Fail
a News2.76:14.5:1
#000000
#2351A1
Fail
a 2.76:14.5:1
#000000
#2351A1
Fail
option clojure.org2.76:14.5:1
#000000
#2351A1
Fail
option ask.clojure.org2.76:14.5:1
#000000
#2351A1
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 4 failing, 14 passed
REVIEW
81

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
Companies Succeeding with Clojure div.w-section > div.w-container > div > h3.clj-home-companies-heading
Anthony Marcar, Senior Architect Walmart Labs div.w-row > div.w-col > div.clj-home-company > div.clj-home-company-attribution
Chris Price, Software Engineer Puppet Labs div.w-row > div.w-col > div.clj-home-company > div.clj-home-company-attribution
Dave Elliman, Head of Technology ThoughtWorks div.w-row > div.w-col > div.clj-home-company > div.clj-home-company-attribution
Read more about Clojure success stories, how the community uses Clojure, and fi… div.w-section > div.w-container > div.clj-home-company-text > p
success stories div.w-container > div.clj-home-company-text > p > a.clj-home-company-link
community div.w-container > div.clj-home-company-text > p > a.clj-home-company-link
companies using Clojure div.w-container > div.clj-home-company-text > p > a.clj-home-company-link
2026-03-30 div.clj-home-updates-container > ul.w-list-unstyled > li > span.clj-home-updates-date
Clojure Zero to REPL Video div.clj-home-updates-container > ul.w-list-unstyled > li > a.clj-home-updates-link
2026-03-26 div.clj-home-updates-container > ul.w-list-unstyled > li > span.clj-home-updates-date
Clojure Documentary Trailer (Mar 26, 2026) div.clj-home-updates-container > ul.w-list-unstyled > li > a.clj-home-updates-link
2026-03-18 div.clj-home-updates-container > ul.w-list-unstyled > li > span.clj-home-updates-date
Clojure Deref (Mar 18, 2026) div.clj-home-updates-container > ul.w-list-unstyled > li > a.clj-home-updates-link
2026-03-11 div.clj-home-updates-container > ul.w-list-unstyled > li > span.clj-home-updates-date
core.async and Virtual Threads div.clj-home-updates-container > ul.w-list-unstyled > li > a.clj-home-updates-link
2026-03-10 div.clj-home-updates-container > ul.w-list-unstyled > li > span.clj-home-updates-date
Clojure Deref (Mar 10, 2026) div.clj-home-updates-container > ul.w-list-unstyled > li > a.clj-home-updates-link
2026-04-09 div.clj-home-updates-container > ul.w-list-unstyled > li > span.clj-home-updates-date
Los Angeles Clojure Meetup: Hyper div.clj-home-updates-container > ul.w-list-unstyled > li > a.clj-home-updates-link
2026-04-16 div.clj-home-updates-container > ul.w-list-unstyled > li > span.clj-home-updates-date
Clojure Documentary Premiere div.clj-home-updates-container > ul.w-list-unstyled > li > a.clj-home-updates-link
2026-04-25 div.clj-home-updates-container > ul.w-list-unstyled > li > span.clj-home-updates-date
Clojure Community Check-In div.clj-home-updates-container > ul.w-list-unstyled > li > a.clj-home-updates-link
2026-05-09 div.clj-home-updates-container > ul.w-list-unstyled > li > span.clj-home-updates-date
Dutch Clojure Days free conference div.clj-home-updates-container > ul.w-list-unstyled > li > a.clj-home-updates-link

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
COMMUNITY div.w-container > div.w-row > div.w-col > h6.clj-footer-heading

These are opportunities to improve keyboard navigation in your application.

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
div.w-container > div.w-row > div.w-col > img.clj-home-support-logo div.w-container > div.w-row > div.w-col > img.clj-home-support-logo

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

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.w-mod-js html.w-mod-js

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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">`
○`<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
Alt Text Quality
1 of 3 images have issues
PASS
1 of 3 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 image(s) with good alt text
3 images 2 good alt text 1 missing
IssueCount
missing1 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

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

Send Feedback