Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 4 REVIEW 6 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

Mobile-Readable Font Sizes

Action

58% of visible text renders at >= 12 CSS px (5 below threshold)

FIX

58% of visible text renders at >= 12 CSS px (5 below threshold)

5 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> 11.0px ("Back-Office Authentication"); <button> 11.0px ("Forgot password?"); <span> 11.0px ("Unified Access Control"); <span> 10.0px ("PostgreSQL 17"); <p> 10.0px ("Unauthorized access to this back-office ...").

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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.

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 ✗

Heading Hierarchy

2 headings

REVIEW

2 headings

No H1 heading found

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

H2 Centralized Resource Management For Naree Foundation and Group Ventures
H2 Sign in to CRM

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

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 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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.

Color Contrast (Screenshot)

Action

19 text elements analyzed, 19 fail WCAG AA

REVIEW

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

0 pass 19 fail WCAG AA

h2 Centralized Resource Management

1.08:1

#000000

#080B1D

needs 3.0:1 (large text)

24px · top of page (header area)

h2 and Group Ventures

1.09:1

#000000

#090C20

needs 3.0:1 (large text)

24px · above the fold

h2 Sign in to CRM

1.11:1

#000000

#0C0E26

needs 3.0:1 (large text)

24px · above the fold

title CRM + NFVS | Enterprise Business Managem…

1.07:1

#000000

#070B1B

needs 4.5:1 (normal text)

16px · top of page (header area)

span Our Portfolio

1.07:1

#000000

#070B1C

needs 4.5:1 (normal text)

16px · top of page (header area)

span For Naree Foundation

1.08:1

#000000

#080C1F

needs 4.5:1 (normal text)

16px · top of page (header area)

span Powered by NFVS Enterprise CRM

1.09:1

#000000

#0A0D22

needs 4.5:1 (normal text)

16px · above the fold

span Build 2026.09.15

1.09:1

#000000

#0A0D23

needs 4.5:1 (normal text)

16px · above the fold

span CRM + NFVS Enterprise

1.10:1

#000000

#0B0E24

needs 4.5:1 (normal text)

16px · above the fold

span Back-Office Authentication

1.10:1

#000000

#0B0E25

needs 4.5:1 (normal text)

16px · above the fold

p Enter your authorized enterprise credent…

1.11:1

#000000

#0C0E27

needs 4.5:1 (normal text)

16px · above the fold

label Corporate Email

1.11:1

#000000

#0C0E27

needs 4.5:1 (normal text)

16px · above the fold

label Password

1.11:1

#000000

#0C0E27

needs 4.5:1 (normal text)

16px · mid-page

button Forgot password?

1.10:1

#000000

#0C0D26

needs 4.5:1 (normal text)

16px · mid-page

span Remember this workstation

1.11:1

#000000

#0C0E25

needs 4.5:1 (normal text)

16px · mid-page

span Sign In to Back Office

1.10:1

#000000

#0B0E23

needs 4.5:1 (normal text)

16px · mid-page

span Unified Access Control

1.09:1

#000000

#0B0D22

needs 4.5:1 (normal text)

16px · mid-page

span PostgreSQL 17

1.09:1

#000000

#0B0D20

needs 4.5:1 (normal text)

16px · mid-page

p Unauthorized access to this back-office …

1.09:1

#000000

#0B0D1E

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (19)

Element	Ratio	Required	FG	BG	Result
h2 Centralized Resource…	1.08:1	3.0:1	#000000	#080B1D	Fail
h2 and Group Ventures	1.09:1	3.0:1	#000000	#090C20	Fail
h2 Sign in to CRM	1.11:1	3.0:1	#000000	#0C0E26	Fail
title CRM + NFVS \| Enterpr…	1.07:1	4.5:1	#000000	#070B1B	Fail
span Our Portfolio	1.07:1	4.5:1	#000000	#070B1C	Fail
span For Naree Foundation	1.08:1	4.5:1	#000000	#080C1F	Fail
span Powered by NFVS Ente…	1.09:1	4.5:1	#000000	#0A0D22	Fail
span Build 2026.09.15	1.09:1	4.5:1	#000000	#0A0D23	Fail
span CRM + NFVS Enterpris…	1.10:1	4.5:1	#000000	#0B0E24	Fail
span Back-Office Authenti…	1.10:1	4.5:1	#000000	#0B0E25	Fail
p Enter your authorize…	1.11:1	4.5:1	#000000	#0C0E27	Fail
label Corporate Email	1.11:1	4.5:1	#000000	#0C0E27	Fail
label Password	1.11:1	4.5:1	#000000	#0C0E27	Fail
button Forgot password?	1.10:1	4.5:1	#000000	#0C0D26	Fail
span Remember this workst…	1.11:1	4.5:1	#000000	#0C0E25	Fail
span Sign In to Back Offi…	1.10:1	4.5:1	#000000	#0B0E23	Fail
span Unified Access Contr…	1.09:1	4.5:1	#000000	#0B0D22	Fail
span PostgreSQL 17	1.09:1	4.5:1	#000000	#0B0D20	Fail
p Unauthorized access …	1.09:1	4.5:1	#000000	#0B0D1E	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.

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

6 image(s) with good alt text

6 images 6 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#email	text	Corporate Email	for/id
#password	password	Password	for/id
input	checkbox		none

A+

Link & Button Quality

0 links, 3 buttons — all OK

PASS

0 links, 3 buttons — all OK

0 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

3 links and buttons have descriptive text

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "email" should use type="email" (currently type="text")

Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

All 1 eligible field(s) carry autocomplete/inputmode

PASS

All 1 eligible field(s) carry autocomplete/inputmode

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+

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

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

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+

Lighthouse Accessibility Audits

Score 98/100 — 1 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.

Best practices

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.geist_a71539c9-module__T19VSG__variable `html.geist_a71539c9-module__T19VSG__variable`

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

●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

●Elements use only permitted ARIA attributes

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

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

○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

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