Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 5 REVIEW 2 FIX

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

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

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="search" name="q">; <input type="search" name="q">

1 control(s) properly labeled

3 controls

1 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
input	input	Ask	aria-label
q	search	(Search companies, robots, technologies, papers)	placeholder only
q	search	(Search companies, robots, technologies, papers)	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

Tap Target Adequacy

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

REVIEW

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

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

Mobile-Readable Font Sizes

Action

76% of visible text renders at >= 12 CSS px (86 below threshold)

REVIEW

76% of visible text renders at >= 12 CSS px (86 below threshold)

86 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 ("Partnership"); <span> 11.0px ("Partnership"); <time> 11.0px ("01:22"); <a> 11.0px ("HD Hyundai Robotics"); <a> 11.0px ("Palantir Technologies").

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: MEKAWIRE

No 192x192 icon

A 192px icon is required for PWA installation.

512x512 icon present

PWA Install Criteria Not Installable

Name MEKAWIRE ✓192×192 icon ✗512×512 icon ✓Start URL / ✓Display Mode browser ✗

Name MEKAWIRE Display Mode browser Theme Color #000000 Background Color #ffffff Icons 2 icon(s)

PWA Depth

2 PWA signal(s) surfaced

REVIEW

2 PWA signal(s) surfaced

Manifest declares display="browser" -- no PWA UX

When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).

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

Landmark Structure

15 landmarks

PASS

15 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

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

Heading Hierarchy

29 headings, 1 skip(s)

PASS

29 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 HD Hyundai Robotics says Palantir AI agents cut fix time 63%, from 21.5 to 7.9 days
H3 Jeonnam-Gwangju fire service plans KRW 2.4bn firefighting robot for 800C blazes in 2027 skipped
H3 Inovance robot-and-energy line up 88%; Sanhua, Tuopu Q3 reports never mention robots
H3 Meta reportedly built humanoid Max with China's Fourier in three months
H2 Wire
H3 Thrun's Dulo reportedly raises USD 130m seed for AI that designs hardware
H3 Leaderdrive Q3 sales up 56% on humanoid joints as margins slip; Efort narrows loss
H3 Ecovacs Q3 profit falls 72% on memory chip costs as Roborock grows 33%
H3 Orbbec signs 10,000-unit deal with ACE Robotics as robot vision sales double
H3 What is Physical Intelligence (pi)? Robot AI models now sold through an API
H3 Re:Build gets $2.1bn for US contract manufacturing, robotics one of five lines
H3 Jack Technology launches Ani sewing robot as Q3 profit falls 59% on robot spending
H3 KRAFTON's Ludo Robotics shows Ludi 0.2, a robot model built to read human intent
H3 Walmart commits about $6B more to Symbotic; backlog could rise up to $6.92B
H3 Agility Robotics SPAC to raise $465M after redemptions; AGLT to trade on Nasdaq Nov 5
H3 AgiBot and Tsinghua train 96 robots on their own runs; packaging success hits 98.3%
H3 Estun Q3 revenue falls 12% to RMB 1.10bn as China's robot output booms; core profit up 133%
H2 Paper of the day
H3 Design and Experimental Validation of the Separation and Deployment System for the CHERI Lunar Micro-Rovers
H2 Watchlist
H2 Latest stories
H2 MEKAWIRE Analysis
H3 What is Physical Intelligence (pi)? Robot AI models now sold through an API
H3 Robot demand in Q3 2026 by region: China output up about 30%, Japan orders at a record
H3 Q3 2026 robotics earnings scorecard: installed bases profit, humanoid bets burn cash
H2 Trending technologies
H2 Trending companies
H2 Funding activity
H2 Latest deals

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Link & Button Quality

151 links, 3 buttons — all OK

PASS

151 links, 3 buttons — all OK

151 link(s) with descriptive text

151 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

154 links and buttons have descriptive text

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

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

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"

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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found · MEKAWIRE ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Favicon & Branding

6 icon(s) detected

PASS

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light dark

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 light dark ✓Dark theme-color #000000 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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.

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 Wire	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Paper of the day	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Watchlist	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest stories	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 MEKAWIRE Analysis	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trending technologie…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trending companies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Funding activity	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest deals	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title MEKAWIRE: The AI new…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span MEKAWIRE	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Ask	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Watchlist	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Sign in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Wire	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Papers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Companies	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Humanoids	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Robots	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Invest	21.00:1	4.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.

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 26 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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
24H `div.flex > div.flex > div.flex > a.tnum`
7D `div.flex > div.flex > div.flex > a.tnum`
30D `div.flex > div.flex > div.flex > a.tnum`
YTD `div.flex > div.flex > div.flex > a.tnum`

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.

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
Jeonnam-Gwangju fire service plans KRW 2.4bn firefighting robot for 800C blazes… `section.border-b > div.grid > article.border-b > h3.mt-1`

These are opportunities to improve keyboard navigation in your application.

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
About `nav.container-site > ul.flex > li > a.text-muted-foreground`
Terms `nav.container-site > ul.flex > li > a.text-muted-foreground`

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

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

●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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

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

●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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

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