Skip to content
https://flaticon.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

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>.

Why this matters

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.

Why this matters

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

F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Access denied ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
2 headings
REVIEW
2 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H4 Error
  • H4 Access denied

Every page should have one H1 that describes the page content.

Why this matters

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

C
Favicon & Branding
Action
9 icon(s) detected
REVIEW
9 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
11 text elements analyzed, 10 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

1 pass 10 fail WCAG AA 1 pass AA only
title Access denied
1.43:1
#000000
on
#22244E
needs 4.5:1 (normal text)
16px · top of page (header area)
h4 Error
1.43:1
#000000
on
#22244E
needs 3.0:1 (large text)
16px · top of page (header area)
span 403
2.74:1
#000000
on
#2C4DA9
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
b Reference:
2.21:1
#000000
on
#29408C
needs 3.0:1 (large text)
16px · above the fold · over background image/gradient
p 0.8d631302.1776801071.5cce9d55
1.41:1
#000000
on
#21234D
needs 4.5:1 (normal text)
16px · above the fold
b My IP Address:
2.41:1
#000000
on
#703D35
needs 3.0:1 (large text)
16px · above the fold · over background image/gradient
p 141.227.188.193
1.63:1
#000000
on
#2A2C60
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p You don't have permission to access this…
1.43:1
#000000
on
#22244E
needs 4.5:1 (normal text)
16px · above the fold
p If the problem persists, contact our sup…
1.43:1
#000000
on
#22244E
needs 4.5:1 (normal text)
16px · above the fold
a support@freepik.com
1.43:1
#000000
on
#22244E
needs 4.5:1 (normal text)
16px · above the fold

4 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 (11)
ElementRatioRequiredFGBGResult
title Access denied1.43:14.5:1
#000000
#22244E
Fail
h4 Error1.43:13.0:1
#000000
#22244E
Fail
span 4032.74:14.5:1
#000000
#2C4DA9
Fail
h4 Access denied4.07:13.0:1
#000000
#3165E0
Pass
b Reference:2.21:13.0:1
#000000
#29408C
Fail
p 0.8d631302.177680107…1.41:14.5:1
#000000
#21234D
Fail
b My IP Address:2.41:13.0:1
#000000
#703D35
Fail
p 141.227.188.1931.63:14.5:1
#000000
#2A2C60
Fail
p You don't have permi…1.43:14.5:1
#000000
#22244E
Fail
p If the problem persi…1.43:14.5:1
#000000
#22244E
Fail
a support@freepik.com1.43:14.5:1
#000000
#22244E
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.

C
Lighthouse Accessibility Audits
Action
Score 71/100 — 7 failing, 22 passed
REVIEW
71

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.push-right > div#gr_user_menu > div#notification-center-menu-trigger > button#notification-center-menu__trigger-icon div.push-right > div#gr_user_menu > div#notification-center-menu-trigger > button#notification-center-menu__trigger-icon
section#viewport > aside#collections > header.collection-section-header > button.hide-collections section#viewport > aside#collections > header.collection-section-header > button.hide-collections
aside#collections > header.collection-section-header > div.tooltip > button#list_collections_btn aside#collections > header.collection-section-header > div.tooltip > button#list_collections_btn
aside#collections > header.collection-section-header > div.tooltip > button#new_collection_btn aside#collections > header.collection-section-header > div.tooltip > button#new_collection_btn
div.header-options > div.popover > div.popover-container > button.collection-options div.header-options > div.popover > div.popover-container > button.collection-options
section.collection > header.collection-header > div.edit-name > button.flaticon-disk section.collection > header.collection-header > div.edit-name > button.flaticon-disk
div.stickers > section.search-holder > form.home_search_input > button.clean-search__button div.stickers > section.search-holder > form.home_search_input > button.clean-search__button
div.stickers > section.search-holder > form.home_search_input > button.bj-button div.stickers > section.search-holder > form.home_search_input > button.bj-button

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.empty-collection > div.empty-collection-content > div.empty-collection-register > img div.empty-collection > div.empty-collection-content > div.empty-collection-register > img
div.home__figma > div.row > div.col__xs--12 > img.lzy div.home__figma > div.row > div.col__xs--12 > img.lzy

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.collection > header.collection-header > div.edit-name > input.collection-name-input section.collection > header.collection-header > div.edit-name > input.collection-name-input

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.push-right > div#gr_user_menu > div#gr_not-connected > a.track div.push-right > div#gr_user_menu > div#gr_not-connected > a.track

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Do you want to make a personalized icon pack? div.empty-collection > div.empty-collection-content > div.empty-collection-register > p
Just add the icons you want to the collection and download them in the format y… div.empty-collection > div.empty-collection-content > div.empty-collection-register > p
Register for free div.empty-collection > div.empty-collection-content > div.empty-collection-register > a.bj-button
Create up to 3 collections div.empty-collection-content > div.empty-collection-register > p.register-check > span.v-alignc
Add 256 icons per collection div.empty-collection-content > div.empty-collection-register > p.register-check > span.v-alignc
Save and customize your icons div.empty-collection-content > div.empty-collection-register > p.register-check > span.v-alignc
50,400+ free, UI icons in 9 different styles. All fully editable and customizab… div.home__free-svg > div.home__free-svg__header > div > p
200 icons div.home__free-svg > div.home__free-svg__container > a.home__free-svg-brands > span.font-xs
10,000 icons div.home__free-svg > div.home__free-svg__container > a.home__free-svg-bold > span.font-xs
13,000 icons div.home__free-svg > div.home__free-svg__container > a.home__free-svg-regular > span.font-xs
13,000 icons div.home__free-svg > div.home__free-svg__container > a.home__free-svg-solid > span.font-xs
13,000 icons div.home__free-svg > div.home__free-svg__container > a.home__free-svg-thin > span.font-xs
Editor div.slider-box--items > div.item > div > p.item-title
Google Workspace div.slider-box--items > div.item > div > p.item-title
Create multiple collections to have your icons organized and download them in t… div.container > div.slider-box > div.slider-box--items-mobile > p.item-text
Browse all div.whats-new-section > div.row > div.whats-new-section__text > a.bj-button
Try the Plugin div.home__figma > div.row > div.col__xs--12 > a.bj-button
Contributor access div.row > div.push-right > div.row > a.bj-button
Accept All div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-accept-btn-handler
Reject All div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-reject-all-handler

These are opportunities to improve the legibility of your content.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Icons a.track > div.cards-products-home__item > div.cards-products-home__item__text > h6.font-lg
What’s New in Flaticon div.whats-new-section > div.row > div.whats-new-section__text > h5.mg-none

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback