Skip to content
https://naver.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
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::
1 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 1 <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
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 네이버 :: 페이지를 찾을 수 없습니다. ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Lighthouse Accessibility Audits
Action
Score 72/100 — 8 failing, 20 passed
REVIEW
72

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
추천 뉴스 엔터 스포츠 쇼핑 경제 클립 패션뷰티 여행맛집 카테크 지식 리빙푸드 건강 게임 웹툰 우리동네 판 관리 바로가기 nav#NAV > div.nav_scroll_wrap > div#NAV_LIST > ul.nav_list

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
하락 0.01% li.chq_loop_item > div.chq_weather_side > a.chq_stock > span.chqs_gap
챌린지 모음 div.cc_title_wrap > h3.cc_title > span.cc_main > em.comp_em
로그인 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link
전체서비스 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link
PC버전 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link
이용약관 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link
개인정보처리방침 div.mf_info_wrap > div.mf_info > a.mf_info_link > strong
고객센터 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
휘슬😙👌 노크✊ 챌린지 모음 div.grid1 > div.comp_common_feed > div.cc_title_wrap > h3.cc_title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.chf_link_thumb > div.chf_grid_big > div.chf_grid_mw > img.chf_img a.chf_link_thumb > div.chf_grid_big > div.chf_grid_mw > img.chf_img
div.chf_grid_big > div.chf_grid_mw > div.chf_vw_box > img.chf_img div.chf_grid_big > div.chf_grid_mw > div.chf_vw_box > img.chf_img
a.chf_link_thumb > div.chf_grid_big > div.chf_grid_mw > img.chf_img a.chf_link_thumb > div.chf_grid_big > div.chf_grid_mw > img.chf_img
div.chf_grid_big > div.chf_grid_mw > div.chf_vw_box > img.chf_img div.chf_grid_big > div.chf_grid_mw > div.chf_vw_box > img.chf_img
a.chf_link_thumb > div.chf_grid_big > div.chf_grid_mw > img.chf_img a.chf_link_thumb > div.chf_grid_big > div.chf_grid_mw > img.chf_img

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.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb
div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb
div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb
div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb
div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_thumb > a.chf_link_thumb
ul.native_scroll_list > li.cnb_channel_item > div.cnb_channel_mw > a.cnb_link_channel ul.native_scroll_list > li.cnb_channel_item > div.cnb_channel_mw > a.cnb_link_channel
ul.native_scroll_list > li.cnb_channel_item > div.cnb_channel_mw > a.cnb_link_channel ul.native_scroll_list > li.cnb_channel_item > div.cnb_channel_mw > a.cnb_link_channel
ul.native_scroll_list > li.cnb_channel_item > div.cnb_channel_mw > a.cnb_link_channel ul.native_scroll_list > li.cnb_channel_item > div.cnb_channel_mw > a.cnb_link_channel
ul.native_scroll_list > li.cnb_channel_item > div.cnb_channel_mw > a.cnb_link_channel ul.native_scroll_list > li.cnb_channel_item > div.cnb_channel_mw > a.cnb_link_channel

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

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
난자로 플러팅하는 40대 누나 div.chf_feed_card > div.chf_feed_wrap > div.chf_feed_info > a.chf_link_info
로그인 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link
전체서비스 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link
PC버전 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link
이용약관 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link
개인정보처리방침 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link
고객센터 footer > div.mf_info_wrap > div.mf_info > a.mf_info_link

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.web html.web

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
●`[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
●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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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.
○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
○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
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV "주요 서비스" MAIN ASIDE "웨일 브라우저 설치 안내" 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
Heading Hierarchy
5 headings, 1 skip(s)
PASS
5 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 NAVER
  • H3 공지사항 skipped
  • H3 Partners
  • H3 Developers
  • H3 네이버 정책 및 약관

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
All 50 images OK
PASS
All 50 images OK
Info::
22 decorative image(s) correctly marked
Info::
28 image(s) with good alt text
50 images 28 good alt text 22 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 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="query" id="query">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#querysearch(검색어를 입력해 주세요.)placeholder only

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

<input type="search" name="query" id="query">

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+
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)
ElementRatioRequiredFGBGResult
h3 Partners21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Developers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 네이버 정책 및…21.00:13.0:1
#000000
#FFFFFF
Pass
title NAVER19.92:14.5:1
#000000
#F8F9FA
Pass
span 상단영역 바로…20.61:14.5:1
#000000
#FCFDFD
Pass
span 서비스 메뉴 바…21.00:14.5:1
#000000
#FFFFFF
Pass
span 새소식 블록 바…21.00:14.5:1
#000000
#FFFFFF
Pass
span 쇼핑 블록 바로…21.00:14.5:1
#000000
#FFFFFF
Pass
span 관심사 블록 바…14.41:14.5:1
#000000
#9AE6BB
Pass
span MY 영역 바로가…21.00:14.5:1
#000000
#FFFFFF
Pass
span 위젯 보드 바로…21.00:14.5:1
#000000
#FFFFFF
Pass
span 보기 설정 바로…19.09:14.5:1
#000000
#F4F4F4
Pass
div 네이버가 만든 …19.03:14.5:1
#000000
#F3F4F2
Pass
a 웨일 설치19.04:14.5:1
#000000
#EBF8E0
Pass
span 배너 닫기19.03:14.5:1
#000000
#E2FCCC
Pass
span NAVER21.00:14.5:1
#000000
#FFFFFF
Pass
legend 검색21.00:14.5:1
#000000
#FFFFFF
Pass
span 검색20.31:14.5:1
#000000
#FBFBFC
Pass
span 입력도구19.92:14.5:1
#000000
#F8F9FA
Pass
span 자동완성/최근…21.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback