Skip to content
https://jalbum.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Heading Hierarchy
Action
54 headings, 4 skip(s)
FIX
54 headings, 4 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Back
  • H5 Back
  • H5 Back
  • H5 Back
  • H5 Back
  • H5 Back
  • H5 Back
  • H1 Free Photo Gallery Software for Any Website
  • H3 The jAlbum desktop application creates photo album websites from your images skipped
  • H4 A few samples
  • H2 License + Storage
  • H3 Premium
  • H3 Purchase storage with license
  • H3 Create new account
  • H3 You already have storage!
  • H3 Power
  • H3 Purchase storage with license
  • H3 Create new account
  • H3 You already have storage!
  • H3 Super
  • H3 Purchase storage with license
  • H3 Create new account
  • H3 You already have storage!
  • H2 License (without storage)
  • H3 Free
  • H3 Standard
  • H3 Pro
  • H2 Why use jAlbum?
  • H4 Integrity skipped
  • H4 Convenience
  • H4 Safety
  • H4 Ease of use
  • H4 Diversity
  • H4 Trust
  • H2 AVIF image format support
  • H2 Features
  • H4 Gallery maker skipped
  • H4 Image editor
  • H4 Image organizer
  • H4 Uploader
  • H2 Quotes
  • H2 Popular uses
  • H4 Photographers skipped
  • H4 Organizations
  • H4 Families
  • H5 Curious? Try jAlbum for free!
  • H5 About jAlbum
  • H5 Products
  • H5 Get in touch
  • H5 Contribute
  • H5 Preferences
  • H5 Payment options
  • H3 We are using cookies
  • H4 Storage for Accounts

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

F
Alt Text Quality
Action
17 of 62 images have issues
FIX
17 of 62 images have issues
Critical::
17 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
16 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
17 decorative image(s) correctly marked
Info::
28 image(s) with good alt text
62 images 28 good alt text 17 decorative 17 missing
IssueCount
missing17 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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
9 landmarks
REVIEW
9 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 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

C
Form Accessibility
Action
16 of 16 controls have issues
REVIEW
16 of 16 controls have issues
Critical::
16 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:name" id="id1c">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:username" id="id1e">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:email" id="id20">; <input type="password" name="signInOrUpPanel:signUpBox:signUpForm:password" id="id22">; <input type="checkbox" name="signInOrUpPanel:signUpBox:signUpForm:agreeToTerms" id="id24">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:name" id="id2d">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:username" id="id2f">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:email" id="id31">; <input type="password" name="signInOrUpPanel:signUpBox:signUpForm:password" id="id33">; <input type="checkbox" name="signInOrUpPanel:signUpBox:signUpForm:agreeToTerms" id="id35"> (+6 more)
16 controls
0 labeled
0 placeholder only
16 unlabeled
ControlTypeLabelMethod
#id1ctext(none)none
#id1etext(none)none
#id20text(none)none
#id22password(none)none
#id24checkbox(none)none
#id2dtext(none)none
#id2ftext(none)none
#id31text(none)none
#id33password(none)none
#id35checkbox(none)none
#id3etext(none)none
#id40text(none)none
#id42text(none)none
#id44password(none)none
#id46checkbox(none)none
agreecheckbox(none)none

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

<input type="text" name="signInOrUpPanel:signUpBox:signUpForm:name" id="id1c">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:username" id="id1e">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:email" id="id20">; <input type="password" name="signInOrUpPanel:signUpBox:signUpForm:password" id="id22">; <input type="checkbox" name="signInOrUpPanel:signUpBox:signUpForm:agreeToTerms" id="id24">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:name" id="id2d">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:username" id="id2f">; <input type="text" name="signInOrUpPanel:signUpBox:signUpForm:email" id="id31">; <input type="password" name="signInOrUpPanel:signUpBox:signUpForm:password" id="id33">; <input type="checkbox" name="signInOrUpPanel:signUpBox:signUpForm:agreeToTerms" id="id35"> (+6 more)

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 73/100 — 8 failing, 22 passed
REVIEW
73

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
Check out our offers! div#prices > div.medium-4 > p.small-text-center > a#prices-btn
over 120 million galleries div.why-use > div > p > a
4.7/5 in TrustPilot div.why-use > div > p > a
Read more about this exciting image format in our blog! div.row > div.medium-6 > p.medium-text-left > a.small
DigitalFoto div.medium-6 > small > em > a
DigitalFoto div.row > div.medium-6 > p > a.readmore
jAlbum div.medium-6 > small > em > a
Read an interesting interview with me! div.row > div.medium-6 > p > a
Customer reviews div.row > div.columns > p > a.readmore
Photographers div.row > div.medium-4 > h4.pull-up > a
Read more about portfolios div.row > div.medium-4 > p > a.readmore
iOS div.row > div.large-12 > p.mobile > a
Android div.row > div.large-12 > p.mobile > a
on the GDPR-page form#id4d > p > small > a
OK, close body.fullwidth > div.agreeSocialTrackingBox > div.buttons > a#id4e

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
over 120 million galleries div.why-use > div > p > a
4.7/5 in TrustPilot div.why-use > div > p > a
iOS div.row > div.large-12 > p.mobile > a
Android div.row > div.large-12 > p.mobile > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
The jAlbum desktop application creates photo album websites from your images div.main-content > div.row > div.large-4 > h3.text-center
Integrity div.medium-12 > div.why-use > div > h4
Gallery maker div.main-content > div.row > div.large-3 > h4.medium-text-left
Photographers div.main-content > div.row > div.medium-4 > h4.pull-up

