Skip to content
https://xrea.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark 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 MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
favicon.ico Missing
PNG Icons Present
Apple Touch Present
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
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
23 headings, 1 skip(s)
REVIEW
23 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 XREA(エクスリア)| 無料レンタルサーバー
  • H1 無料から使える高機能・高品質レンタルサーバー XREA(エクスリア) duplicate H1
  • H4 PICK UP skipped
  • H3 XREA Free(無料プラン)
  • H3 XREA Plus(有料プラン)
  • H3 Mail&Backup
  • H3 (empty)
  • H2 (empty)
  • H3 Webサイト全面リニューアル
  • H3 全プラン最新のCPU、SSDに対応
  • H3 コントロールパネルを刷新
  • H4 従来の基本機能もそのまま使うことができます
  • H2 運用と安定にこだわったXREA4つの特徴
  • H3 シンプルな料金プラン
  • H3 無料お試し10日間
  • H3 SNI SSL対応
  • H3 万全のサポート体制
  • H2 お知らせ
  • H2 障害情報
  • H3 ドメイン関連サービス
  • H3 サーバー/クラウドサービス
  • H3 その他のサービス
  • H3 サポート

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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
Alt Text Quality
Action
6 of 44 images have issues
REVIEW
6 of 44 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with filename as alt text
Warning::
3 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
37 image(s) with good alt text
44 images 37 good alt text 1 decorative 4 generic 2 missing
IssueCount
missing2 image(s)
filename1 image(s)
generic3 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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 404 Not Found | 無料から使えるレンタルサーバー【 XREA(エクスリア)】 Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h1 XREA
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
32px · top of page (header area) · over background image/gradient

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
h1 XREA1.13:13.0:1
#000000
#131313
Fail
h1 | 無料レンタ…7.28:13.0:1
#000000
#989898
Pass
h1 無料から使え…18.76:13.0:1
#000000
#F2F2F2
Pass
h2 運用と安定に…18.76:13.0:1
#000000
#F2F2F2
Pass
h2 4つの特徴18.76:13.0:1
#000000
#F2F2F2
Pass
h2 お知らせ18.76:13.0:1
#000000
#F2F2F2
Pass
h2 障害情報18.76:13.0:1
#000000
#F2F2F2
Pass
h3 XREA Free18.76:13.0:1
#000000
#F2F2F2
Pass
h3 XREA Plus18.76:13.0:1
#000000
#F2F2F2
Pass
h3 Mail&Backup18.76:13.0:1
#000000
#F2F2F2
Pass
h3 Webサイト全面…18.76:13.0:1
#000000
#F2F2F2
Pass
h3 全プラン最新…18.76:13.0:1
#000000
#F2F2F2
Pass
h3 コントロール…18.76:13.0:1
#000000
#F2F2F2
Pass
h3 シンプルな料…18.76:13.0:1
#000000
#F2F2F2
Pass
h3 無料お試し10日…18.76:13.0:1
#000000
#F2F2F2
Pass
h3 SNI SSL対応18.76:13.0:1
#000000
#F2F2F2
Pass
h3 万全のサポー…18.76:13.0:1
#000000
#F2F2F2
Pass
h3 ドメイン関連…18.76:13.0:1
#000000
#F2F2F2
Pass
h3 サーバー/ク…18.76:13.0:1
#000000
#F2F2F2
Pass
h3 その他のサー…18.76:13.0:1
#000000
#F2F2F2
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 18 passed
REVIEW
84

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.wrap > div.set-area__txt > p > span.red
月額390円~のドメインセットプランを見る div.set-area > div.wrap > div.set-area__btn > a#xrea_top_setarea
【コアサーバーV2プラン20%OFF】春のスタートダッシュキャンペーン ul.main_pickup_box > li > p.main_pickup_txt > a#xrea_top_pickup02
【コアサーバーV2プラン料金1年間無料!】ビジネス応援キャンペーン ul.main_pickup_box > li > p.main_pickup_txt > a#xrea_top_pickup03
PHP8.4 / PHP8.5 対応完了のお知らせ ul.main_pickup_box > li > p.main_pickup_txt > a#xrea_top_pickup01
現在の仕様はこちら li > ul.link_list > li > a#xrea_top_brandnew_point
料金表はこちら div.feature_list_block > ul.link_list > li > a#xrea_top_feature_price
無料アカウントの作成はこちら div.feature_list_block > ul.link_list > li > a#xrea_top_feature_signup
仕様ページはこちら div.feature_list_block > ul.link_list > li > a#xrea_top_feature_spec
サポートページはこちら div.feature_list_block > ul.link_list > li > a#xrea_top_feature_support
【コアサーバーV2プラン20%OFF】春のスタートダッシュキャンペーン div.information_left > dl.information_list > dd > a
【選べる2つのレンタルサーバーが30%OFF】30周年 3連勝・感謝キャンペーン div.information_left > dl.information_list > dd > a
【コアサーバーV2プラン料金1年間無料!】ビジネス応援キャンペーン div.information_left > dl.information_list > dd > a
PHP8.4 / PHP8.5 対応完了のお知らせ div.information_left > dl.information_list > dd > a
お知らせ一覧 div.information_left > ul.link_list > li > a#xrea_top_information_more
緊急メンテナンス div.information_right > dl.information_list > dd > a
緊急メンテナンス div.information_right > dl.information_list > dd > a
緊急メンテナンス div.information_right > dl.information_list > dd > a
緊急メンテナンス div.information_right > dl.information_list > dd > a
緊急メンテナンス div.information_right > dl.information_list > dd > a
緊急メンテナンス div.information_right > dl.information_list > dd > a
メンテナンス・障害情報 div.information_right > ul.link_list > li > a#xrea_top_information_mainte
管理画面とIP・仕様 div.information_right > ul.link_list > li > a#xrea_top_information_ip
XREA(エクスリア)はユーザー側で自由に設定をカスタマイズできる、高い機能性を持った無料から使えるレンタルサーバーです。最新のCPUとSSD搭載で高速化を実… div.footer_block_top > div.footer_center > div.footer_center_inner > p
© XREA All rights reserved. div.bottomBox > div.detail > p.copyright > small

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
body#top > a.hamburger body#top > a.hamburger
div.gmoGroupHeader > div.gmoGroupHeader_logo > div.gmoGroupHeader_3wins > a div.gmoGroupHeader > div.gmoGroupHeader_logo > div.gmoGroupHeader_3wins > 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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

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
無料診断 div.gmoGroupHeader > div.gmoGroupHeader_secCont > div.gmoGroupHeader_sec > a
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>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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
`<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
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.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Heading elements appear in a sequentially-descending order
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
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
`[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
Buttons have an accessible name
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 a valid value for its `[lang]` attribute
`<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
`<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.
`<td>` elements in a large `<table>` have one or more table headers.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
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.

Send Feedback