Skip to content
https://fontawesome.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
2
PASS
7
INFO
0
Checks
13
7 PASS 2 REVIEW 4 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 2 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #528dd7
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 ModePartial Dark Mode
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
1 <nav> landmark(s) found
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.
Page Structure — as a screen reader sees it
BANNER header NAV "Awesomeverse Products + Links" MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page Not Found | Font Awesome ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A
Heading Hierarchy
43 headings
PASS
43 headings
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Font Awesome
  • H2 Font Awesome Elsewhere
  • H1 Font Awesome. Icons. Easy. Done.
  • H2 Font Awesome 7
  • H2 Link to Start for Free on this page No Reservations Required
  • H1 1 line of code… 1 million+ icons. duplicate H1
  • H2 Why do you need my email address?
  • H2 Link to Announcing Font Awesome 7 on this page New Recipe. Same Great Taste.
  • H2 Font Awesome 7 Pro
  • H3 Revamped + Refreshed Icons
  • H3 Fresh New Icons
  • H3 New Modifiers!
  • H3 Icon Upload!
  • H2 Included Icon Packs
  • H2 Link to New Icon Packs on this page Hot Off the Griddle
  • H1 New Icon Packs Pro+ duplicate H1
  • H2 Link to Tech Updates on this page Only the Freshest Ingredients
  • H2 Tech Updates
  • H3 Faster Load Times!
  • H3 Toolkit Updates!
  • H3 Consistent Icon Widths!
  • H3 Improved Accessibility!
  • H3 Great for Developers
  • H3 Great for Designers
  • H3 Great for Content Creators
  • H2 Link to Styling Toolkit on this page Seasoned to Perfection
  • H2 Styling Toolkit
  • H2 Link to Today's Specials on this page Today's Specials
  • H1 Go Pro (or Pro+) duplicate H1
  • H2 Font Awesome 7
  • H2 Proudly Open Source
  • H3 Always Free
  • H3 Support Open Source
  • H3 No Shenanigans
  • H3 Font Awesome is one of the top open source projects on GitHub.
  • H2 The Web's Default Icon Set, Used on Over 200 Million Sites
  • H2 Introducing Build Awesome!
  • H2 Font Awesome Font Awesome Go Make Something Awesome
  • H3 Awesomeverse
  • H3 Font Awesome
  • H3 Community
  • H3 Help
  • H2 Cookie. Cookie. Cookie.

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

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 Quality
All 7 images OK
PASS
All 7 images OK
Info::
7 image(s) with good alt text
7 images 7 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 38 controls have issues
PASS
1 of 38 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
37 control(s) properly labeled
38 controls
37 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#icons-searchtextSearch for Iconsfor/id
#emailemailEnter your email to get started start with a free Kit!for/id
#accept-policiescheckboxnone
#icon_familyselectIcon Familyfor/id
#color-noneradioDefault Colorfor/id
#color-yellowradioyellowfor/id
#color-tealradiotealfor/id
#color-blueradiobluefor/id
#color-violetradiovioletfor/id
#color-customradionone
#size-2xsradio2xsfor/id
#size-xsradioxsfor/id
#size-smradiosmfor/id
#size-noneradioDefault Sizefor/id
#size-lgradiolgfor/id
#size-xlradioxlfor/id
#size-2xlradio2xlfor/id
#rotate-noneradioNo Rotationfor/id
#rotate-90radio90°for/id
#rotate-180radio180°for/id
#rotate-270radio270°for/id
#rotate-customradioRotate customfor/id
#rotate-customnumberRotate customfor/id
#flip-noneradioNo Flipfor/id
#flip-horizontalradioFlip Horizontalfor/id
#flip-verticalradioFlip Verticalfor/id
#flip-bothradioFlip Bothfor/id
#animations-noneradioNo Animationfor/id
#animations-beatradioBeatfor/id
#animations-beat-faderadioBeat Fadefor/id
#animations-bounceradioBouncefor/id
#animations-faderadioFadefor/id
#animations-flipradioFlipfor/id
#animations-shakeradioShakefor/id
#animations-spinradioSpinfor/id
#animations-spin-reverseradioSpin Reversefor/id
#animations-spin-pulseradioSpin Pulsefor/id
#g-recaptcha-response-100000textarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

Why this matters

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

A
Favicon & Branding
6 icon(s) detected
PASS
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 1 line of code… 1 …18.58:13.0:1
#000000
#F0F1F3
Pass
h1 New Icon Packs18.58:13.0:1
#000000
#F0F1F3
Pass
h1 Go Pro (or Pro+)18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Font Awesome21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Font Awesome Elsewhe…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Font Awesome 718.58:13.0:1
#000000
#F0F1F3
Pass
h2 No Reservations Requ…18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Why do you need my e…18.58:13.0:1
#000000
#F0F1F3
Pass
h2 New Recipe. Same Gre…18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Font Awesome 718.58:13.0:1
#000000
#F0F1F3
Pass
h2 Included Icon Packs18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Hot Off the Griddle18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Only the Freshest In…18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Tech Updates18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Seasoned to Perfecti…18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Styling Toolkit18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Today's Specials18.58:13.0:1
#000000
#F0F1F3
Pass
h2 Font Awesome 718.58:13.0:1
#000000
#F0F1F3
Pass
h2 Proudly Open Source18.58:13.0:1
#000000
#F0F1F3
Pass
h2 The Web's Default Ic…18.58:13.0:1
#000000
#F0F1F3
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 Audits
Score 96/100 — 2 failing, 35 passed
PASS
96

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.container > button#trigger div.container > button#trigger

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Start Using This Icon div.wrap-icon-details > div.icon-detail-use > div.display-flex > a.button
○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
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●No form fields have multiple labels
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○`<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
○Skip links are focusable.
○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
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback