Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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 ✗

Link & Button Quality

Action

10 issue(s) across 143 links and 37 buttons

REVIEW

10 issue(s) across 143 links and 37 buttons

1 link(s) with generic text

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

Got: https://global.fujitsu/ja-jp/ ("Website")

7 link(s) open in new tab without warning

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

Got: https://twitter.com/Fujitsu_Global; https://www.facebook.com/FujitsuICT; https://www.youtube.com/FujitsuTS; https://www.linkedin.com/company/fujitsu; https://www.fujitsu.com/global/about/resources/privacy/; https://www.fujitsu.com/global/about/resources/privacy/; https://www.onetrust.com/products/cookie-consent/

9 button(s) with no accessible text

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

Got: button.c-close (#157 on page); button.c-search__close (#178 on page); button.c-close (#271 on page); button.c-close (#413 on page); button.c-close (#461 on page); button.c-menu (#481 on page); button.c-close (#485 on page); button (#1505 on page); button (#1517 on page)

135 link(s) with descriptive text

143 links

0 empty

1 generic text

7 new tab

9 empty buttons

Element	Text	Issue	Suggested Fix
https://global.fujitsu/ja-jp/	Website	generic text	Replace with descriptive text
Before: Website Suggested: Ja Jp
https://twitter.com/Fujitsu_Global	X	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/FujitsuICT	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/FujitsuTS	YouTube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/fujitsu	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.fujitsu.com/global/about/res…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.fujitsu.com/global/about/res…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<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
<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
<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

163 links and buttons have descriptive text

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

https://global.fujitsu/ja-jp/ ("Website")

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://twitter.com/Fujitsu_Global; https://www.facebook.com/FujitsuICT; https://www.youtube.com/FujitsuTS; https://www.linkedin.com/company/fujitsu; https://www.fujitsu.com/global/about/resources/privacy/; https://www.fujitsu.com/global/about/resources/privacy/; https://www.onetrust.com/products/cookie-consent/

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.c-close (#157 on page); button.c-search__close (#178 on page); button.c-close (#271 on page); button.c-close (#413 on page); button.c-close (#461 on page); button.c-menu (#481 on page); button.c-close (#485 on page); button (#1505 on page); button (#1517 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

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | Fujitsu Global ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Landmark Structure

15 landmarks

PASS

15 landmarks

<main> landmark present

8 <nav> landmark(s) found

5 of 8 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

15 headings, 1 skip(s)

PASS

15 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Fujitsu across the World
H3 Japan skipped
H2 Main Office
H3 Other offices
H3 Americas
H3 Asia Pacific
H3 Europe
H3 Other countries
H2 Privacy Preference Centre
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Sale of Personal Data
H5 Performance Cookies
H5 Targeting Cookies
H3 Cookie List

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+

Alt Text Quality

1 of 22 images have issues

PASS

1 of 22 images have issues

1 image(s) with generic alt text

21 image(s) with good alt text

22 images 21 good alt text 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

All 8 controls labeled

PASS

All 8 controls labeled

8 control(s) properly labeled

8 controls

8 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	search		none
q	search		none
#ot-group-id-SPD_BG	checkbox	Sale of Personal Data	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Main Office	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Privacy Preference C…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Japan	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Other offices	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Americas	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Asia Pacific	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Europe	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Other countries	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Manage Consent Prefe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Cookie List	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Locations \| Fujitsu …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span This is a skip link …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button About us	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a About Fujitsu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Our Business	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Locations	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Fujitsu Blog	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Customer stories	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Events	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Co-creation with sta…	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 29 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
Privacy Policy `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●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

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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