Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FFavicon & BrandingAction1 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure2 landmarksREVIEW
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 HierarchyNo headingsREVIEW
No headings found
Headings create the document outline for screen reader navigation.
Headings (H1-H6) create the document outline for screen reader navigation.
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
C404 Error PageActionCould not testREVIEW
404 page quality check not available.
CColor Contrast (Screenshot)Action13 text elements analyzed, 3 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
1 contrast failures on background images/gradients
These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.
Show all checked elements (13)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| title Lycos.com | 7.46:1 | 4.5:1 | #000000 | #999A9C | Pass |
| button Search | 7.64:1 | 4.5:1 | #000000 | #9B9C9E | Pass |
| p To our users of Ange… | 7.83:1 | 4.5:1 | #000000 | #9D9EA0 | Pass |
| span Mail users can now a… | 2.31:1 | 4.5:1 | #5E6278 | #9FA1A1 | Fail |
| a webmail.lycos.com | 8.22:1 | 4.5:1 | #000000 | #A1A2A4 | Pass |
| p © 2025 | 8.42:1 | 4.5:1 | #000000 | #A3A4A6 | Pass |
| a lycos.com | 8.72:1 | 4.5:1 | #000000 | #A6A7A9 | Pass |
| p All rights reserved. | 8.93:1 | 4.5:1 | #000000 | #A8A9AB | Pass |
| a Home | 9.34:1 | 4.5:1 | #000000 | #ACADAE | Pass |
| a Contact | 9.79:1 | 4.5:1 | #000000 | #B0B1B3 | Pass |
| a Privacy Policy | 8.93:1 | 4.5:1 | #000000 | #A8A9AB | Pass |
| a Terms of Service | 4.11:1 | 4.5:1 | #000000 | #6D6E70 | Fail |
| a For Advertisers | 2.09:1 | 4.5:1 | #000000 | #414244 | 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.
AAlt Text Quality1 of 1 images have issuesPASS
| Issue | Count |
|---|---|
| missing | 1 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
AForm Accessibility1 of 1 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| kw | text | (Search...) | placeholder only |
Placeholder text disappears on focus and is not a reliable label.
<input type="text" name="kw">
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
A+Link & Button Quality7 links, 1 buttons — all OKPASS
ALighthouse Accessibility AuditsScore 93/100 — 1 failing, 17 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.
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 |
|---|
form > div.search-form-container > div.col-12 > img.mx-auto form > div.search-form-container > div.col-12 > img.mx-auto |
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.