Skip to content
https://dafont.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
8
REVIEW
5
PASS
0
INFO
0
Checks
13
5 REVIEW 8 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
Alt Text Quality
Action
20 of 20 images have issues
FIX
20 of 20 images have issues
Critical::
20 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
13 image-in-link without alt text
An image inside a link with no alt creates an empty link.
20 images 20 missing
IssueCount
missing20 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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.
D
Lighthouse Accessibility Audits
Action
Score 58/100 — 7 failing, 11 passed
FIX
58

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
15 439 téléchargements (1 760 hier) div.container > div > div.lv2right > span.light
17 447 téléchargements (1 751 hier) div.container > div > div.lv2right > span.light
53 500 téléchargements (1 682 hier) div.container > div > div.lv2right > span.light
22 915 téléchargements (403 hier) div.container > div > div.lv2right > span.light
75 763 téléchargements (319 hier) div.container > div > div.lv2right > span.light
partners div.sd-cmp-xbcna > div.sd-cmp-VhJqD > div > strong.vendors
Do not accept div.sd-cmp-gpI1s > div.sd-cmp-Wfd7X > button.sd-cmp-7Ga7b > span.sd-cmp-j-Z5-
powered by div.sd-cmp-Wfd7X > div.sd-cmp-KebVX > a > span

