Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

2 landmarks

FIX

2 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

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

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

Link & Button Quality

Action

6 issue(s) across 44 links and 4 buttons

FIX

6 issue(s) across 44 links and 4 buttons

2 link(s) with no accessible text

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

Got: #; https://twitter.com/lycorptechjp_e

1 link(s) with generic text

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

Got: ("More")

8 link(s) open in new tab without warning

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

Got: https://pay.line.me/portal/global/main; https://blockchain.line.biz/; https://pay.line.me/portal/global/main; https://blockchain.line.biz/; https://developers-pay.line.me/; https://adsnetwork-docs.linebiz.com/; https://docs.dappportal.io/; https://api.line-status.info/

3 button(s) with no accessible text

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

Got: button.custom (#105 on page); button.focus-visible:outline-primary (#108 on page); button.rounded-md (#118 on page)

33 link(s) with descriptive text

44 links

2 empty

1 generic text

8 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
	More	generic text	Replace with descriptive text
Before: More Suggested: Home page
#	(empty)	empty	Add link text or aria-label
https://pay.line.me/portal/global/main	LINE PayAdd the LINE Pay payme…	new tab	Add '(opens in new tab)' to text
https://blockchain.line.biz/	Mini DappAdopt Blockchain tech…	new tab	Add '(opens in new tab)' to text
https://pay.line.me/portal/global/main	LINE Pay	new tab	Add '(opens in new tab)' to text
https://blockchain.line.biz/	Mini Dapp	new tab	Add '(opens in new tab)' to text
https://developers-pay.line.me/	LINE Pay	new tab	Add '(opens in new tab)' to text
https://adsnetwork-docs.linebiz.com/	LY Ads Network (Japanese only)	new tab	Add '(opens in new tab)' to text
https://docs.dappportal.io/	Mini Dapp	new tab	Add '(opens in new tab)' to text
https://api.line-status.info/	LINE API Status	new tab	Add '(opens in new tab)' to text
https://twitter.com/lycorptechjp_e	(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
<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.

#; https://twitter.com/lycorptechjp_e

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.

("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

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

https://pay.line.me/portal/global/main; https://blockchain.line.biz/; https://pay.line.me/portal/global/main; https://blockchain.line.biz/; https://developers-pay.line.me/; https://adsnetwork-docs.linebiz.com/; https://docs.dappportal.io/; https://api.line-status.info/

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

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

button.custom (#105 on page); button.focus-visible:outline-primary (#108 on page); button.rounded-md (#118 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

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-9pk1gs

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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://social-plugins.line.me/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://social-plugins.line.me/manifest.json

Manifest contains invalid JSON.

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

9 headings

REVIEW

9 headings

No H1 heading found

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

H2 Products
H3 Messaging API
H3 LINE Login
H3 LINE Front-end Framework (LIFF)
H3 LINE MINI App
H3 LINE Pay
H3 Mini Dapp
H2 News
H2 Tips for Developers

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

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

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA 6 pass AA only

div Tips

3.39:1

#000000

#5B6630

needs 4.5:1 (normal text)

16px · above the fold

div FAQ

2.52:1

#000000

#48522C

needs 4.5:1 (normal text)

16px · above the fold

div Glossary

4.30:1

#000000

#7F6F52

needs 4.5:1 (normal text)

16px · above the fold

span Messaging API

3.72:1

#000000

#666861

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

1 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
h2 Products	9.64:1	3.0:1	#000000	#C7AB8E	Pass
h2 News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tips for Developers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title LINE Developers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div About	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div News	6.78:1	4.5:1	#000000	#8C9862	Pass
div Products	6.35:1	4.5:1	#000000	#80963C	Pass
div Documentation	5.24:1	4.5:1	#000000	#788547	Pass
div Tips	3.39:1	4.5:1	#000000	#5B6630	Fail
div FAQ	2.52:1	4.5:1	#000000	#48522C	Fail
div Glossary	4.30:1	4.5:1	#000000	#7F6F52	Fail
div More	5.49:1	4.5:1	#000000	#977E66	Pass
div Connect with	5.75:1	4.5:1	#000000	#9B816B	Pass
a / Start Console >	7.45:1	4.5:1	#000000	#B1957A	Pass
div Brief overview of ea…	8.08:1	4.5:1	#000000	#9FA1A0	Pass
span Messaging API	3.72:1	4.5:1	#000000	#666861	Fail
span Enable two-way commu…	12.07:1	4.5:1	#000000	#CCC3B8	Pass
span LINE Login	12.71:1	4.5:1	#000000	#CEC9BD	Pass
span Let LINE users easil…	11.86:1	4.5:1	#000000	#C5C3B6	Pass
span LINE Front-end Frame…	6.66:1	4.5:1	#000000	#969181	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 83/100 — 5 failing, 22 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.

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