Skip to content
https://llvm.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
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'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 65/100 — 5 failing, 11 passed
FIX
65

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
body > div.www_title > img body > div.www_title > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.www_sidebar > form > div > input div.www_sidebar > form > div > input

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
Overview tr > td > div.www_sidebar > a
Features tr > td > div.www_sidebar > a
Documentation tr > td > div.www_sidebar > a
Command Guide tr > td > div.www_sidebar > a
FAQ tr > td > div.www_sidebar > a
Publications tr > td > div.www_sidebar > a
LLVM Projects tr > td > div.www_sidebar > a
Open Projects tr > td > div.www_sidebar > a
LLVM Users tr > td > div.www_sidebar > a
Bug tracker tr > td > div.www_sidebar > a
LLVM Logo tr > td > div.www_sidebar > a
Blog tr > td > div.www_sidebar > a
Meetings tr > td > div.www_sidebar > a
LLVM Foundation tr > td > div.www_sidebar > a
All Releases tr > td > div.www_sidebar > a
APT Packages tr > td > div.www_sidebar > a
RPM Snapshots tr > td > div.www_sidebar > a
Pre-releases tr > td > div.www_sidebar > a
div.www_sidebar > form > div > input div.www_sidebar > form > div > input
div.www_sidebar > form > div > input div.www_sidebar > form > div > input
doxygen tr > td > div.www_sidebar > a
Sources (GitHub) tr > td > div.www_sidebar > a
Code Review tr > td > div.www_sidebar > a
Blog tr > td > div.www_sidebar > a
Bug tracker tr > td > div.www_sidebar > a
Buildbot tr > td > div.www_sidebar > a
Green Dragon tr > td > div.www_sidebar > a
LNT tr > td > div.www_sidebar > a
Scan-build tr > td > div.www_sidebar > a
llvm-cov tr > td > div.www_sidebar > a
All Announcements td > div.www_sidebar > span > a
October 27-29, 2025 div.www_text > ul > li > a
June 10, 2025 div.www_text > ul > li > a
April 14-16, 2025 div.www_text > ul > li > a
October 22-24, 2024 div.www_text > ul > li > a
April 10-11, 2024 div.www_text > ul > li > a
October 9-11, 2023 div.www_text > ul > li > a
May 10-11, 2023 div.www_text > ul > li > a
November 8-9, 2022 div.www_text > ul > li > a
May 10-11, 2022 div.www_text > ul > li > a
November 16-19, 2021 div.www_text > ul > li > a
October 6-8, 2020 div.www_text > ul > li > a
October 22-23, 2019 div.www_text > ul > li > a
April 8-9, 2019 div.www_text > ul > li > a
October 17-18, 2018 div.www_text > ul > li > a
April 16-17, 2018 div.www_text > ul > li > a
October 18-19, 2017 div.www_text > ul > li > a
March 27-28, 2017 div.www_text > ul > li > a
November 3-4, 2016 div.www_text > ul > li > a
March 17-18, 2016 div.www_text > ul > li > a
October 29-30, 2015 div.www_text > ul > li > a
April 13-14, 2015 div.www_text > ul > li > a
October 28-29, 2014 div.www_text > ul > li > a
April 7-8, 2014 div.www_text > ul > li > a
Nov 6-7, 2013 div.www_text > ul > li > a
April 29-30, 2013 div.www_text > ul > li > a
November 7-8, 2012 div.www_text > ul > li > a
April 12, 2012 div.www_text > ul > li > a
November 18, 2011 div.www_text > ul > li > a
September 2011 div.www_text > ul > li > a
November 2010 div.www_text > ul > li > a
October 2009 div.www_text > ul > li > a
August 2008 div.www_text > ul > li > a
May 2007 div.www_text > 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-hidden="true"]` is not present on the document `<body>`
●Input buttons have discernible text.
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●The page contains a heading, skip link, or landmark region
●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
○Deprecated ARIA roles were not used
○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
○`[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
○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
○`<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
○Heading elements appear in a sequentially-descending order
○`<html>` element has a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="q">; <input type="submit" name="submit">
2 controls
0 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
qtext(none)none
submitsubmit(none)none

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

<input type="text" name="q">; <input type="submit" name="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

B
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)
ElementRatioRequiredFGBGResult
title The LLVM Compiler In…21.00:14.5:1
#000000
#FFFFFF
Pass
div The21.00:14.5:1
#000000
#FFFFFF
Pass
strong LLVM21.00:13.0:1
#000000
#FFFFFF
Pass
div Compiler Infrastruct…21.00:14.5:1
#000000
#FFFFFF
Pass
b Site Map:21.00:13.0:1
#000000
#FFFFFF
Pass
a Overview21.00:14.5:1
#000000
#FFFFFF
Pass
a Features19.77:14.5:1
#000000
#F8F8F8
Pass
a Documentation18.59:14.5:1
#000000
#F1F1F1
Pass
a Command Guide8.83:14.5:1
#000000
#A8A8A8
Pass
a FAQ21.00:14.5:1
#000000
#FFFFFF
Pass
a Publications15.61:14.5:1
#000000
#DEDEDE
Pass
a LLVM Projects21.00:14.5:1
#000000
#FFFFFF
Pass
a Open Projects21.00:14.5:1
#000000
#FFFFFF
Pass
a LLVM Users21.00:14.5:1
#000000
#FFFFFF
Pass
a Bug tracker9.36:14.5:1
#000000
#ADADAD
Pass
a LLVM Logo21.00:14.5:1
#000000
#FFFFFF
Pass
a Blog5.82:14.5:1
#000000
#7878F6
Pass
a Meetings21.00:14.5:1
#000000
#FFFFFF
Pass
a LLVM Foundation10.59:14.5:1
#000000
#B8B8B8
Pass
b Download!21.00:13.0: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.

A
Alt Text Quality
1 of 1 images have issues
PASS
1 of 1 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
1 images 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