Skip to content
https://huaweicloud.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
38
GRADE
F
FIX
10
REVIEW
2
PASS
1
INFO
0
Checks
13
1 PASS 2 REVIEW 10 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

D
Heading Hierarchy
Action
102 headings, 2 skip(s)
FIX
102 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Huawei Cloud MaaS Available Globally
  • H5 MaaS Available Globally
  • H5 HUAWEI CLOUD INSPIRE 2026
  • H5 HUAWEI CLOUD INSPIRE 2026
  • H5 New Releases
  • H5 New Releases
  • H5 Huawei Cloud Flexus
  • H5 Huawei Cloud Flexus
  • H5 GaussDB
  • H5 GaussDB
  • H5 Huawei Cloud Flexus
  • H5 Object Storage Service (OBS)
  • H5 Elastic Cloud Server (ECS)
  • H5 ROMA Connect
  • H5 Cloud Backup and Recovery (CBR)
  • H5 GeminiDB
  • H5 Content Delivery Network (CDN)
  • H5 FunctionGraph
  • H5 Elastic Cloud Server (ECS)
  • H5 Bare Metal Server (BMS)
  • H5 Huawei Cloud Flexus
  • H5 Auto Scaling
  • H5 Image Management Service (IMS)
  • H5 FunctionGraph
  • H5 Dedicated Computing Cluster (DCC)
  • H5 GPU Accelerated Cloud Server (GACS)
  • H5 Object Storage Service (OBS)
  • H5 Business Recovery Service (BRS)
  • H5 Elastic Volume Service (EVS)
  • H5 Cloud Backup and Recovery (CBR)
  • H5 Scalable File Service (SFS)
  • H5 Data Express Service (DES)
  • H5 Dedicated Distributed Storage Service (DSS)
  • H5 Cloud Server Backup Service (CSBS)
  • H5 Virtual Private Cloud (VPC)
  • H5 Virtual Private Network (VPN)
  • H5 Cloud Connect
  • H5 Elastic IP (EIP)
  • H5 Elastic Load Balance (ELB)
  • H5 NAT Gateway
  • H5 Direct Connect
  • H5 Enterprise Switch (ESW)
  • H5 TaurusDB
  • H5 RDS for MySQL
  • H5 RDS for PostgreSQL
  • H5 GaussDB
  • H5 GeminiDB
  • H5 Distributed Cache Service (DCS)
  • H5 Document Database Service (DDS)
  • H5 Data Replication Service (DRS)
  • H5 ModelArts
  • H5 Optical Character Recognition (OCR)
  • H5 Huawei HiLens (HiLens)
  • H5 Content Moderation
  • H5 Short Sentence Recognition
  • H5 Image Recognition
  • H5 Graph Engine Service (GES)
  • H5 EIHealth
  • H5 MapReduce Service (MRS)
  • H5 Cloud Search Service (CSS)
  • H5 DataArts Studio
  • H5 Data Lake Insight (DLI)
  • H5 Data Warehouse Service (DWS)
  • H5 Data Lake Visualization (DLV)
  • H5 Cloud Stream Service (CS)
  • H5 Data Ingestion Service (DIS)
  • H5 Host Security Service (HSS)
  • H5 Web Application Firewall (WAF)
  • H5 Anti-DDoS Service (AAD)
  • H5 Data Encryption Workshop (DEW)
  • H5 Data Security Center (DSC)
  • H5 Database Security Service (DBSS)
  • H5 Cloud Firewall (CFW)
  • H5 Cloud Bastion Host (CBH)
  • H5 Cloud Service Engine (CSE)
  • H5 Distributed Cache Service (DCS) for Redis®
  • H5 Distributed Cache Service (DCS) for Memcached
  • H5 Distributed Message Service (DMS)
  • H5 Distributed Message Service (DMS) for Kafka
  • H5 API Gateway (APIG)
  • H5 Huawei Cloud Flexus
  • H5 Object Storage Service (OBS)
  • H5 Elastic Cloud Server (ECS)
  • H5 ROMA Connect
  • H5 Cloud Backup and Recovery (CBR)
  • H5 GeminiDB
  • H5 Content Delivery Network (CDN)
  • H5 FunctionGraph
  • H3 E-Commerce
  • H3 Automotive
  • H3 Insurance
  • H3 Media & Entertainment
  • H3 Gaming
  • H3 Smart City
  • H5 Developer Institute skipped
  • H5 Developer Events
  • H5 Developer Forum
  • H3 See How Customers Are Innovating with Us
  • H3 See How Customers Are Innovating with Us
  • H5 Professional Services skipped
  • H5 Contact Sales
  • H5 After-Sales Support

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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
100 of 101 images have issues
FIX
100 of 101 images have issues
Critical::
100 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
98 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with good alt text
101 images 1 good alt text 100 missing
IssueCount
missing100 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::
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 67/100 — 5 failing, 10 passed
FIX
67

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.

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
Professional Services li.home-consultation-card > a > div.home-consultation-content > h5

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
ul.product-m-list > li > a.product-m-card > img ul.product-m-list > li > a.product-m-card > img
ul.product-m-list > li > a.product-m-card > img ul.product-m-list > li > a.product-m-card > img
ul.product-m-list > li > a.product-m-card > img ul.product-m-list > li > a.product-m-card > img
ul.product-m-list > li > a.product-m-card > img ul.product-m-list > li > a.product-m-card > img
ul.product-m-list > li > a.product-m-card > img ul.product-m-list > li > a.product-m-card > img
ul.product-m-list > li > a.product-m-card > img ul.product-m-list > li > a.product-m-card > img
div.por-container > div.section-body > div.information-frontground-m > img.lazyload div.por-container > div.section-body > div.information-frontground-m > img.lazyload
div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload
div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload
div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload
div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload
div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload
div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload
div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload
div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload div.section-body > div.customers-m-logos > a.customers-m-logo > img.lazyload
ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon
ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon
ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon
ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon
ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon
ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon ul.safety-card-list > li.safety-card-item > a.safety-card > img.safety-card-icon
ul.por-container > li.home-consultation-card > a > img.lazyload ul.por-container > li.home-consultation-card > a > img.lazyload
ul.por-container > li.home-consultation-card > a > img.lazyload ul.por-container > li.home-consultation-card > a > img.lazyload
ul.por-container > li.home-consultation-card > a > img.lazyload ul.por-container > li.home-consultation-card > a > img.lazyload

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.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo
div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo
div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo
div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo
div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo
div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo
div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo
div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo div.por-container > div.section-body > div.customers-m-logos > a.customers-m-logo
div.footer-nav-left > ul.footer-nav-icons > li > a.footer-link div.footer-nav-left > ul.footer-nav-icons > li > a.footer-link
div.footer-nav-left > ul.footer-nav-icons > li > a.footer-link div.footer-nav-left > ul.footer-nav-icons > li > a.footer-link
div.footer-nav-left > ul.footer-nav-icons > li > a.footer-link div.footer-nav-left > ul.footer-nav-icons > li > a.footer-link

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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.phone html.phone

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>`
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●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
○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
○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.
○No element has a `[tabindex]` value greater than 0
○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.
○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.
C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 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" id="header-navigation-search-input">; <input type="text">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
3 controls
0 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
inputtext(搜索)placeholder only
#header-navigation-search-inputtext(none)none
inputtext(none)none

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

<input type="text" id="header-navigation-search-input">; <input type="text">

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

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

<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

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 404页面_华为云 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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
h3 E-Commerce21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Automotive21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Insurance21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Media & Entertainmen…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gaming21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Smart City21.00:13.0:1
#000000
#FFFFFF
Pass
h3 See How Customers Ar…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 See How Customers Ar…21.00:13.0:1
#000000
#FFFFFF
Pass
title Huawei Cloud - The A…21.00:14.5:1
#000000
#FFFFFF
Pass
p 检测到您已登…21.00:14.5:1
#000000
#FFFFFF
Pass
a https://www.huaweicl…21.00:14.5:1
#000000
#FFFFFF
Pass
p 不再显示此消…21.00:14.5:1
#000000
#FFFFFF
Pass
span Intl-English21.00:14.5:1
#000000
#FFFFFF
Pass
div International21.00:14.5:1
#000000
#FFFFFF
Pass
a English21.00:14.5:1
#000000
#FFFFFF
Pass
a Bahasa Indonesia21.00:14.5:1
#000000
#FFFFFF
Pass
a Español21.00:14.5:1
#000000
#FFFFFF
Pass
a Português21.00:14.5:1
#000000
#FFFFFF
Pass
a Türkçe21.00:14.5:1
#000000
#FFFFFF
Pass
a عربي21.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