Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Link & Button Quality

Action

3 issue(s) across 29 links and 0 buttons

FIX

3 issue(s) across 29 links and 0 buttons

3 link(s) with no accessible text

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

Got: https://desktop.line-scdn.net/win/new/LineInst.exe; https://www.youtube.com/user/LineAppGlobal; https://www.facebook.com/line.worldwide

8 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/"]; a[href="https://play.google.com/store/apps/details?id=jp.naver.line.android"]; a[href="https://itunes.apple.com/jp/app/line/id443904275"]; a[href="https://play.google.com/store/apps/details?id=jp.naver.line.android"]; a[href="https://itunes.apple.com/app/line/id443904275"]; a[href="https://play.google.com/store/apps/details?id=jp.naver.line.android"]; a[href="https://desktop.line-scdn.net/win/new/LineInst.exe"]; a[href="https://apps.microsoft.com/store/detail/line-desktop/XPFCC4CD725961"]

3 link(s) open in new tab without warning

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

Got: https://chrome.google.com/webstore/detail/line/ophjlpahpchlmihnnnihgmmeilfjmj…; https://line-android-universal-download.line-scdn.net/line-apk-download.html; https://line.me/en/download/screen-saver

15 link(s) with descriptive text

29 links

3 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	<picture> <sou…	img no alt	Add alt attribute to the image
https://play.google.com/store/apps/detai…	<picture> …	new tab	Add '(opens in new tab)' to text
https://itunes.apple.com/jp/app/line/id4…	<picture> …	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	<picture> …	new tab	Add '(opens in new tab)' to text
https://desktop.line-scdn.net/win/new/Li…	(empty)	empty	Add link text or aria-label
https://itunes.apple.com/app/line/id4439…	App Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Google Play	new tab	Add '(opens in new tab)' to text
https://desktop.line-scdn.net/win/new/Li…	Desktop	new tab	Add '(opens in new tab)' to text
https://apps.microsoft.com/store/detail/…	Windows Store	new tab	Add '(opens in new tab)' to text
https://chrome.google.com/webstore/detai…	Chrome	new tab	Add '(opens in new tab)' to text
https://line-android-universal-download.…	APK	new tab	Add '(opens in new tab)' to text
https://line.me/en/download/screen-saver	Screen Saver	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/LineAppGlob…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/line.worldwide	(empty)	empty	Add link text or aria-label

15 links and buttons have descriptive text

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

https://desktop.line-scdn.net/win/new/LineInst.exe; https://www.youtube.com/user/LineAppGlobal; https://www.facebook.com/line.worldwide

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/"]; a[href="https://play.google.com/store/apps/details?id=jp.naver.line.android"]; a[href="https://itunes.apple.com/jp/app/line/id443904275"]; a[href="https://play.google.com/store/apps/details?id=jp.naver.line.android"]; a[href="https://itunes.apple.com/app/line/id443904275"]; a[href="https://play.google.com/store/apps/details?id=jp.naver.line.android"]; a[href="https://desktop.line-scdn.net/win/new/LineInst.exe"]; a[href="https://apps.microsoft.com/store/detail/line-desktop/XPFCC4CD725961"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://chrome.google.com/webstore/detail/line/ophjlpahpchlmihnnnihgmmeilfjmj…; https://line-android-universal-download.line-scdn.net/line-apk-download.html; https://line.me/en/download/screen-saver

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

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 ✗

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

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

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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found | LINE ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

13 icon(s) detected

REVIEW

13 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, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA 5 pass AA only

a Messenger APP

4.30:1

#000000

#A15F59

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

div LINE—always at your side.

4.33:1

#000000

#A36049

needs 4.5:1 (normal text)

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

p More than just a messenger app. …

4.29:1

#000000

#8F694B

needs 4.5:1 (normal text)

16px · above the fold

a Life on LINE

4.47:1

#000000

#926C4C

needs 4.5:1 (normal text)

16px · above the fold

a Messenger APP

4.14:1

#000000

#8C6743

needs 4.5:1 (normal text)

16px · above the fold

2 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 Life on LINE	3.07:1	3.0:1	#000000	#3E642E	Pass
h2 Messenger APP	7.84:1	3.0:1	#000000	#A59D92	Pass
h2 Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title LINE｜always at you…	5.75:1	4.5:1	#000000	#AE796C	Pass
a Life on LINE	4.59:1	4.5:1	#000000	#A4655C	Pass
a Messenger APP	4.30:1	4.5:1	#000000	#A15F59	Fail
a Services	5.76:1	4.5:1	#000000	#9F7F73	Pass
div Life on LINE	7.18:1	4.5:1	#000000	#B09086	Pass
div LINE—always at you…	4.33:1	4.5:1	#000000	#A36049	Fail
div Download	9.43:1	4.5:1	#000000	#B4ACAB	Pass
div Download	9.02:1	4.5:1	#000000	#B1A8A6	Pass
span Scroll	8.29:1	4.5:1	#000000	#A9A1A0	Pass
p More than just a mes…	4.29:1	4.5:1	#000000	#8F694B	Fail
a Life on LINE	4.47:1	4.5:1	#000000	#926C4C	Fail
a Messenger APP	4.14:1	4.5:1	#000000	#8C6743	Fail
a Services	4.82:1	4.5:1	#000000	#8E7553	Pass
p New communication ap…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span App Store	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Google Play	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Desktop	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 87/100 — 2 failing, 15 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.

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
Messenger APP `div#gnbArea > ul.gnb > li.gnbItem > a.fontB`
Services `div#gnbArea > ul.gnb > li.gnbItem > a.fontB`
Keep current with the latest news on LINE. `li.serviceCnt > div.service > div.txtArea > h4.onlySp`
LINE NEWS is the most popular news content curation service in Asia and aims to… `li.serviceCnt > div.service > div.txtArea > div.desc`
Listen, Watch and <br>Sing along. `li.serviceCnt > div.service > div.txtArea > h4.onlySp`
LINE MUSIC is a music streaming service in Japan with over 100 million songs, b… `li.serviceCnt > div.service > div.txtArea > div.desc`
All Product `div.productMenuWrap > ul.productMenu > li.all > button.productCategory`

These are opportunities to improve the legibility of your content.

Names and labels

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
header.en > div > h1 > a `header.en > div > h1 > a`
div.productCnt > ul.productList > li.productBanner > a `div.productCnt > ul.productList > li.productBanner > a`
div.externalLinks > ul.snsLinks > li > a.YouTube `div.externalLinks > ul.snsLinks > li > a.YouTube`
div.externalLinks > ul.snsLinks > li > a.Facebook `div.externalLinks > ul.snsLinks > li > a.Facebook`

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.

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

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

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○`button`, `link`, and `menuitem` elements have accessible names

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

○Deprecated ARIA roles were not used

○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

○`[role]`s have all required `[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

○`[role]` values are valid

○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

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

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

A+

Heading Hierarchy

4 headings

PASS

4 headings

Single H1 present

H1 <picture> <source srcset="/static/img/icon-title-pc_1.png 1x,/static/img/icon-title-pc_1.5.png 1.5x,/static/img/icon-title-pc_2.png 2x" /> <img loadin
H2 Life on LINE
H2 Messenger APP
H2 Services

A+

Alt Text Quality

All 29 images OK

PASS

All 29 images OK

29 decorative image(s) correctly marked

29 images 29 decorative

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.

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