Skip to content
https://sony.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Landmark Structure
21 landmarks
REVIEW
21 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
3 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "サイト全体の簡易的なメニュー" SEARCH MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

B
Heading Hierarchy
19 headings
REVIEW
19 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 MissionMission
  • H2 New Products /ServicesNew Products / Services
  • H2 Creator StoriesCreator Stories
  • H2 Corporate ActivitiesCorporate Activities
  • H2 News ReleasesNews Releases
  • H3 Sony and TCL Sign Definitive Agreements for Strategic Partnership in the Home Entertainment Field
  • H3 Sony to Open a Base in Japan to Engage in Media Production with Creators
  • H3 Sony's Breakthrough Audio, Imaging and Sports Technologies Raise the Bar for the NFL's Super Bowl LX in San Francisco
  • H3 Establishment of the World's First¹ Global Supply Chain to Introduce the Use of Renewable Plastics in Sony's High-Performance Products
  • H2 Important NoticesImportant Notices Important notice regardingproducts/servicesImportant notice
  • H3 Change of the Sony entity for License Agreements, etc.
  • H3 Free Repair for VAIO Fit 11A Personal Computer
  • H2 Cookie Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Cookie List

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

B
Form Accessibility
2 of 20 controls have issues
REVIEW
2 of 20 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="text" name="q">
Info::
18 control(s) properly labeled
20 controls
18 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
doctypeselectnone
ctselectnone
sortselectnone
pagemaxselectnone
imgsizeselectnone
doctypeselectnone
ctselectnone
sortselectnone
pagemaxselectnone
imgsizeselectnone
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
qtext(Enter the word you want to search)placeholder only
qtext(Enter the word you want to search)placeholder only

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

<input type="text" name="q">; <input type="text" name="q">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title SONY ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
title Sony Corporation - Home
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
button Corporate Information
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
span Corporate …
1.05:1
#000000
on
#080808
needs 4.5:1 (normal text)
16px · top of page (header area)
span CEO …
1.05:1
#000000
on
#080808
needs 4.5:1 (normal text)
16px · top of page (header area)
span Mission / …
1.05:1
#000000
on
#080808
needs 4.5:1 (normal text)
16px · above the fold
a Creator Stories
1.05:1
#000000
on
#080808
needs 4.5:1 (normal text)
16px · above the fold
a Products & Services
1.05:1
#000000
on
#080808
needs 4.5:1 (normal text)
16px · above the fold
button News
1.04:1
#000000
on
#070707
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Cookie Preference Ce…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manage Consent Prefe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie List21.00:13.0:1
#000000
#FFFFFF
Pass
title Sony Corporation - H…1.00:14.5:1
#000000
#000000
Fail
button Corporate Informatio…1.00:14.5:1
#000000
#000000
Fail
span Corporate …1.05:14.5:1
#000000
#080808
Fail
span CEO …1.05:14.5:1
#000000
#080808
Fail
span Mission / …1.05:14.5:1
#000000
#080808
Fail
a Creator Stories1.05:14.5:1
#000000
#080808
Fail
a Products & Services1.05:14.5:1
#000000
#080808
Fail
button News1.04:14.5:1
#000000
#070707
Fail
span News …21.00:14.5:1
#000000
#FFFFFF
Pass
span Important …21.00:14.5:1
#000000
#FFFFFF
Pass
button Sustainability21.00:14.5:1
#000000
#FFFFFF
Pass
span Sustainability21.00:14.5:1
#000000
#FFFFFF
Pass
span Environment21.00:14.5:1
#000000
#FFFFFF
Pass
span Accessibility21.00:14.5:1
#000000
#FFFFFF
Pass
span Diversity21.00:14.5:1
#000000
#FFFFFF
Pass
span Social Contribution21.00:14.5:1
#000000
#FFFFFF
Pass
option All21.00:14.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.

A+
Alt Text Quality
All 37 images OK
PASS
All 37 images OK
Info::
35 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
37 images 2 good alt text 35 decorative
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 31 passed
PASS
100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SonyEarthDay2026SpecialPage Sony Earth Day 2026 Special Page div.cp-home-hero-2026-hero__content-wrapper > div.cp-home-hero-2026-hero__content > div.cp-home-hero-2026-hero__items > a.cp-home-hero-2026-hero__item
○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
●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
●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○`<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.
○Identical links have the same purpose.
○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.

Send Feedback