Skip to content
https://www.crowdin.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
2
REVIEW
6
PASS
5
INFO
0
Checks
13
5 PASS 6 REVIEW 2 FIX
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::
2 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 2 <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
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 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

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
Form Accessibility
6 of 6 controls have issues
REVIEW
6 of 6 controls have issues
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">
6 controls
0 labeled
6 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(Search app or integration...)placeholder only
inputtext(Search app or integration...)placeholder only
inputtext(Search app or integration...)placeholder only
inputtext(Search app or integration...)placeholder only
inputtext(Search app or integration...)placeholder only
inputtext(Search app or integration...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 24 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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GitHub div.bg-white > div.flex > div.flex > div.w-8
GitLab div.bg-white > div.flex > div.flex > div.w-8
Bitbucket div.bg-white > div.flex > div.flex > div.w-8
Figma div.bg-white > div.flex > div.flex > div.w-8

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.bg-gradient-to-br > div.bg-background > div.flex > button.p-1.5 div.bg-gradient-to-br > div.bg-background > div.flex > button.p-1.5
div.col-span-12 > astro-island > div.flex > button div.col-span-12 > astro-island > div.flex > button
div.col-span-12 > astro-island > div.flex > button div.col-span-12 > astro-island > div.flex > button
div.col-span-12 > astro-island > div.flex > button div.col-span-12 > astro-island > div.flex > button
div.flex > astro-island > div.flex > button div.flex > astro-island > div.flex > button
div.flex > astro-island > div.flex > button div.flex > astro-island > div.flex > button
div.flex > astro-island > div.flex > button div.flex > astro-island > div.flex > button

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.grid > div.flex > a div.container > div.grid > div.flex > 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.

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
* Crowdin.com UI section#screenshots > div.container > div.bg-purple-200 > p.text-xs
With Crowdin div.container > div.grid > div.bg-primary > div.inline-block
Small Business div.bg-purple-200 > div.transition-opacity > div.text-center > p.text-muted-foreground

These are opportunities to improve the legibility of your content.

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
Go to slide 3 div.relative > div.flex > div.flex > button.h-2
Go to slide 4 div.relative > div.flex > div.flex > button.h-2
Go to slide 5 div.relative > div.flex > div.flex > button.h-2
Go to slide 6 div.relative > div.flex > div.flex > button.h-2

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
●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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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
○`<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
○Links are distinguishable without relying on color.
○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.
○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+
Heading Hierarchy
35 headings
PASS
35 headings
Info::
Single H1 present
  • H1 Localization that just works
  • H2 Localize any type of your content with Crowdin
  • H2 Why old localization fails compared to modern solutions
  • H3 Translation without a system is a real nightmare
  • H4 No context
  • H4 Out-of-Sync content
  • H4 Communication challenges
  • H4 Scattered Data
  • H3 Localization done right
  • H4 AI-Powered automation
  • H4 Contextual translation
  • H4 Scales with you
  • H4 Real-Time collaboration
  • H2 Real feedback. Real impact.
  • H3 "Seamless Integration, Fast Support, and All-in-One Functionality"
  • H2 Crowdin fits seamlessly into your development workflow
  • H3 Upload source content
  • H3 Add context
  • H3 Pre-translate texts
  • H3 Quality assurance
  • H3 Deployment
  • H3 Continuous localization
  • H2 Connect, automate, and localize with Crowdin localization platform
  • H3 Crowdin store: 700+ apps and integrations
  • H3 AI translation suite for localization teams
  • H2 Powerful features for every team size
  • H2 Ready to go international?
  • H2 Choose the right Crowdin for your product's localization
  • H2 Security is at the heart of everything we build
  • H3 Product Security
  • H3 Company Security
  • H3 Workflow Security
  • H2 Why companies choose Crowdin?
  • H2 Recognized by industry leaders
  • H2 Make your whole company multilingual
A+
Alt Text Quality
All 36 images OK
PASS
All 36 images OK
Info::
36 image(s) with good alt text
36 images 36 good alt text
All images have appropriate alt text.
A
Favicon & Branding
8 icon(s) detected
PASS
8 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: Crowdin
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Crowdin ✓192×192 icon ✓512×512 icon ✓Start URL /profile ✓Display Mode standalone ✓
Name Crowdin Display Mode standalone Theme Color #263238 Background Color #263238 Icons 5 icon(s)
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
h2 Why old localization…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ready to go internat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recognized by indust…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Make your whole comp…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Translation without …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Localization done ri…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Seamless Integration…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Upload source conten…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Add context21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pre-translate texts21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Quality assurance21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Deployment21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Continuous localizat…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI translation suite…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product Security21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Company Security21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Workflow Security21.00:13.0:1
#000000
#FFFFFF
Pass
title Crowdin: Localizatio…21.00:14.5:1
#000000
#FFFFFF
Pass
button Product21.00:14.5:1
#000000
#FFFFFF
Pass
button Solutions21.00:14.5:1
#000000
#FFFFFF
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