These are opportunities to improve keyboard navigation in your application.

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.carousel > div > a > img div.carousel > div > a > img
div.row > div.large-8 > a > img div.row > div.large-8 > a > img
div.medium-4 > div > a > img div.medium-4 > div > a > img
div.why-use > div > div.picto > img div.why-use > div > div.picto > img
div.medium-5 > p.medium-text-right > a > img div.medium-5 > p.medium-text-right > a > img
div.row > div.large-7 > a > img div.row > div.large-7 > a > img
div.row > div.large-7 > a > img div.row > div.large-7 > a > img
div.row > div.large-6 > a > img div.row > div.large-6 > a > img
div.row > div.large-6 > a > img div.row > div.large-6 > a > img
tr > td > a > img tr > td > a > 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.agreeSocialTrackingBox > form#id4d > p > input div.agreeSocialTrackingBox > form#id4d > p > input

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
nav.top-bar > ul.title-area > li.toggle-topbar > a nav.top-bar > ul.title-area > li.toggle-topbar > a
div.large-8 > div.carousel > div > a div.large-8 > div.carousel > div > a
div.main-content > div.row > div.large-8 > a div.main-content > div.row > div.large-8 > a
div.row > div.medium-4 > div > a div.row > div.medium-4 > div > a
div.row > div.medium-4 > div > a div.row > div.medium-4 > div > a
div.row > div.medium-4 > div > a div.row > div.medium-4 > div > a
div.row > div.medium-5 > p.medium-text-right > a div.row > div.medium-5 > p.medium-text-right > a
div.main-content > div.row > div.large-7 > a div.main-content > div.row > div.large-7 > a
div.main-content > div.row > div.large-7 > a div.main-content > div.row > div.large-7 > a
div.main-content > div.row > div.large-6 > a div.main-content > div.row > div.large-6 > a
div.main-content > div.row > div.large-6 > a div.main-content > div.row > div.large-6 > a
div.medium-4 > div.carousel > div > a div.medium-4 > div.carousel > div > a
div.medium-4 > div.carousel > div > a div.medium-4 > div.carousel > div > a
div.medium-4 > div.carousel > div > a div.medium-4 > div.carousel > div > a
tbody > tr > td > a tbody > tr > td > a
tbody > tr > td > a.tip-top tbody > tr > td > a.tip-top

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.

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
This is jAlbum div.large-8 > div.toc5 > p > a
Contact us div.large-8 > div.toc5 > p > a
The team div.large-8 > div.toc5 > p > a
Blog div.large-8 > div.toc5 > p > a
Awards div.large-8 > div.toc5 > p > a.last
Online jAlbum div.large-8 > div.toc5 > p > a
jAlbum for Android div.large-8 > div.toc5 > p > a
jAlbum for iOS div.large-8 > div.toc5 > p > a
Photo book div.large-8 > div.toc5 > p > a
Contact us div.large-8 > div.toc5 > p > a
Forum div.large-8 > div.toc5 > p > a
Advertisers div.large-8 > div.toc5 > p > a
Press div.large-8 > div.toc5 > p > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`[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
●Elements use only permitted ARIA attributes
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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 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
○Buttons have an accessible name
○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
○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.
○No element has a `[tabindex]` value greater than 0
○`<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
○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.
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 Free Photo Gallery S…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 License + Storage19.09:13.0:1
#000000
#F4F4F4
Pass
h2 License (without sto…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Why use jAlbum?19.09:13.0:1
#000000
#F4F4F4
Pass
h2 AVIF image format su…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Features19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Quotes19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Popular uses19.09:13.0:1
#000000
#F4F4F4
Pass
h3 The jAlbum desktop a…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Premium19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Purchase storage wit…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Create new account19.09:13.0:1
#000000
#F4F4F4
Pass
h3 You already have sto…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Power19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Purchase storage wit…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Create new account19.09:13.0:1
#000000
#F4F4F4
Pass
h3 You already have sto…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Super19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Purchase storage wit…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Create new account19.09:13.0: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