Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureActionNo landmarksFIX
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>.
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.
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
FAlt Text QualityAction4 of 11 images have issuesFIX
| Issue | Count |
|---|---|
| missing | 4 image(s) |
Images without alt text are invisible to screen readers.
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
An image inside a link with no alt creates an empty link.
Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.
Learn more ▾ ▴
An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.
Source: WCAG 2.1 SC 2.4.4
DFavicon & BrandingAction3 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy5 headingsREVIEW
- H2 What is curl used for?
- H2 curl supports
- H2 Who makes curl?
- H2 What is the latest curl?
- H2 Where is the code?
Every page should have one H1 that describes the page content.
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
BLink & Button Quality2 issue(s) across 79 links and 0 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| / | (empty) | empty | Add link text or aria-label |
| https://youtu.be/V5vZWHP-RqU | (empty) | empty | Add link text or aria-label |
Links without text are announced as raw URLs by screen readers.
/; https://youtu.be/V5vZWHP-RqU
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
B404 Error PageHTTP 404, custom pageREVIEW
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
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 |
|---|---|---|---|---|---|
| h2 What is curl used fo… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 curl supports | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Who makes curl? | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 What is the latest c… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Where is the code? | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title curl | 1.69:1 | 4.5:1 | #000000 | #093754 | Fail |
| a Download | 1.69:1 | 4.5:1 | #000000 | #093754 | Fail |
| a Browse source | 1.69:1 | 4.5:1 | #000000 | #093754 | Fail |
| a Changelog | 1.69:1 | 4.5:1 | #000000 | #093754 | Fail |
| a Release candidates | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Release log | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a tiny-curl | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Documentation | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Project | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a FAQ | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Help us | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Known bugs | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Known risks | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a TODO | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Protocols | 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.
CLighthouse Accessibility AuditsActionScore 78/100 — 3 failing, 11 passedREVIEW
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
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.contents > div > div.sidebar-box > img div.contents > div > div.sidebar-box > img |
div.contents > div > div.sidebar-box > img div.contents > div > div.sidebar-box > img |
div.sidebar-box > p > a > img div.sidebar-box > p > a > img |
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 |
|---|
div > div.sidebar-box > p > a div > div.sidebar-box > p > a |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.