These are opportunities to improve the legibility of your content.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div > a#top > img div > div > a#top > img
div.dfsmall > div.dfsmall > a > img div.dfsmall > div.dfsmall > a > img
div.dfsmall > div.dfsmall > a.tdn > img div.dfsmall > div.dfsmall > a.tdn > img
div.dfsmall > div.dfsmall > b > img div.dfsmall > div.dfsmall > b > img
div.dfsmall > div.dfsmall > a.tdn > img div.dfsmall > div.dfsmall > a.tdn > img
div.dfsmall > div.dfsmall > a.tdn > img div.dfsmall > div.dfsmall > a.tdn > img
div.dfsmall > div.dfsmall > a.tdn > img div.dfsmall > div.dfsmall > a.tdn > img
div.dfsmall > div.dfsmall > a.tdn > img div.dfsmall > div.dfsmall > a.tdn > img
div.container > div > div > img div.container > div > div > img
div.container > div > a > img div.container > div > a > img
div > div.lv1left > a.tdn > img.out div > div.lv1left > a.tdn > img.out
div > div.lv1left > a.tdn > img.out div > div.lv1left > a.tdn > img.out
div > div.lv1left > a.tdn > img.out div > div.lv1left > a.tdn > img.out
div > div.lv1left > a.tdn > img.out div > div.lv1left > a.tdn > img.out
div > div.lv1left > a.tdn > img.out div > div.lv1left > a.tdn > img.out
div.layout > div.container > div > img.fleche div.layout > div.container > div > img.fleche
div > div.dfsmall > div > img div > div.dfsmall > div > img
div > div.dfsmall > div > img div > div.dfsmall > div > img
div#width > div.tdn > div.right > img div#width > div.tdn > div.right > img
div#width > div.tdn > div > img div#width > div.tdn > div > img

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
div > div > form > input.search_form div > div > form > input.search_form

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.layout > div.container > div > iframe div.layout > div.container > div > iframe

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.container > div > div > a#top div.container > div > div > a#top
div > div.dfsmall > div.dfsmall > a div > div.dfsmall > div.dfsmall > a
div.layout > div.container > div > a div.layout > div.container > div > a
div.container > div > div.preview > a div.container > div > div.preview > a
div.container > div > div.preview > a div.container > div > div.preview > a
div.container > div > div.preview > a div.container > div > div.preview > a
div.container > div > div.preview > a div.container > div > div.preview > a
div.container > div > div.preview > a div.container > div > div.preview > a

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div > form > input.search_form div > div > form > input.search_form

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Fantaisie tr > td > div.metacat > a
Cartoon tr > td > div.catpp > a
BD, Comic tr > td > div.catpp > a
Groovy tr > td > div.catpp > a
Old School tr > td > div.catpp > a
Spirales tr > td > div.catpp > a
Western tr > td > div.catpp > a
Usé tr > td > div.catpp > a
Destructuré tr > td > div.catpp > a
Destroy tr > td > div.catpp > a
Horreur tr > td > div.catpp > a
Feu, Glace tr > td.colthemes > div.catpp > a
Déco tr > td.colthemes > div.catpp > a
Typewriter tr > td.colthemes > div.catpp > a
Rétro tr > td.colthemes > div.catpp > a
Lettrines tr > td.colthemes > div.catpp > a
Grille tr > td.colthemes > div.catpp > a
Divers tr > td.colthemes > div.catpp > a
Etranger tr > td.colthemes > div.metacat > a
Chinois, Jap. tr > td.colthemes > div.catpp > a
Arabe tr > td.colthemes > div.catpp > a
Mexicain tr > td.colthemes > div.catpp > a
Russe tr > td.colthemes > div.catpp > a
Divers tr > td.colthemes > div.catpp > a
Techno tr > td.colthemes > div.metacat > a
Carré td.colthemes > div > div.catpp > a
LCD td.colthemes > div > div.catpp > a
Divers td.colthemes > div > div.catpp > a
Bitmap td.colthemes > div > div.metacat > a
Pixel, Bitmap td.colthemes > div > div.catpp > a
Gothique tr > td.colthemes > div.metacat > a
Médiéval tr > td.colthemes > div.catpp > a
Moderne tr > td.colthemes > div.catpp > a
Celtique tr > td.colthemes > div.catpp > a
Lettrines tr > td.colthemes > div.catpp > a
Divers tr > td.colthemes > div.catpp > a
Basique tr > td.colthemes > div.metacat > a
Sans serif tr > td.colthemes > div.catpp > a
Serif tr > td.colthemes > div.catpp > a
Largeur fixe tr > td.colthemes > div.catpp > a
Divers tr > td.colthemes > div.catpp > a
Script tr > td.colthemes > div.metacat > a
Calligraphie tr > td.colthemes > div.catpp > a
Scolaire tr > td.colthemes > div.catpp > a
Manuscrit tr > td.colthemes > div.catpp > a
Brush tr > td.colthemes > div.catpp > a
Trash tr > td.colthemes > div.catpp > a
Graffiti tr > td.colthemes > div.catpp > a
Old School tr > td.colthemes > div.catpp > a
Divers tr > td.colthemes > div.catpp > a
Symboles tr > td.colthemes > div.metacat > a
Alien tr > td.colthemes > div.catpp > a
Animaux tr > td.colthemes > div.catpp > a
Asiatique tr > td.colthemes > div.catpp > a
Ancien tr > td.colthemes > div.catpp > a
Esotérique tr > td.colthemes > div.catpp > a
Fantastique tr > td.colthemes > div.catpp > a
Horreur tr > td.colthemes > div.catpp > a
Jeux tr > td.colthemes > div.catpp > a
Formes tr > td.colthemes > div.catpp > a
Codes barres tr > td.colthemes > div.catpp > a
Nature tr > td.colthemes > div.catpp > a
Sport tr > td.colthemes > div.catpp > a
Têtes tr > td.colthemes > div.catpp > a
Enfants tr > td.colthemes > div.catpp > a
TV, Cinéma tr > td.colthemes > div.catpp > a
Logos tr > td.colthemes > div.catpp > a
Sexy tr > td.colthemes > div.catpp > a
Armée tr > td.colthemes > div.catpp > a
Musique tr > td.colthemes > div.catpp > a
Divers tr > td.colthemes > div.catpp > a
Fêtes tr > td.colthemes > div.metacat > a
St Valentin tr > td.colthemes > div.catpp > a
Pâques tr > td.colthemes > div.catpp > a
Halloween tr > td.colthemes > div.catpp > a
Noël tr > td.colthemes > div.catpp > a
Divers tr > td.colthemes > div.catpp > a

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-hidden="true"]` is not present on the document `<body>`
●Buttons have an accessible name
●Input buttons have discernible text.
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○Heading elements appear in a sequentially-descending order
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<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.
○Elements with visible text labels have matching accessible names.
○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.
B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="q">; <input type="submit">
2 controls
0 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
qtext(none)none
inputsubmit(none)none

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

<input type="text" name="q">; <input type="submit">

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

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 Error 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
title DaFont - Polices à télécharger
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
a English
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
b Français
2.45:1
#000000
on
#4C4C4C
needs 3.0:1 (large text)
16px · top of page (header area)
a Español
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Deutsch
2.45:1
#000000
on
#4C4C4C
needs 4.5:1 (normal text)
16px · above the fold
a Italiano
1.61:1
#000000
on
#313131
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Português
2.41:1
#000000
on
#4B4B4B
needs 4.5:1 (normal text)
16px · above the fold
a Mon compte
2.41:1
#000000
on
#4B4B4B
needs 4.5:1 (normal text)
16px · above the fold
a Inscription
1.52:1
#000000
on
#2D2D2D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Thèmes
2.41:1
#000000
on
#4B4B4B
needs 4.5:1 (normal text)
16px · above the fold
a Nouveautés
1.50:1
#000000
on
#432323
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Auteurs
2.41:1
#000000
on
#4B4B4B
needs 4.5:1 (normal text)
16px · above the fold
a Top
2.41:1
#000000
on
#4B4B4B
needs 4.5:1 (normal text)
16px · above the fold
a Forum
1.74:1
#000000
on
#363636
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a FAQ
2.41:1
#000000
on
#4B4B4B
needs 4.5:1 (normal text)
16px · mid-page
a Proposer une police
1.44:1
#000000
on
#421E1E
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Logiciels
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Fantaisie
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Cartoon
2.41:1
#000000
on
#4B4B4B
needs 4.5:1 (normal text)
16px · mid-page
a BD, Comic
1.44:1
#000000
on
#431E1E
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

7 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)
ElementRatioRequiredFGBGResult
title DaFont - Polices à …2.45:14.5:1
#000000
#4C4C4C
Fail
a English2.45:14.5:1
#000000
#4C4C4C
Fail
b Français2.45:13.0:1
#000000
#4C4C4C
Fail
a Español2.45:14.5:1
#000000
#4C4C4C
Fail
a Deutsch2.45:14.5:1
#000000
#4C4C4C
Fail
a Italiano1.61:14.5:1
#000000
#313131
Fail
a Português2.41:14.5:1
#000000
#4B4B4B
Fail
a Mon compte2.41:14.5:1
#000000
#4B4B4B
Fail
a Inscription1.52:14.5:1
#000000
#2D2D2D
Fail
a Thèmes2.41:14.5:1
#000000
#4B4B4B
Fail
a Nouveautés1.50:14.5:1
#000000
#432323
Fail
a Auteurs2.41:14.5:1
#000000
#4B4B4B
Fail
a Top2.41:14.5:1
#000000
#4B4B4B
Fail
a Forum1.74:14.5:1
#000000
#363636
Fail
a FAQ2.41:14.5:1
#000000
#4B4B4B
Fail
a Proposer une police1.44:14.5:1
#000000
#421E1E
Fail
a Logiciels1.26:14.5:1
#000000
#1E1E1E
Fail
a Fantaisie1.00:14.5:1
#000000
#000000
Fail
a Cartoon2.41:14.5:1
#000000
#4B4B4B
Fail
a BD, Comic1.44:14.5:1
#000000
#431E1E
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback