Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FForm AccessibilityAction8 of 13 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| #CybotCookiebotDialogBodyLevelButtonNecessary | checkbox | Necessary | for/id |
| #CybotCookiebotDialogBodyLevelButtonPreferences | checkbox | Preferences | for/id |
| #CybotCookiebotDialogBodyLevelButtonStatistics | checkbox | Statistics | for/id |
| #CybotCookiebotDialogBodyLevelButtonMarketing | checkbox | Marketing | for/id |
| #CybotCookiebotDialogBodyContentCheckboxPersonalInformation | checkbox | Do not sell or share my personal information | for/id |
| query | text | ( search for premium domains on fruits) | placeholder only |
| query | text | (search domain on fruits) | placeholder only |
| #CybotCookiebotDialogBodyLevelButtonMarketingInline | checkbox | (none) | none |
| #CybotCookiebotDialogBodyLevelButtonNecessaryInline | checkbox | (none) | none |
| #CybotCookiebotDialogBodyLevelButtonPreferencesInline | checkbox | (none) | none |
| input | submit | (none) | none |
| #CybotCookiebotDialogBodyLevelButtonStatisticsInline | checkbox | (none) | none |
| input | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <input type="submit">; <input type="submit">
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
Placeholder text disappears on focus and is not a reliable label.
<input type="text" name="query">; <input type="text" name="query">
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
DLink & Button QualityAction4 issue(s) across 49 links and 16 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.cookiebot.com/en/what-is-beh… | Cookiebot by Usercentrics - op… | new tab | Add '(opens in new tab)' to text |
| https://www.cookiebot.com/goto/privacy-p… | Learn more about this provider… | new tab | Add '(opens in new tab)' to text |
| https://business.safety.google/privacy/ | Learn more about this provider… | new tab | Add '(opens in new tab)' to text |
| https://www.intercom.com/terms-and-polic… | Learn more about this provider… | new tab | Add '(opens in new tab)' to text |
| https://segment.com/docs/legal/privacy/ | Learn more about this provider… | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/policy.php/ | Learn more about this provider… | new tab | Add '(opens in new tab)' to text |
| https://business.safety.google/privacy/ | Learn more about this provider… | new tab | Add '(opens in new tab)' to text |
| https://segment.com/docs/legal/privacy/ | Learn more about this provider… | new tab | Add '(opens in new tab)' to text |
| https://www.cookiebot.com | Cookiebot | new tab | Add '(opens in new tab)' to text |
| / | (empty) | empty | Add link text or aria-label |
| /explore/for-buyer | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: For Buyer | |||
| https://www.fruits.co/search?query= | More TLDs | new tab | Add '(opens in new tab)' to text |
| / | (empty) | empty | Add link text or aria-label |
| <input> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
/; /
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
Generic link text like 'click here' doesn't describe the destination.
/explore/for-buyer ("Learn more")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.cookiebot.com/goto/privacy-policy/; https://business.safety.google/privacy/; https://www.intercom.com/terms-and-policies#privacy; https://segment.com/docs/legal/privacy/; https://www.facebook.com/policy.php/; https://business.safety.google/privacy/; https://segment.com/docs/legal/privacy/; https://www.cookiebot.com; https://www.fruits.co/search?query=
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
Icon-only buttons need an aria-label so screen readers can announce them.
input[type="submit"].query-button (#626 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction2 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
C404 Error PageActionHTTP 404, custom pageREVIEW
BFavicon & Branding5 icon(s) detectedREVIEW
CWeb ManifestActionValid manifestREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 10 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
2 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 (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 No matter what your … | 16.98:1 | 3.0:1 | #000000 | #E7E7E7 | Pass |
| h1 No matter what your … | 16.98:1 | 3.0:1 | #000000 | #E7E7E7 | Pass |
| h2 Comfortable and secu… | 16.98:1 | 3.0:1 | #000000 | #E7E7E7 | Pass |
| h2 Comfortable and secu… | 16.98:1 | 3.0:1 | #000000 | #E7E7E7 | Pass |
| h2 Find your top-level … | 16.98:1 | 3.0:1 | #000000 | #E7E7E7 | Pass |
| h2 Find your top-level … | 16.98:1 | 3.0:1 | #000000 | #E7E7E7 | Pass |
| h2 Are you a domain sel… | 16.98:1 | 3.0:1 | #000000 | #E7E7E7 | Pass |
| h2 Get started with us … | 16.98:1 | 3.0:1 | #000000 | #E7E7E7 | Pass |
| title fruits | 2.01:1 | 4.5:1 | #000000 | #443183 | Fail |
| a Consent | 2.01:1 | 4.5:1 | #000000 | #433184 | Fail |
| a Details | 1.99:1 | 4.5:1 | #000000 | #433084 | Fail |
| a [#IABV2SETTINGS#] | 4.37:1 | 4.5:1 | #000000 | #C84446 | Fail |
| a About | 4.50:1 | 4.5:1 | #000000 | #CF4145 | Pass |
| div This website uses co… | 3.64:1 | 4.5:1 | #000000 | #9A4C70 | Fail |
| div We use cookies to pe… | 2.32:1 | 4.5:1 | #000000 | #4D3896 | Fail |
| div [#GPC_BANNER_ICON#] | 2.40:1 | 4.5:1 | #000000 | #50399B | Fail |
| div [#GPC_TOAST_TEXT#] | 2.53:1 | 4.5:1 | #000000 | #533CA1 | Fail |
| legend Consent Selection | 2.63:1 | 4.5:1 | #000000 | #553EA7 | Fail |
| strong Necessary | 2.72:1 | 3.0:1 | #000000 | #583FAC | Fail |
| strong Preferences | 4.05:1 | 3.0:1 | #000000 | #7862A0 | 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.
AHeading Hierarchy7 headingsPASS
- H1 No matter what your project is – find your premium domain.
- H1 No matter what your project is – find your premium domain duplicate H1
- H2 Comfortable and secure access to premium domains
- H2 Comfortable and secure access to premium domains.
- H2 Find your top-level domain
- H2 Find your top-level domain.
- H2 Are you a domain seller?Get started with us now.
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
A+Alt Text Quality1 of 12 images have issuesPASS
| Issue | Count |
|---|---|
| generic | 1 image(s) |
ALighthouse Accessibility AuditsScore 90/100 — 3 failing, 28 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.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
More TLDs div.container-large > div.section-component > div.flexbox-centered > a.text-link-orange |
Sell with fruits div.padding-xhuge > div.section-component > div.top-seller_wrapper > a.button |
These are opportunities to improve the legibility of your content.
Names and labels
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.form-block > form#wf-form-Domain-Search > div.submit-button_wrapper > input.query-button div.form-block > form#wf-form-Domain-Search > div.submit-button_wrapper > input.query-button |
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.footer-bottom_content-wrapper > div.footer-bottom_content > div.vertical-body > a.footer-brand-link div.footer-bottom_content-wrapper > div.footer-bottom_content > div.vertical-body > a.footer-brand-link |
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.