Skip to content
https://kyoto-u.ac.jp

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #00205b
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link detected
Info::
6 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 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
24 headings
REVIEW
24 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 グローバルナビゲーション
  • H2 ヘッダー プライマリーリンク
  • H2 ヘッダー セカンダリーリンク
  • H3 海外向け研究プロモーション動画「KyotoU Future Commons」を公開しました
  • H3 令和8年度学部入学式を挙行しました
  • H3 令和8年度大学院入学式を挙行しました
  • H3 広報誌「紅萠」第49号を刊行しました
  • H3 魚研究から“ラオス料理人”へ。現地で出会った「タマサート」とは？
  • H3 北川進 理事・副学長、高等研究院特別教授がノーベル賞授賞式に出席しました
  • H3 北極域の氷河前縁は “ご馳走スポット”
  • H2 Announcements
  • H3 国際卓越研究大学の認定候補に選定されました
  • H3 ウクライナ情勢への対応
  • H2 Latest research news
  • H2 磁性材料のエネルギー損失に潜む「熱ゆらぎ」を説明可能AIで解明～エントロピーの効果を世界初で可視化、新材料の設計指針を提示～
  • H2 膵β細胞が増えるための新しいしくみを解明―ストレスへの適応が生存と増殖をうまく調整―
  • H2 高齢者虐待を防ぐ手がかりは“子ども時代”にある？―子ども期のポジティブな体験の多さが将来の加害リスクの低さと関連―
  • H2 サルの好奇心：「ほどよく不確実」な刺激を自ら探索する―飼育動物向けビデオゲーム開発にもつながる知見―
  • H2 KyotoU News
  • H2 Upcoming Events
  • H2 Features
  • H2 フッター プライマリーリンク
  • H2 フッター セカンダリーリンク
  • H2 フッター スペシャルリンク

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
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title ページが見つかりません | 京都大学 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h2 ヘッダー プライマリーリンク
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ヘッダー セカンダリーリンク
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Announcements
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest research news
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 KyotoU News
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Upcoming Events
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Features
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 フッター プライマリーリンク
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 フッター セカンダリーリンク
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 フッター スペシャルリンク
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
24px · bottom of viewport
h3 海外向け研究プロモーション…
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 令和8年度学部入学式を挙行し…
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 令和8年度大学院入学式を挙行…
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 広報誌「紅萠」第49号を刊行…
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 魚研究から“ラオス料理人”…
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 北川進 理事・副学長、高等研…
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 北極域の氷河前縁は “ご馳走…
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 国際卓越研究大学の認定候補…
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ウクライナ情勢への対応
1.36:1
#000000
on
#00205B
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 グローバルナ…15.14:13.0:1
#000000
#D9DBDE
Pass
h2 ヘッダー プラ…1.36:13.0:1
#000000
#00205B
Fail
h2 ヘッダー セカ…1.36:13.0:1
#000000
#00205B
Fail
h2 Announcements1.36:13.0:1
#000000
#00205B
Fail
h2 Latest research news1.36:13.0:1
#000000
#00205B
Fail
h2 KyotoU News1.36:13.0:1
#000000
#00205B
Fail
h2 Upcoming Events1.36:13.0:1
#000000
#00205B
Fail
h2 Features1.36:13.0:1
#000000
#00205B
Fail
h2 フッター プラ…1.36:13.0:1
#000000
#00205B
Fail
h2 フッター セカ…1.36:13.0:1
#000000
#00205B
Fail
h2 フッター スペ…1.36:13.0:1
#000000
#00205B
Fail
h3 海外向け研究…1.36:13.0:1
#000000
#00205B
Fail
h3 令和8年度学部…1.36:13.0:1
#000000
#00205B
Fail
h3 令和8年度大学…1.36:13.0:1
#000000
#00205B
Fail
h3 広報誌「紅萠…1.36:13.0:1
#000000
#00205B
Fail
h3 魚研究から“…1.36:13.0:1
#000000
#00205B
Fail
h3 北川進 理事・…1.36:13.0:1
#000000
#00205B
Fail
h3 北極域の氷河…1.36:13.0:1
#000000
#00205B
Fail
h3 国際卓越研究…1.36:13.0:1
#000000
#00205B
Fail
h3 ウクライナ情…1.36:13.0:1
#000000
#00205B
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.

A
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "block-global-navigation-menu" MAIN 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
1 of 31 images have issues
PASS
1 of 31 images have issues
Warning::
1 image(s) with generic alt text
Info::
8 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
31 images 22 good alt text 8 decorative 1 generic
IssueCount
generic1 image(s)
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">
Info::
2 control(s) properly labeled
3 controls
2 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
search-typeradionone
search-typeradionone
qsearch(Search...)placeholder only

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

<input type="search" 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

A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_DnnCR_0XCteU8WvaNL-jo14D2nu2j84JVvukSFvThBM.css?delta=4&language=ja&theme=camphor&include=eJxlzksOwyAMBNALkXCkyIAFNAYjDEnp6ftJky66sTxPsjUWUglctSc2QJO0QTF7Zb9M6MGOP87scKIo7RKh6FAC78oSiAxtQPDcE4qARznz-1xZrqhd7QVohhvcD8hcE1B8oFr74kCCYahOr326giIY3NvioljesA7NGS2TKlDBVyhBzr8_mXsu3bwqB3RKhjRMR8Ut4i76M-fErhM-AX5Hawk
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/default/files/css/css_DnnCR_0XCteU8WvaNL-jo14D2nu2j84JVvukSFvThBM.css?delta=4&language=ja&theme=camphor&include=eJxlzksOwyAMBNALkXCkyIAFNAYjDEnp6ftJky66sTxPsjUWUglctSc2QJO0QTF7Zb9M6MGOP87scKIo7RKh6FAC78oSiAxtQPDcE4qARznz-1xZrqhd7QVohhvcD8hcE1B8oFr74kCCYahOr326giIY3NvioljesA7NGS2TKlDBVyhBzr8_mXsu3bwqB3RKhjRMR8Ut4i76M-fErhM-AX5Hawk ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 28 passed
PASS
97

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
Copyright © Kyoto University. All Rights Reserved. div.layout-page > footer.layout-footer > p.layout-copyright > small

These are opportunities to improve the legibility of your content.

○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
●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.
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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.
○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
○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