Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.F404 Error PageActionSoft 404 detectedFIX
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
FFavicon & BrandingAction1 icon(s) detectedFIX
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy6 headings, 1 skip(s)REVIEW
- H1 lencr.org
- H1 What’s lencr.org? duplicate H1
- H1 Why is my computer fetching this data? Is it malicious? duplicate H1
- H1 What exactly is this data for? duplicate H1
- H1 Why “lencr.org”? duplicate H1
- H4 Subscribe for email updates about Let's Encrypt and other ISRG projects skipped
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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
CLink & Button QualityAction4 issue(s) across 63 links and 4 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| #what-s-lencr-org | (empty) | empty | Add link text or aria-label |
| #why-is-my-computer-fetching-this-data-i… | (empty) | empty | Add link text or aria-label |
| #what-exactly-is-this-data-for | (empty) | empty | Add link text or aria-label |
| #why-lencr-org | (empty) | empty | Add link text or aria-label |
| https://www.abetterinternet.org | Internet Security Research Gro… | new tab | Add '(opens in new tab)' to text |
| https://github.com/letsencrypt | GitHub | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/company/lets-en… | new tab | Add '(opens in new tab)' to text | |
| https://www.abetterinternet.org/terms-of… | Terms | new tab | Add '(opens in new tab)' to text |
| https://www.abetterinternet.org/trademar… | Trademark Policy | new tab | Add '(opens in new tab)' to text |
Links without text are announced as raw URLs by screen readers.
#what-s-lencr-org; #why-is-my-computer-fetching-this-data-is-it-malicious; #what-exactly-is-this-data-for; #why-lencr-org
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://www.abetterinternet.org; https://github.com/letsencrypt; https://www.linkedin.com/company/lets-encrypt/; https://www.abetterinternet.org/terms-of-service; https://www.abetterinternet.org/trademarks
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
CColor Contrast (Screenshot)Action20 text elements analyzed, 4 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 lencr.org | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 What’s | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Why is my computer f… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 What exactly is this… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Why “ | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 ”? | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title lencr.org - Let's E… | 19.08:1 | 4.5:1 | #000000 | #F3F4F6 | Pass |
| span Languages | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span English | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Català | 1.84:1 | 4.5:1 | #000000 | #003A70 | Fail |
| span Čeština | 1.84:1 | 4.5:1 | #000000 | #003A70 | Fail |
| span Dansk | 1.84:1 | 4.5:1 | #000000 | #003A70 | Fail |
| span Deutsch | 1.84:1 | 4.5:1 | #000000 | #003A70 | Fail |
| span Greek | 5.72:1 | 4.5:1 | #000000 | #6689A9 | Pass |
| span Español | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Suomi | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Français | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span עברית | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Magyar | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Bahasa Indonesia | 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.
ALandmark Structure5 landmarksPASS
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
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
A+Alt Text QualityAll 3 images OKPASS
A+Form AccessibilityNo form controlsPASS
ALighthouse Accessibility AuditsScore 94/100 — 2 failing, 20 passedPASS
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
SUBSCRIBE FOR EMAIL UPDATES ABOUT LET'S ENCRYPT AND OTHER ISRG PROJECTS div.grid > div.pt-0 > div.border > h4.text-eyebrow |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
main > div.narrow-container > h1#what-s-lencr-org > a.autoanchor main > div.narrow-container > h1#what-s-lencr-org > a.autoanchor |
main > div.narrow-container > h1#why-is-my-computer-fetching-this-data-is-it-malicious > a.autoanchor main > div.narrow-container > h1#why-is-my-computer-fetching-this-data-is-it-malicious > a.autoanchor |
main > div.narrow-container > h1#what-exactly-is-this-data-for > a.autoanchor main > div.narrow-container > h1#what-exactly-is-this-data-for > a.autoanchor |
main > div.narrow-container > h1#why-lencr-org > a.autoanchor main > div.narrow-container > h1#why-lencr-org > a.autoanchor |
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.