Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 6 REVIEW 5 FIX

Link & Button Quality

Action

12 issue(s) across 37 links and 9 buttons

FIX

12 issue(s) across 37 links and 9 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a (#134 on page); a.elementor-button (#508 on page); http://demo.casethemes.net/consultio-corporate3/; https://www.nichidai.jp/english/index.html; https://nichidaifilter.co.jp/english/; #; #

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.nichidai.co.th/service/filter-housting/ ("Read more"); https://www.nichidai.co.th/service/bonmesh/ ("Read more"); https://www.nichidai.co.th/service/poremet/ ("Read more")

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.search-submit (#139 on page); button.search-submit (#643 on page)

27 link(s) with descriptive text

37 links

7 empty

3 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://www.nichidai.co.th/service/filte…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Filter Housting
https://www.nichidai.co.th/service/bonme…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Bonmesh
https://www.nichidai.co.th/service/porem…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Poremet
	(empty)	empty	Add link text or aria-label
http://demo.casethemes.net/consultio-cor…	(empty)	empty	Add link text or aria-label
https://www.nichidai.jp/english/index.ht…	(empty)	empty	Add link text or aria-label
https://nichidaifilter.co.jp/english/	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

34 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a (#134 on page); a.elementor-button (#508 on page); http://demo.casethemes.net/consultio-corporate3/; https://www.nichidai.jp/english/index.html; https://nichidaifilter.co.jp/english/; #; #

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

https://www.nichidai.co.th/service/filter-housting/ ("Read more"); https://www.nichidai.co.th/service/bonmesh/ ("Read more"); https://www.nichidai.co.th/service/poremet/ ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Icon-only buttons need an aria-label so screen readers can announce them.

button.search-submit (#139 on page); button.search-submit (#643 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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

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

1 navigation landmark(s) detected

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Heading Hierarchy

19 headings

REVIEW

19 headings

No H1 heading found

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

H3 Filter Housting
H3 Filter Housting
H3 Bonmesh
H3 Bonmesh
H3 Poremet
H3 Poremet
H3 Who are We
H3 Principles of Management
H3 News
H3 Let’s have a conversation
H3 Contact Us:
H3 Keep in Touch
H3 Location
H3 Telephone
H3 Email
H3 Filter Products
H3 Partners
H3 Contact Us
H3 Visitor

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

Form Accessibility

7 of 8 controls have issues

REVIEW

7 of 8 controls have issues

7 control(s) rely on placeholder only

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

Got: <input type="text" name="s">; <input type="text" name="subject">; <input type="text" name="your-name">; <input type="email" name="your-email">; <input type="text" name="your-phone">; <textarea name="your-message">; <input type="text" name="s" id="search">

1 control(s) properly labeled

8 controls

1 labeled

7 placeholder only

0 unlabeled

Control	Type	Label	Method
_wpcf7_ak_hp_textarea	textarea	Δ	none
subject	text	(Subject *)	placeholder only
your-name	text	(Your name *)	placeholder only
your-email	email	(Your mail *)	placeholder only
your-phone	text	(Phone number *)	placeholder only
your-message	textarea	(Message...)	placeholder only
s	text	(Search...)	placeholder only
#search	text	(Enter Keywords...)	placeholder only

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

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

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA 1 pass AA only

span Filter Products

1.10:1

#000000

#0F0F0F

needs 4.5:1 (normal text)

16px · top of page (header area)

span Bonmesh

2.82:1

#000000

#555555

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span Poremet

3.55:1

#000000

#646464

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span Filter Housing

1.30:1

#000000

#212121

needs 4.5:1 (normal text)

16px · above the fold

span Sanitary Tank

1.37:1

#000000

#252525

needs 4.5:1 (normal text)

16px · above the fold

span Super Clean Plate

3.83:1

#000000

#696969

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span Advantages

1.50:1

#000000

#2C2C2C

needs 4.5:1 (normal text)

16px · above the fold

span About Us

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

span Company Profile

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · above the fold

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 Filter Housting	5.03:1	3.0:1	#000000	#7C7C7C	Pass
h3 Bonmesh	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Poremet	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Contact Us:	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Location	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Telephone	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Email	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title NICHIDAI (THAILAND) …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Sintered Wire Mesh	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Filter Products	1.10:1	4.5:1	#000000	#0F0F0F	Fail
span Bonmesh	2.82:1	4.5:1	#000000	#555555	Fail
span Poremet	3.55:1	4.5:1	#000000	#646464	Fail
span Filter Housing	1.30:1	4.5:1	#000000	#212121	Fail
span Sanitary Tank	1.37:1	4.5:1	#000000	#252525	Fail
span Super Clean Plate	3.83:1	4.5:1	#000000	#696969	Fail
span Metal Fiber	5.03:1	4.5:1	#000000	#7C7C7C	Pass
span Advantages	1.50:1	4.5:1	#000000	#2C2C2C	Fail
span About Us	1.41:1	4.5:1	#000000	#272727	Fail
span Company Profile	1.35:1	4.5:1	#000000	#242424	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.

Lighthouse Accessibility Audits

Action

Score 79/100 — 4 failing, 16 passed

REVIEW

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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#copyButton > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button `div#copyButton > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ct-modal-content > form.search-form-popup > div.searchform-wrap > button.search-submit `div.ct-modal-content > form.search-form-popup > div.searchform-wrap > button.search-submit`

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.elementor-element > div.elementor-widget-container > div.ct-image-single > a `div.elementor-element > div.elementor-widget-container > div.ct-image-single > a`
div.elementor-element > div.elementor-widget-container > div.ct-image-single > a `div.elementor-element > div.elementor-widget-container > div.ct-image-single > a`
div.elementor-element > div.elementor-widget-container > div.ct-image-single > a `div.elementor-element > div.elementor-widget-container > div.ct-image-single > 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.

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
【NEW!】We will exhibit METALEX 2026 on 18~21 Nov. 2026 at BITEC, Bangkok `li > div > div.newsscroller_title > a`

These are opportunities to improve the legibility of your content.

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●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-hidden="true"]` elements do not contain focusable descendents

●Document has a `<title>` element

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○ARIA attributes are used as specified for the element's role

○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 use only permitted 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

○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

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

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

Landmark Structure

5 landmarks

PASS

5 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 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 13 images OK

PASS

All 13 images OK

7 decorative image(s) correctly marked

6 image(s) with good alt text

13 images 6 good alt text 7 decorative

All images have appropriate alt text.

Form Input Types

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

PASS

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

Input "s" should use type="search" (currently type="text")

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

Input "your-phone" should use type="tel" (currently type="text")

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

Input "s" should use type="search" (currently type="text")

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

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

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

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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+

Mobile-Readable Font Sizes

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

PASS

All 43 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

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.

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