Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction5 landmarksFIX
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
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
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
FFavicon & BrandingAction2 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
BForm Accessibility2 of 3 controls have issuesREVIEW
| Control | Type | Label | Method |
|---|---|---|---|
| input | checkbox | none | |
| #icons-search-input | text | (Search icons...) | placeholder only |
| #v-0-0 | (Enter your email...) | placeholder only |
Placeholder text disappears on focus and is not a reliable label.
<input type="text" name="search-input" id="icons-search-input">; <input type="email" id="v-0-0">
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
C404 Error PageActionHTTP 404, custom pageREVIEW
A+Heading Hierarchy11 headingsPASS
- H1 Original stock graphics by our team, plus design apps and AI tools
- H2 Start your next project here
- H2 Get rid of routine
- H2 Toys for design nerds
- H3 Generate humans with AI
- H3 AI icon replacer
- H3 Hackable icon URLs
- H3 Anonymize your identity with AI
- H2 Tutorials
- H2 Developers
- H2 Community
A+Alt Text Quality1 of 92 images have issuesPASS
| Issue | Count |
|---|---|
| generic | 1 image(s) |
ALink & Button Quality174 links, 3 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://icons8.com/blog | Blog | new tab | Add '(opens in new tab)' to text |
| https://www.youtube.com/playlist?list=PL… | See all | new tab | Add '(opens in new tab)' to text |
| https://www.cdn77.com/ | CDN77 | new tab | Add '(opens in new tab)' to text |
Add '(opens in new tab)' to link text or aria-label.
https://icons8.com/blog; https://www.youtube.com/playlist?list=PL7NuoYuwcraAe-JjfYG0EgeEtB50TnZqZ; https://www.cdn77.com/
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
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 Original stock graph… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Start your next proj… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Get rid of routine | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Toys for design nerd… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Tutorials | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Developers | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Community | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Generate humans with… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 AI icon replacer | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Hackable icon URLs | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Anonymize your ident… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Free Icons, Clipart … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Icons8 | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Icons | 20.82:1 | 4.5:1 | #000000 | #FEFEFE | Pass |
| div Illustrations | 20.40:1 | 4.5:1 | #000000 | #F9FCFF | Pass |
| div Photos | 18.87:1 | 4.5:1 | #000000 | #EAF4FE | Pass |
| a Music | 18.87:1 | 4.5:1 | #000000 | #EAF4FE | Pass |
| a Lunacy | 18.72:1 | 4.5:1 | #000000 | #E9F3FE | Pass |
| a Blog | 18.02:1 | 4.5:1 | #000000 | #EAEDFC | Pass |
| a Forum | 18.53:1 | 4.5:1 | #000000 | #EFF0FB | 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 95/100 — 2 failing, 25 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 |
|---|
AI div.i8-search-switch > label.i8-switch > span.i8-switch__content > span.i8-search-switch__label |
Protected by reCAPTCHA and the Google Privacy Policy and the Terms of Service a… footer#app-footer > div._container_1hzf9_70 > div._body_1hzf9_82 > p._communityDisclaimer_1hzf9_105 |
Privacy Policy div._container_1hzf9_70 > div._body_1hzf9_82 > p._communityDisclaimer_1hzf9_105 > a |
Terms of Service div._container_1hzf9_70 > div._body_1hzf9_82 > p._communityDisclaimer_1hzf9_105 > a |
These are opportunities to improve the legibility of your content.
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.