Skip to content
https://nippon.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Form Accessibility
Action
6 of 13 controls have issues
FIX
6 of 13 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="gn1">; <input type="checkbox" id="gn2">; <input type="checkbox" id="gsp_global">; <input type="checkbox" id="gnsp">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="query-text">; <input type="text" id="query-text2">
Info::
7 control(s) properly labeled
13 controls
7 labeled
2 placeholder only
4 unlabeled
ControlTypeLabelMethod
#gn4checkboxNewsfor/id
#gn5checkboxSectionsfor/id
#gn3checkboxPopularfor/id
#gnsp2checkboxNewsfor/id
#gnsp1checkboxSectionsfor/id
#gnsp3checkboxSectionsfor/id
#gnsp5checkboxPopularfor/id
#query-texttext(Search)placeholder only
#query-text2text(Search)placeholder only
#gn1checkbox(none)none
#gsp_globalcheckbox(none)none
#gnspcheckbox(none)none
#gn2checkbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="gn1">; <input type="checkbox" id="gn2">; <input type="checkbox" id="gsp_global">; <input type="checkbox" id="gnsp">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" id="query-text">; <input type="text" id="query-text2">

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
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.
B
Heading Hierarchy
15 headings
REVIEW
15 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 News in Brief
  • H2 In-depth Deeper takes on the issues that shape the nation.
  • H2 Japan Data Basic information on Japan with easy-to-understand statistics and diagrams.
  • H2 Languages
  • H2 Follow Us
  • H2 Our Newsletter
  • H2 Most Popular
  • H2 By Hits
  • H2 By Shares
  • H2 By Time
  • H2 Tags to Watch
  • H2 Japan Glances Quick, basic overviews on Japan's culture, society, and more.
  • H2 Japan in Video Video views of the country and its people, places, and many charms. Japan in
  • H2 (empty)
  • H2 Explore Japan in Photos

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found | nippon.com ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
11 icon(s) detected
REVIEW
11 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 2 pass AA only
a 简体字
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a 繁體字
3.47:1
#000000
on
#A84308
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a العربية
4.15:1
#000000
on
#AD570D
needs 4.5:1 (normal text)
16px · above the fold
a Русский
4.26:1
#000000
on
#B2570D
needs 4.5:1 (normal text)
16px · above the fold
a Latest
2.35:1
#000000
on
#7E3206
needs 4.5:1 (normal text)
16px · above the fold
a In-depth
1.04:1
#000000
on
#0F0500
needs 4.5:1 (normal text)
16px · above the fold

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)
ElementRatioRequiredFGBGResult
h2 News in Brief11.36:13.0:1
#000000
#95D03A
Pass
h2 Languages11.36:13.0:1
#000000
#95D03A
Pass
h2 Follow Us11.36:13.0:1
#000000
#95D03A
Pass
h2 Our Newsletter11.36:13.0:1
#000000
#95D03A
Pass
h2 Most Popular11.36:13.0:1
#000000
#95D03A
Pass
h2 By Hits11.36:13.0:1
#000000
#95D03A
Pass
h2 By Shares11.36:13.0:1
#000000
#95D03A
Pass
h2 By Time11.36:13.0:1
#000000
#95D03A
Pass
h2 Tags to Watch11.36:13.0:1
#000000
#95D03A
Pass
h2 Explore Japan in Pho…11.36:13.0:1
#000000
#95D03A
Pass
title Nippon.com | Your Do…21.00:14.5:1
#000000
#FFFFFF
Pass
a 日本語7.37:14.5:1
#000000
#999999
Pass
a 简体字1.00:14.5:1
#000000
#000000
Fail
a 繁體字3.47:14.5:1
#000000
#A84308
Fail
a Français5.58:14.5:1
#000000
#CA6A0D
Pass
a Español5.15:14.5:1
#000000
#C0660F
Pass
a العربية4.15:14.5:1
#000000
#AD570D
Fail
a Русский4.26:14.5:1
#000000
#B2570D
Fail
a Latest2.35:14.5:1
#000000
#7E3206
Fail
a In-depth1.04:14.5:1
#000000
#0F0500
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 26 passed
REVIEW
85

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

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.usp-gn > div.usp-gnin > form.usp-search > button div.usp-gn > div.usp-gnin > form.usp-search > button

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.usp-gnin > ul.usp-gn_sns > li > a.i-insta div.usp-gnin > ul.usp-gn_sns > li > a.i-insta
div.usp-gnin > ul.usp-gn_sns > li > a.i-youtube div.usp-gnin > ul.usp-gn_sns > li > a.i-youtube
div.usp-gnin > ul.usp-gn_sns > li > a.i-twitter div.usp-gnin > ul.usp-gn_sns > li > a.i-twitter
div.usp-gnin > ul.usp-gn_sns > li > a.i-facebook div.usp-gnin > ul.usp-gn_sns > li > a.i-facebook
div.cpc-asidediv > div.cpc-asidediv_in > p#csnslink > a.i-insta div.cpc-asidediv > div.cpc-asidediv_in > p#csnslink > a.i-insta
div.cpc-asidediv > div.cpc-asidediv_in > p#csnslink > a.i-youtube div.cpc-asidediv > div.cpc-asidediv_in > p#csnslink > a.i-youtube
div.cpc-asidediv > div.cpc-asidediv_in > p#csnslink > a.i-twitter div.cpc-asidediv > div.cpc-asidediv_in > p#csnslink > a.i-twitter
div.cpc-asidediv > div.cpc-asidediv_in > p#csnslink > a.i-facebook div.cpc-asidediv > div.cpc-asidediv_in > p#csnslink > a.i-facebook
li.gpc-c1_2 > ul.c-footersns > li > a.i-insta li.gpc-c1_2 > ul.c-footersns > li > a.i-insta
li.gpc-c1_2 > ul.c-footersns > li > a.i-youtube li.gpc-c1_2 > ul.c-footersns > li > a.i-youtube
li.gpc-c1_2 > ul.c-footersns > li > a.i-twitter li.gpc-c1_2 > ul.c-footersns > li > a.i-twitter
li.gpc-c1_2 > ul.c-footersns > li > a.i-facebook li.gpc-c1_2 > ul.c-footersns > li > a.i-facebook
li.gpc-c1_2 > ul.c-footersns > li > a.i-rss li.gpc-c1_2 > ul.c-footersns > li > a.i-rss

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
All section.c-wrap > div.c-newsswiper > ul#newstitle > li#news_all
Subscribe div.cpc-asidediv > div.cpc-asidediv_in > p.c-newsletter > a.i-newsletter
Guide div.c-wrap > p.c-mainttl > span.c-mainttllogo > span#TITLE_TOP_GUIDE_TITLE_1
to Japan div.c-wrap > p.c-mainttl > span.c-mainttllogo > span#TITLE_TOP_GUIDE_TITLE_2
Japan in div.c-wrap > h2.c-mainttl > span.c-mainttllogo > span#TITLE_TOP_VIDEO_TITLE_1
Video div.c-wrap > h2.c-mainttl > span.c-mainttllogo > span#TITLE_TOP_VIDEO_TITLE_2

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Subscribe ul.gpc > li.gpc-c1_2 > form.c-melma > button

These are opportunities to improve keyboard navigation in your application.

○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN ASIDE CONTENTINFO footer

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+
Alt Text Quality
All 12 images OK
PASS
All 12 images OK
Info::
12 image(s) with good alt text
12 images 12 good alt text
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback