Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 REVIEW 6 FIX

Tap Target Adequacy

Action

24 tap target(s) too small or too close together

FIX

24 tap target(s) too small or too close together

24 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-phwkno

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #00e676

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

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

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 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 Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

title Smart G4 Hotel GRMS — Guest Room Manag…

1.16:1

#000000

#161614

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Hotel GRMS, BMS & Sm…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Affordable Smart Hot…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 One System. Every Bu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Why Choose G4 Techno…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We Manufacture Every…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Join the Smart G4 Pa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Smart Automation Acr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Hotel GRMS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 BMS Solutions	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 360+ SBUS Products, …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Open Protocol	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Global Reach	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Full Integration	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Wall Control Panel	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Hotel & Hospitality	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Medical & Healthcare	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Technology	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cookie Consent	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Smart G4 Hotel GRMS …	1.16:1	4.5:1	#000000	#161614	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Heading Hierarchy

19 headings

PASS

19 headings

Single H1 present

H1 Hotel GRMS, BMS & Smart Building Automation
H2 Affordable Smart Hotel G4 Automation Cost Solutions for Modern Hotels
H3 Hotel GRMS
H3 BMS Solutions
H3 360+ SBUS Products, 60+ Wireless & Retrofit
H3 Open Protocol
H3 Global Reach
H3 Full Integration
H2 One System. Every Building Type.
H2 Why Choose G4 Technology?
H2 We Manufacture Everything You Need
H2 Join the Smart G4 Partner Network
H2 Smart Automation Across Every Sector
H3 Wall Control Panel
H3 Hotel & Hospitality
H3 Medical & Healthcare
H3 Technology
H3 Resources
H3 Cookie Consent

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 48 images OK

PASS

All 48 images OK

48 image(s) with good alt text

48 images 48 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

58 links, 68 buttons — all OK

PASS

58 links, 68 buttons — all OK

14 link(s) open in new tab without warning

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

Got: https://www.facebook.com/smarthomeG4; https://www.youtube.com/digitcom; https://www.youtube.com/smartg4; https://www.youtube.com/smarthomebus; https://www.linkedin.com/in/smartg4; https://x.com/SmartG4s; https://x.com/smartbusg4; https://instagram.com/smartg4/; https://wa.me/963997456194; https://wa.me/639271594575 (+4 more)

44 link(s) with descriptive text

58 links

0 empty

0 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/smarthomeG4	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/digitcom	YouTube (digitcom)	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/smartg4	YouTube (Smart G4)	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/smarthomebus	YouTube (SmartHomeBus)	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/smartg4	LinkedIn	new tab	Add '(opens in new tab)' to text
https://x.com/SmartG4s	Twitter / X (@SmartG4s)	new tab	Add '(opens in new tab)' to text
https://x.com/smartbusg4	Twitter / X (@smartbusg4)	new tab	Add '(opens in new tab)' to text
https://instagram.com/smartg4/	Instagram	new tab	Add '(opens in new tab)' to text
https://wa.me/963997456194	WhatsApp (+963 997 456 194 @ho…	new tab	Add '(opens in new tab)' to text
https://wa.me/639271594575	WhatsApp / Viber (+63 927 159 …	new tab	Add '(opens in new tab)' to text
viber://chat?number=%2B639271594575	Viber (+63 927 159 4575)	new tab	Add '(opens in new tab)' to text
weixin://dl/chat?smartgroup	WeChat (@smartgroup)	new tab	Add '(opens in new tab)' to text
https://t.me/hotelcontrol	Telegram (@hotelcontrol)	new tab	Add '(opens in new tab)' to text
https://t.me/smartgroup	Telegram (@smartgroup)	new tab	Add '(opens in new tab)' to text

112 links and buttons have descriptive text

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

https://www.facebook.com/smarthomeG4; https://www.youtube.com/digitcom; https://www.youtube.com/smartg4; https://www.youtube.com/smarthomebus; https://www.linkedin.com/in/smartg4; https://x.com/SmartG4s; https://x.com/smartbusg4; https://instagram.com/smartg4/; https://wa.me/963997456194; https://wa.me/639271594575 (+4 more)

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"

PASS

Lang attribute set to "en"

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

Got: en

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+

Mobile-Readable Font Sizes

All 113 visible text node(s) render at >= 12 CSS pixels

PASS

All 113 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 22 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
Decline `div.max-w-7xl > div.flex > div.flex > button.inline-flex`

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
View Grand Hotel Lobby `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Smart Guest Room `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Intelligent Corridors `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Rooftop Pool Automation `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Luxury Suite Control `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Smart Reception `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Nurse Call System `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Smart Hospital Corridor `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Patient Room Automation `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Modern Healthcare Facility `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Operating Theatre Control `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Accessibility & PWD `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Intelligent Living Room `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Luxury Villa Exterior `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Smart Kitchen `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Outdoor Pool & Terrace `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Master Bedroom Suite `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Wall Control Panel `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Private Home Cinema `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Home Theater Room `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Luxury Screening Room `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View LED Ambient Cinema `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Entertainment Control `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`
View Auditorium Automation `div.max-w-content > div.mt-6 > div.flex > button.rounded-full`

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

●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

●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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

○Identical links have the same purpose.

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.