Skip to content
https://kakao.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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.
Page Structure — as a screen reader sees it
BANNER header NAV 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

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

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

0 pass 20 fail WCAG AA
h2 메인메뉴
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · above the fold
h2 메인메뉴
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 홈 본문
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 하단 메뉴
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 서비스 이용정보
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h3 카카오최근소식
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 카카오최근소식
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 서비스 바로가기
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 카카오의 다양한 모습
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 바로가기
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 더 나은 세상을 만드는
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 카카오 서비스
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
h3 오늘의 카카오
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
19px · bottom of viewport
title 카카오
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
a 본문 바로가기
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
a 메뉴 바로가기
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
span KaKao
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · top of page (header area)
button 소개
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · above the fold
a 카카오 문화
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · above the fold
a 카카오그룹
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 메인메뉴1.11:13.0:1
#000000
#111111
Fail
h2 메인메뉴1.11:13.0:1
#000000
#111111
Fail
h2 홈 본문1.11:13.0:1
#000000
#111111
Fail
h2 하단 메뉴1.11:13.0:1
#000000
#111111
Fail
h2 서비스 이용정…1.11:13.0:1
#000000
#111111
Fail
h3 카카오최근소…1.11:13.0:1
#000000
#111111
Fail
h3 카카오최근소…1.11:13.0:1
#000000
#111111
Fail
h3 서비스 바로가…1.11:13.0:1
#000000
#111111
Fail
h3 카카오의 다양…1.11:13.0:1
#000000
#111111
Fail
h3 바로가기1.11:13.0:1
#000000
#111111
Fail
h3 더 나은 세상을…1.11:13.0:1
#000000
#111111
Fail
h3 카카오 서비스1.11:13.0:1
#000000
#111111
Fail
h3 오늘의 카카오1.11:13.0:1
#000000
#111111
Fail
title 카카오1.11:14.5:1
#000000
#111111
Fail
a 본문 바로가기1.11:14.5:1
#000000
#111111
Fail
a 메뉴 바로가기1.11:14.5:1
#000000
#111111
Fail
span KaKao1.11:14.5:1
#000000
#111111
Fail
button 소개1.11:14.5:1
#000000
#111111
Fail
a 카카오 문화1.11:14.5:1
#000000
#111111
Fail
a 카카오그룹1.11:14.5:1
#000000
#111111
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 26 passed
REVIEW
89

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 > div > a.item_service > span.info_service
좋은 곳을 함께 찾아가는 지도, 카카오맵 div > div > a.item_service > span.info_service
더 편한 모바일 생활의 시작, 카카오톡 채널 div > div > a.item_service > span.info_service
이용약관 section.section_relation > div.group_info > div.wrap_info > a.link_info
운영정책 및 제안 section.section_relation > div.group_info > div.wrap_info > a.link_info
청소년보호정책 새창열림 div.group_info > div.wrap_info > a.link_info > span
접근성 안내 새창열림 div.group_info > div.wrap_info > a.link_info > span
브랜드보호정책 새창열림 div.group_info > div.wrap_info > a.link_info > span
권리침해신고안내 새창열림 div.group_info > div.wrap_info > a.link_info > span
공지사항 section.section_relation > div.group_info > div.wrap_info > a.link_info
사이버윤리실 새창열림 div.group_info > div.wrap_info > a.link_info > span
Contact Us 새창열림 div.group_info > div.wrap_info > a.link_info > span
© Kakao Corp. All rights reserved. footer.doc-footer > div.inner_footer > section.section_relation > small.txt_copyright
Kakao Corp. div.inner_footer > section.section_relation > small.txt_copyright > a

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
닫기 section#mainContent > div.wrap_search > div.inner_search > button.btn_close

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-*]` 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
●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
●Elements with the `role=text` attribute do not have focusable descendents.
●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
●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
○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
○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.
○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
○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
12 headings
PASS
12 headings
Info::
Single H1 present
  • H1 KaKao
  • H2 메인메뉴
  • H2 메인메뉴
  • H2 홈 본문
  • H3 카카오최근소식
  • H3 카카오최근소식
  • H3 서비스 바로가기
  • H3 카카오의 다양한 모습바로가기
  • H3 더 나은 세상을 만드는카카오 서비스
  • H2 하단 메뉴
  • H3 오늘의 카카오
  • H2 서비스 이용정보
A+
Alt Text Quality
All 46 images OK
PASS
All 46 images OK
Info::
32 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
46 images 14 good alt text 32 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#inpSearchEtctext검색어for/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback