Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 5 REVIEW 4 FIX

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

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

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

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

Alt Text Quality

2 of 190 images have issues

REVIEW

2 of 190 images have issues

2 image(s) with generic alt text

6 image(s) with alt text over 125 characters

182 image(s) with good alt text

190 images 182 good alt text 2 generic

Issue	Count
generic	2 image(s)
too long	6 image(s)

Mobile-Readable Font Sizes

94% of visible text renders at >= 12 CSS px (7 below threshold)

REVIEW

94% of visible text renders at >= 12 CSS px (7 below threshold)

7 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 8.0px ("API"); <div> 11.0px ("Email"); <div> 11.0px ("Hotline"); <p> 11.0px ("©2026 EASY AI TECHNOLOGY SOLUTIONS COMPA..."); <a> 11.0px ("hello@geteasy.ai").

Favicon & Branding

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

A+

Heading Hierarchy

71 headings

PASS

71 headings

Single H1 present

H3 Revenue AI OS (Revenue AI Operating System): AI Infrastructure for Revenue Growth
H3 Revenue AI OS (Revenue AI Operating System): AI Infrastructure for Revenue Growth
H1 Revenue AI OSfor business growthRetail & E-commerce
H2 Top companieshave successfully deployed AI succeeding
H2 Real-world Deployment Projects
H2 Revenue AI OS for intelligent business operations
H3 AI Customer Care Assistant
H3 AI Sales Conversion Assistant
H3 AI Experience Personalization Assistant
H3 AI Reporting & Analytics Assistant
H3 AI Customer Care Assistant
H3 AI Sales Conversion Assistant
H3 AI Experience Personalization Assistant
H3 AI Reporting and Analytics Assistant
H2 Powerful AI features for Sales and Customer Service
H3 AI Chatbot & Livechat
H4 Omnichannel AI Chatbot
H4 Livechat switching between AI and agents
H4 Multimedia interactive chat
H4 AI selling directly in conversation
H3 Ticket & Conversation Management System
H4 Centralized conversation management & organization
H4 AI-assisted conversation classification & analysis
H4 Ticket management & assignment
H4 Auto lead extraction from conversations
H3 Customer Data Platform (CDP)
H4 Consolidate & standardize customer data
H4 AI-assisted multi-source data collection & sync
H4 AI segment & behavioral analytics
H4 Data for automated AI personalization
H3 Marketing Automation
H4 AI-automated sales and marketing scenarios
H4 Content personalization by customer groups
H4 Right-time, right-context campaign triggers
H4 Optimize conversion and marketing costs
H3 Analytics, Reporting & Prediction
H4 Overall performance tracking dashboard
H4 Customer journey & conversion funnel
H4 Customer experience and service efficiency
H4 Business reporting & recommended actions
H3 AI Chatbot & Livechat
H4 Omnichannel AI Chatbot
H4 Livechat switching between AI and agents
H4 Multimedia interactive chat
H4 AI selling directly in conversation
H3 Ticket & Conversation Management System
H4 Centralized conversation management & organization
H4 AI-assisted conversation classification & analysis
H4 Ticket management & assignment
H4 Auto lead extraction from conversations
H3 Customer Data Platform (CDP)
H4 Consolidate & standardize customer data
H4 AI-assisted multi-source data collection & sync
H4 AI segment & behavioral analytics
H4 Data for automated AI personalization
H3 Marketing Automation
H4 AI-automated sales and marketing scenarios
H4 Content personalization by customer groups
H4 Right-time, right-context campaign triggers
H4 Optimize conversion and marketing costs
H3 Analytics, Reporting & Prediction
H4 Overall performance tracking dashboard
H4 Customer journey & conversion funnel
H4 Customer experience and service efficiency
H4 Business reporting & recommended actions
H2 Distinct data processing mechanism, superior response quality
H2 Tokens used for CS & Sales each month
H2 Certified by leading prestigious organizations
H2 Latest Posts
H3 Revenue AI OS (Revenue AI Operating System): AI Infrastructure for Revenue Growth
H3 Dien may XANH's IPO and the Value of Investing Ahead of the Curve

A+

Heading Text Quality

All 71 heading(s) have substantive, well-formed text

PASS

All 71 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

77 links, 19 buttons — all OK

PASS

77 links, 19 buttons — all OK

6 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.linkedin.com/company/easyai-ltd; https://zalo.me/0977626065; https://www.facebook.com/easyai.ltd/; https://www.youtube.com/@geteasyai; https://www.tiktok.com/@geteasy.ai; /en/cookie-policy

71 link(s) with descriptive text

77 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.linkedin.com/company/easyai-…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://zalo.me/0977626065	Zalo	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/easyai.ltd/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@geteasyai	YouTube	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@geteasy.ai	TikTok	new tab	Add '(opens in new tab)' to text
/en/cookie-policy	Cookie Policy	new tab	Add '(opens in new tab)' to text

90 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.linkedin.com/company/easyai-ltd; https://zalo.me/0977626065; https://www.facebook.com/easyai.ltd/; https://www.youtube.com/@geteasyai; https://www.tiktok.com/@geteasy.ai; /en/cookie-policy

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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)

Element	Ratio	Required	FG	BG	Result
h2 Real-world Deploymen…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Revenue AI OS for in…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Powerful AI features…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Distinct data proces…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Tokens used for CS &…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 by leading prestigi…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Latest Posts	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 Revenue AI OS (Reven…	18.56:1	3.0:1	#000000	#F5EFF6	Pass
h3 Revenue AI OS (Reven…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 AI Customer Care Ass…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 AI Sales Conversion …	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 AI Experience Person…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 AI Reporting & Analy…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 AI Customer Care Ass…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 AI Sales Conversion …	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 AI Experience Person…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 AI Reporting and Ana…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 AI Chatbot & Livecha…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 Ticket & Conversatio…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 Customer Data Platfo…	20.65:1	3.0:1	#000000	#FDFDFD	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.

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 20 passed

PASS

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
EMAIL `div.relative > address.relative > div.relative > div.relative`
HOTLINE `div.relative > address.relative > div.relative > div.relative`
©2026 EASY AI TECHNOLOGY SOLUTIONS COMPANY LIMITED. Business Registration Certi… `div.relative > div.relative > div.relative > p`
hello@geteasy.ai `div.relative > div.relative > p > a.hover-underline-animation`
0346 335 168 `div.relative > div.relative > p > a.hover-underline-animation`

These are opportunities to improve the legibility of your content.

Names and labels

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
Start free trialStart free trial `div.relative > div.container > div.liquid-section > 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.

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
Start free trial Start free trial `header#site-header-bar > div.relative > a > button.btn`
Start free trial Start free trial `div.flex > div.flex > a > button.btn`
Start free trial Start free trial `div.container > div.relative > a > button.btn`

○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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●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.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[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

○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.

○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.