Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 日テレ ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

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.

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) 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.

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

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Favicon & Branding

3 icon(s) detected

REVIEW

3 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

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

REVIEW

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

3 pass 17 fail WCAG AA 3 pass AA only

title 日本テレビ

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a ドラマ

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a ニュース·情報

3.06:1

#000000

#735253

needs 4.5:1 (normal text)

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

a バラエティ·音楽

2.52:1

#000000

#654647

needs 4.5:1 (normal text)

16px · top of page (header area)

a 映画

3.35:1

#000000

#B03328

needs 4.5:1 (normal text)

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

a ミニ番組

4.29:1

#000000

#DA2811

needs 4.5:1 (normal text)

16px · above the fold

a 通販

4.46:1

#000000

#E12414

needs 4.5:1 (normal text)

16px · above the fold

a 日テレの取り組み

2.61:1

#000000

#585119

needs 4.5:1 (normal text)

16px · above the fold

span 番組サイト

2.61:1

#000000

#585119

needs 4.5:1 (normal text)

16px · above the fold

span 番組サイト

2.61:1

#000000

#585119

needs 4.5:1 (normal text)

16px · above the fold

span 番組サイト

2.64:1

#000000

#585219

needs 4.5:1 (normal text)

16px · mid-page

span 番組サイト

2.64:1

#000000

#585219

needs 4.5:1 (normal text)

16px · mid-page

span 番組サイト

2.84:1

#000000

#5D5718

needs 4.5:1 (normal text)

16px · mid-page

span 前へ

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · mid-page

span 次へ

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · mid-page

span 日テレ系人気番組をTVerで

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · mid-page

span リアルタイム視聴できます

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · mid-page

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
title 日本テレビ	1.00:1	4.5:1	#000000	#000000	Fail
a ドラマ	1.00:1	4.5:1	#000000	#000000	Fail
a ニュース·情報	3.06:1	4.5:1	#000000	#735253	Fail
a バラエティ·音…	2.52:1	4.5:1	#000000	#654647	Fail
a 映画	3.35:1	4.5:1	#000000	#B03328	Fail
a イベント	4.74:1	4.5:1	#000000	#E62C17	Pass
a スポーツ	4.65:1	4.5:1	#000000	#E62616	Pass
a アニメ	4.65:1	4.5:1	#000000	#E52815	Pass
a ミニ番組	4.29:1	4.5:1	#000000	#DA2811	Fail
a 通販	4.46:1	4.5:1	#000000	#E12414	Fail
a 日テレの取り�…	2.61:1	4.5:1	#000000	#585119	Fail
span 番組サイト	2.61:1	4.5:1	#000000	#585119	Fail
span 番組サイト	2.61:1	4.5:1	#000000	#585119	Fail
span 番組サイト	2.64:1	4.5:1	#000000	#585219	Fail
span 番組サイト	2.64:1	4.5:1	#000000	#585219	Fail
span 番組サイト	2.84:1	4.5:1	#000000	#5D5718	Fail
span 前へ	1.32:1	4.5:1	#000000	#222222	Fail
span 次へ	1.32:1	4.5:1	#000000	#222222	Fail
span 日テレ系人気�…	1.32:1	4.5:1	#000000	#222222	Fail
span リアルタイム�…	1.32:1	4.5:1	#000000	#222222	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+

Alt Text Quality

1 of 10 images have issues

PASS

1 of 10 images have issues

1 image(s) with generic alt text

1 decorative image(s) correctly marked

8 image(s) with good alt text

10 images 8 good alt text 1 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

31 links, 2 buttons — all OK

PASS

31 links, 2 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://shop.ntv.co.jp/; https://www.ntv.co.jp/info/; https://www.ntvhd.co.jp/

28 link(s) with descriptive text

31 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://shop.ntv.co.jp/	通販	new tab	Add '(opens in new tab)' to text
https://www.ntv.co.jp/info/	日テレ企業・IR情報	new tab	Add '(opens in new tab)' to text
https://www.ntvhd.co.jp/	日テレホールディング…	new tab	Add '(opens in new tab)' to text

30 links and buttons have descriptive text

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

https://shop.ntv.co.jp/; https://www.ntv.co.jp/info/; https://www.ntvhd.co.jp/

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

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 22 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.

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
番組表 `div.OnAir-module-scss-module__attOOq__onairButtons > a.LinkButton-module-scss-module__6NqDkG__linkButton > div.LinkButton-module-scss-module__6NqDkG__content > span`
番組サイト `div.OnAirItem-module-scss-module__GiT_0a__itemButton > a.LinkButton-module-scss-module__6NqDkG__linkButton > div.LinkButton-module-scss-module__6NqDkG__content > span`
同時配信中 `div.OnAirItem-module-scss-module__GiT_0a__itemButton > a.LinkButton-module-scss-module__6NqDkG__linkButton > div.LinkButton-module-scss-module__6NqDkG__content > span`
夜 9:00〜 `div.OnAir-module-scss-module__attOOq__onairNavGrid > div.OnAir-module-scss-module__attOOq__onairNavCell > div.OnAir-module-scss-module__attOOq__onairNavItem > p.OnAir-module-scss-module__attOOq__onairNavItemTime`
夜 9:54〜 `div.OnAir-module-scss-module__attOOq__onairNavGrid > div.OnAir-module-scss-module__attOOq__onairNavCell > div.OnAir-module-scss-module__attOOq__onairNavItem > p.OnAir-module-scss-module__attOOq__onairNavItemTime`
夜 10:00〜 `div.OnAir-module-scss-module__attOOq__onairNavGrid > div.OnAir-module-scss-module__attOOq__onairNavCell > div.OnAir-module-scss-module__attOOq__onairNavItem > p.OnAir-module-scss-module__attOOq__onairNavItemTime`
第7話あらすじ・予告動画公開！ `div.InformationItem-module-scss-module__z_vtnG__item > div.InformationItem-module-scss-module__z_vtnG__itemBody > div.InformationItem-module-scss-module__z_vtnG__itemBodyTexts > p.InformationItem-module-scss-module__z_vtnG__itemBodyHeading`
04/23 01:31 `div.swiper-slide > a.NtvNewsItem-module-scss-module__6L_Vrq__item > div > p.NtvNewsItem-module-scss-module__6L_Vrq__itemBodyDate`
04/23 01:26 `div.swiper-slide > a.NtvNewsItem-module-scss-module__6L_Vrq__item > div > p.NtvNewsItem-module-scss-module__6L_Vrq__itemBodyDate`

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
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > a`
div.swiper > div.swiper-wrapper > div.swiper-slide > a `div.swiper > div.swiper-wrapper > div.swiper-slide > 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.

○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

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

●Elements use only permitted ARIA attributes

●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

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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