Skip to content
https://preply.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 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
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 MAIN (missing!) CONTENTINFO footer

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

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: #ffffff
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA 12 pass AA only
title Preply: Learn with the best online langu…
1.12:1
#000000
on
#121215
needs 4.5:1 (normal text)
16px · top of page (header area)
p Preply stands with Ukraine and its peopl…
1.12:1
#000000
on
#121215
needs 4.5:1 (normal text)
16px · top of page (header area)
a Join us
2.68:1
#000000
on
#7A3F58
needs 4.5:1 (normal text)
16px · top of page (header area)
p Log In
2.68:1
#000000
on
#7A3F58
needs 4.5:1 (normal text)
16px · top of page (header area)
span Home
2.68:1
#000000
on
#7A3F58
needs 4.5:1 (normal text)
16px · above the fold
span Find tutors
2.68:1
#000000
on
#7A3F58
needs 4.5:1 (normal text)
16px · above the fold
span For business
2.68:1
#000000
on
#7A3F58
needs 4.5:1 (normal text)
16px · above the fold
span Proven Progress
2.68:1
#000000
on
#7A3F58
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Learn faster4.32:13.0:1
#000000
#717174
Pass
h1 with your best4.32:13.0:1
#000000
#717174
Pass
h1 language tutor.4.32:13.0:1
#000000
#717174
Pass
h2 Progress starts with…4.32:13.0:1
#000000
#717174
Pass
h2 How Preply works:4.32:13.0:1
#000000
#717174
Pass
h2 Lessons you’ll lov…4.32:13.0:1
#000000
#717174
Pass
h2 Become a tutor4.32:13.0:1
#000000
#717174
Pass
h3 Find your tutor.4.32:13.0:1
#000000
#717174
Pass
h3 Start learning.4.32:13.0:1
#000000
#717174
Pass
h3 Make progress every …4.32:13.0:1
#000000
#717174
Pass
h3 Online tutoring & La…4.32:13.0:1
#000000
#717174
Pass
h3 Find a language tuto…4.32:13.0:1
#000000
#717174
Pass
title Preply: Learn with t…1.12:14.5:1
#000000
#121215
Fail
p Preply stands with U…1.12:14.5:1
#000000
#121215
Fail
a Join us2.68:14.5:1
#000000
#7A3F58
Fail
p Log In2.68:14.5:1
#000000
#7A3F58
Fail
span Home2.68:14.5:1
#000000
#7A3F58
Fail
span Find tutors2.68:14.5:1
#000000
#7A3F58
Fail
span For business2.68:14.5:1
#000000
#7A3F58
Fail
span Proven Progress2.68:14.5:1
#000000
#7A3F58
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.

A+
Heading Hierarchy
31 headings
PASS
31 headings
Info::
Single H1 present
  • H1 Learn faster with your best language tutor.
  • H2 Progress starts with the right tutor
  • H3 97% of learners say practicing with a real person is very important to their progress.
  • H2 How Preply works:
  • H3 Find your tutor.
  • H3 Start learning.
  • H3 Make progress every week.
  • H2 Lessons you’ll love. Guaranteed.
  • H2 Become a tutor
  • H3 Online tutoring & Language lessons and classes
  • H4 Popular online language courses
  • H4 Learn a language online
  • H4 Tutors for different learning needs
  • H4 Other popular courses
  • H4 Popular online courses by level
  • H3 Find a language tutor near you
  • H4 Tutors from top cities around the globe
  • H4 Tutors from English speaking countries around the globe
  • H4 Preply global
  • H5 ABOUT US
  • H5 FOR STUDENTS
  • H5 FOR TUTORS
  • H5 FOR COMPANIES
  • H5 Support
  • H5 Contacts
  • H5 Preply social
  • H5 Apps
  • H5 LEARN
  • H5 ONLINE LANGUAGE CLASSES AND COURSES
  • H5 1-ON-1 TUTORS
  • H5 TUTORS NEAR YOU
A
Alt Text Quality
1 of 32 images have issues
PASS
1 of 32 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
30 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
32 images 1 good alt text 30 decorative 1 missing
IssueCount
missing1 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

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Preply
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Preply ✓192×192 icon ✓512×512 icon ✓Start URL ./ ✓Display Mode standalone ✓
Name Preply Display Mode standalone Icons 2 icon(s)
A+
Lighthouse Accessibility Audits
Score 95/100 — 1 failing, 26 passed
PASS
95

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.LayoutGap__FdLKD > div.styles_storeButtons__tXLiq > div.LayoutGap__FdLKD > button div.LayoutGap__FdLKD > div.styles_storeButtons__tXLiq > div.LayoutGap__FdLKD > button
div.styles_FooterInner__93q_C > section#footer_app_badges > div.styles_MenuList__sCQYV > button div.styles_FooterInner__93q_C > section#footer_app_badges > div.styles_MenuList__sCQYV > button

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.

○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
●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.
●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
●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>`).
●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
●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
○Form elements have associated labels
○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.
○Uses ARIA roles only on compatible elements
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback