Skip to content
https://dental-ortho.info

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 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
Info::
No banner (header) landmark
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 (missing!) 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

D
Mobile-Readable Font Sizes
Action
50% of visible text renders at >= 12 CSS px (52 below threshold)
FIX
50% of visible text renders at >= 12 CSS px (52 below threshold)
Warning::
52 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("0755"); <span> 11.0px ("8.5K"); <span> 10.0px ("0755"); <span> 11.0px ("1K"); <span> 10.0px ("0755").
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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 ✗
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.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file" id="upf">; <textarea id="ed">
2 controls
0 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#upffile(none)none
#edtextarea(none)none

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

<input type="file" id="upf">; <textarea id="ed">

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

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::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title ページが見つかりませんでした – 歯並び矯正.info ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
span /home/adinnovative1/www/dentalortho
1.84:1
#000000
on
#303953
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
button UPLOAD
1.84:1
#000000
on
#303953
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

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)
ElementRatioRequiredFGBGResult
h1 歯並び矯正で…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 経験豊富な歯…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 歯並び矯正を…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 マウスピース…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 経験による歯…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 歯並び矯正で…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 丁寧な説明21.00:13.0:1
#000000
#FFFFFF
Pass
h3 親しみやすい21.00:13.0:1
#000000
#FFFFFF
Pass
h3 安易に削らな…21.00:13.0:1
#000000
#FFFFFF
Pass
span /home/adinnovative1/…1.84:14.5:1
#000000
#303953
Fail
button UPLOAD1.84:14.5:1
#000000
#303953
Fail
span [DIR] wp-includes21.00:14.5:1
#000000
#FFFFFF
Pass
span 075521.00:14.5:1
#000000
#FFFFFF
Pass
span 8.5K21.00:14.5:1
#000000
#FFFFFF
Pass
span [DIR] wp-content21.00:14.5:1
#000000
#FFFFFF
Pass
span 075521.00:14.5:1
#000000
#FFFFFF
Pass
span [DIR] wp-admin21.00:14.5:1
#000000
#FFFFFF
Pass
span 07558.63:14.5:1
#000000
#A2A6B2
Pass
span [ ] .htaccess21.00:14.5:1
#000000
#FFFFFF
Pass
span 060421.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.

B
Lighthouse Accessibility Audits
Score 86/100 — 3 failing, 14 passed
REVIEW
86

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
UP body.home > div.hd > button.btn
[DIR] wp-includes body.home > div#lst > div.it > span.n
8.5K body.home > div#lst > div.it > span.s
[DIR] wp-content body.home > div#lst > div.it > span.n
1K body.home > div#lst > div.it > span.s
[DIR] wp-admin body.home > div#lst > div.it > span.n
3K body.home > div#lst > div.it > span.s
[ ] .htaccess body.home > div#lst > div.it > span.n
0.2K body.home > div#lst > div.it > span.s
[ ] ammika.php body.home > div#lst > div.it > span.n
28.15K body.home > div#lst > div.it > span.s
[ ] google3a8070af884e22a6.html body.home > div#lst > div.it > span.n
0.05K body.home > div#lst > div.it > span.s
[ ] index.php body.home > div#lst > div.it > span.n
23.89K body.home > div#lst > div.it > span.s
[ ] license.txt body.home > div#lst > div.it > span.n
19.44K body.home > div#lst > div.it > span.s
[ ] readme.html body.home > div#lst > div.it > span.n
7.23K body.home > div#lst > div.it > span.s
[ ] robots.txt body.home > div#lst > div.it > span.n
0.27K body.home > div#lst > div.it > span.s
[ ] saiga.php body.home > div#lst > div.it > span.n
16.47K body.home > div#lst > div.it > span.s
[ ] wp-activate.php body.home > div#lst > div.it > span.n
7.2K body.home > div#lst > div.it > span.s
[ ] wp-blog-header.php body.home > div#lst > div.it > span.n
0.34K body.home > div#lst > div.it > span.s
[ ] wp-cli.local.yml body.home > div#lst > div.it > span.n
0.03K body.home > div#lst > div.it > span.s
[ ] wp-comments-post.php body.home > div#lst > div.it > span.n
2.27K body.home > div#lst > div.it > span.s
[ ] wp-config-sample.php body.home > div#lst > div.it > span.n
3.26K body.home > div#lst > div.it > span.s
[ ] wp-config.php body.home > div#lst > div.it > span.n
4.13K body.home > div#lst > div.it > span.s
[ ] wp-cron.php body.home > div#lst > div.it > span.n
5.49K body.home > div#lst > div.it > span.s
[ ] wp-links-opml.php body.home > div#lst > div.it > span.n
2.43K body.home > div#lst > div.it > span.s
[ ] wp-load.php body.home > div#lst > div.it > span.n
3.84K body.home > div#lst > div.it > span.s
[ ] wp-login.php body.home > div#lst > div.it > span.n
50.63K body.home > div#lst > div.it > span.s
[ ] wp-mail.php body.home > div#lst > div.it > span.n
8.52K body.home > div#lst > div.it > span.s
[ ] wp-settings.php body.home > div#lst > div.it > span.n
31.88K body.home > div#lst > div.it > span.s
[ ] wp-signup.php body.home > div#lst > div.it > span.n
33.81K body.home > div#lst > div.it > span.s
[ ] wp-trackback.php body.home > div#lst > div.it > span.n
5.09K body.home > div#lst > div.it > span.s
[ ] xmlrpc.php body.home > div#lst > div.it > span.n
3.13K body.home > div#lst > div.it > span.s
歯並び矯正でオススメの 経験豊富な歯科医院 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h1.elementor-heading-title
歯並び矯正を考えている方へ div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title
マウスピース矯正とは div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title
歯並び矯正で大切なのは div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title
経験による歯の動きの予測 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title
歯並びの矯正治療は、長期間に渡り少しずつ歯の位置を動かして整える治療方法です。 特に、子供の歯並び矯正は成長に伴う歯の動きを予測して進めていく必要があります。… div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p
丁寧な説明 div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title
親しみやすい div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title
安易に削らない div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title
当サイトでは平成30年6月1日に施行された改正医療法に基づき、皆さまの判断材料の一助になればと掲載していた「口コミ（体験談）」につきまして、掲載を削除いたしま… div.elementor-column > div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container
【理由】体験談は患者様毎の状態により感想も異なることから、読んだ方に誤認を与える恐れがあるとの見解が厚生労働省より方に示されたため。 div.elementor-column > div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container
© Yoboushika info div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p.elementor-heading-title

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.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon

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.

○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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+
Heading Hierarchy
9 headings
PASS
9 headings
Info::
Single H1 present
  • H1 歯並び矯正でオススメの 経験豊富な歯科医院
  • H2 歯並び矯正を考えている方へ
  • H2 マウスピース矯正とは
  • H3 歯並び矯正で大切なのは
  • H2 経験による歯の動きの予測
  • H3 丁寧な説明
  • H3 親しみやすい
  • H3 安易に削らない
  • H4 ※ 口コミ(体験談)の紹介について
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
9 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 9 all-caps heading(s)
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
8 decorative image(s) correctly marked
8 images 8 decorative
All images have appropriate alt text.
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "ja"
PASS
Lang attribute set to "ja"
Info::
<html lang="ja"> is set and valid
Got: ja
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback