Skip to content
https://myfonts.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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
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.
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
Alt Text Quality
2 of 39 images have issues
REVIEW
2 of 39 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
11 decorative image(s) correctly marked
Info::
26 image(s) with good alt text
39 images 26 good alt text 11 decorative 2 missing
IssueCount
missing2 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

C
Form Accessibility
Action
3 of 5 controls have issues
REVIEW
3 of 5 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input name="newalbum" id="newalbum">; <input type="checkbox" name="create-new-album">; <input type="checkbox" name="tabs">
Info::
2 control(s) properly labeled
5 controls
2 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#newsletter-emailemailSubscribe to our newslettersaria-label
#tab-1checkboxAboutfor/id
#newalbuminput(none)none
create-new-albumcheckbox(none)none
tabscheckbox(none)none

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

<input name="newalbum" id="newalbum">; <input type="checkbox" name="create-new-album">; <input type="checkbox" name="tabs">

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found | MyFonts ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 82/100 — 6 failing, 28 passed
REVIEW
82

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter
Album div.item > div.name-ctas-container > div.ctas > div.searchBarWidget_filter

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.home-slick-caraousel > div.owl-nav > button.owl-prev > button.carousel-arrow div.home-slick-caraousel > div.owl-nav > button.owl-prev > button.carousel-arrow

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.container > div.accordion-wrapper > div.tab > input div.container > div.accordion-wrapper > div.tab > input

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Browse by div.gh-header__bottom-content > div.gh-menu-wrapper > ul.gh-menu > li.gh-fs-13
Categories div.gh-header__bottom-content > div.gh-menu-wrapper > ul.gh-menu > li.gh-fs-13
Blog div.gh-header__bottom-content > div.gh-menu-wrapper > ul.gh-menu > li.gh-fs-13
WhatTheFont div.gh-header__bottom-content > div.gh-menu-wrapper > ul.gh-menu > li.gh-fs-13

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Slide 1 div.home-slick-caraousel > div.owl-dots-container > div.owl-dots > button.owl-dot
Slide 2 div.home-slick-caraousel > div.owl-dots-container > div.owl-dots > button.owl-dot
Slide 3 div.home-slick-caraousel > div.owl-dots-container > div.owl-dots > button.owl-dot
Slide 4 div.home-slick-caraousel > div.owl-dots-container > div.owl-dots > button.owl-dot
Slide 5 div.home-slick-caraousel > div.owl-dots-container > div.owl-dots > button.owl-dot
Slide 6 div.home-slick-caraousel > div.owl-dots-container > div.owl-dots > button.owl-dot

These items highlight common accessibility best practices.

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
Privacy Policy. div#onetrust-policy > div.ot-desc-cntr > div#onetrust-policy-text > a.ot-cookie-policy-link
○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>`
●`[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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○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
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○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.
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

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

A+
Heading Hierarchy
4 headings
PASS
4 headings
Info::
Single H1 present
  • H6 Are you new?
  • H1 MyFonts is one of the largest font marketplaces in the world, offering professional fonts for any project.
  • H2 Over 300,000 available fonts, and counting.
  • H3 Add to Album
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 MyFonts is one of th…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Over 300,000 availab…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Add to Album21.00:13.0:1
#000000
#FFFFFF
Pass
title MyFonts | Buy and Do…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
div Learn21.00:14.5:1
#000000
#FFFFFF
Pass
a Creative Characters21.00:14.5:1
#000000
#FFFFFF
Pass
a Creative Matters21.00:14.5:1
#000000
#FFFFFF
Pass
a Font Field Guide21.00:14.5:1
#000000
#FFFFFF
Pass
a Hidden Gems21.00:14.5:1
#000000
#FFFFFF
Pass
a Fonts in Use21.00:14.5:1
#000000
#FFFFFF
Pass
a The Manual21.00:14.5:1
#000000
#FFFFFF
Pass
a Type Trends19.77:14.5:1
#000000
#F8F8F8
Pass
a fy{T}i - Typographic…19.09:14.5:1
#000000
#F4F4F4
Pass
div Memory Lane19.09:14.5:1
#000000
#F4F4F4
Pass
a Fontshop Memory Lane19.09:14.5:1
#000000
#F4F4F4
Pass
a Linotype Memory Lane19.09:14.5:1
#000000
#F4F4F4
Pass
a Fonts.com Memory Lan…19.09:14.5:1
#000000
#F4F4F4
Pass
div EUR (€)19.09:14.5:1
#000000
#F4F4F4
Pass
li USD ($)19.09:14.5:1
#000000
#F4F4F4
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.

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

Send Feedback