Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FFavicon & BrandingAction2 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction3 landmarksREVIEW
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
BHeading Hierarchy14 headings, 1 skip(s)REVIEW
- H2 (empty)
- H1 An independent computing platform for everyone
- H2 A more elegant way to use your computer
- H2 Room to Breathe
- H2 Batteries Included
- H2 Ecosystem
- H4 GNOME Circle skipped
- H4 Flathub
- H4 Developer Platform
- H2 Get Involved
- H2 Get GNOME
- H2 Supporting Organizations
- H2 Support Us
- H3 Select Language
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
Empty headings appear in the document outline but provide no information.
Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.
Source: WCAG 2.4.6
C404 Error PageActionHTTP 404, custom pageREVIEW
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
A+Alt Text QualityAll 28 images OKPASS
A+Form AccessibilityNo form controlsPASS
A+Link & Button Quality63 links, 0 buttons — all OKPASS
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
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 An independent compu… | 15.11:1 | 3.0:1 | #000000 | #CEDCEF | Pass |
| h2 A more elegant way t… | 15.94:1 | 3.0:1 | #000000 | #D7E1F2 | Pass |
| h2 Room to Breathe | 14.96:1 | 3.0:1 | #000000 | #CADBF5 | Pass |
| h2 Batteries Included | 15.22:1 | 3.0:1 | #000000 | #CBDDF7 | Pass |
| h2 Ecosystem | 15.37:1 | 3.0:1 | #000000 | #CCDEF8 | Pass |
| h2 Get Involved | 18.10:1 | 3.0:1 | #000000 | #EEEEEE | Pass |
| h2 Get GNOME | 18.10:1 | 3.0:1 | #000000 | #EEEEEE | Pass |
| h2 Supporting Organizat… | 18.10:1 | 3.0:1 | #000000 | #EEEEEE | Pass |
| h2 Support Us | 18.10:1 | 3.0:1 | #000000 | #EEEEEE | Pass |
| h3 Select Language | 18.10:1 | 3.0:1 | #000000 | #EEEEEE | Pass |
| title GNOME — An indepen… | 17.91:1 | 4.5:1 | #000000 | #ECEDEE | Pass |
| a About Us | 17.71:1 | 4.5:1 | #000000 | #E9ECEF | Pass |
| a Get Involved | 17.54:1 | 4.5:1 | #000000 | #E7EBF0 | Pass |
| a Donate | 17.25:1 | 4.5:1 | #000000 | #E5E9F0 | Pass |
| p Hit the | 16.53:1 | 4.5:1 | #000000 | #DBE5F4 | Pass |
| kbd Super Key | 14.82:1 | 4.5:1 | #000000 | #CADAF2 | Pass |
| p any time to get an o… | 14.81:1 | 4.5:1 | #000000 | #C9DAF3 | Pass |
| span Continue using your … | 15.45:1 | 4.5:1 | #000000 | #D0DEF5 | Pass |
| strong Visit endof10.org | 15.90:1 | 3.0:1 | #000000 | #D4E1F6 | Pass |
| p Spread out your work… | 14.64:1 | 4.5:1 | #000000 | #C6D9F5 | 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+Lighthouse Accessibility AuditsScore 96/100 — 2 failing, 21 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 |
|---|
GNOME Circle div.tiles > div.tile > div.description > h4 |
These are opportunities to improve keyboard navigation in your application.
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.