Skip to content
https://yna.co.kr

Accessibility

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

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

F
404 Error Page
Action
HTTP 400, bare page
FIX
HTTP 400, bare page
Warning::
Unexpected status code: HTTP 400
Expected HTTP 404 but received 400. This may confuse search engine crawlers.
Got: HTTP 400
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 400 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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
Alt Text Quality
1 of 112 images have issues
REVIEW
1 of 112 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
110 image(s) with good alt text
112 images 110 good alt text 1 missing
IssueCount
missing1 image(s)
too long1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

C
Form Accessibility
Action
9 of 10 controls have issues
REVIEW
9 of 10 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>
Info::
1 control(s) properly labeled
10 controls
1 labeled
0 placeholder only
9 unlabeled
ControlTypeLabelMethod
#keywordSrch01text통합 검색for/id
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none

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

<select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>

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
Favicon & Branding
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
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA
a 메뉴 바로가기
2.36:1
#000000
on
#5A444A
needs 4.5:1 (normal text)
16px · top of page (header area)
span 광고
3.89:1
#000000
on
#796474
needs 4.5:1 (normal text)
16px · above the fold
a English
3.87:1
#000000
on
#7B6373
needs 4.5:1 (normal text)
16px · above the fold
a 中文
2.31:1
#000000
on
#5B4245
needs 4.5:1 (normal text)
16px · above the fold
a 日本語
2.55:1
#000000
on
#614948
needs 4.5:1 (normal text)
16px · above the fold
a عربي
2.82:1
#000000
on
#654F5B
needs 4.5:1 (normal text)
16px · above the fold
a Español
1.74:1
#000000
on
#453133
needs 4.5:1 (normal text)
16px · above the fold
a Français
1.82:1
#000000
on
#493431
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 연합뉴스13.21:13.0:1
#000000
#CDCDCD
Pass
h2 주요뉴스0313.21:13.0:1
#000000
#CDCDCD
Pass
title 연합뉴스21.00:14.5:1
#000000
#FFFFFF
Pass
a 연합뉴스21.00:14.5:1
#000000
#FFFFFF
Pass
a 본문 바로가기21.00:14.5:1
#000000
#FFFFFF
Pass
a 메뉴 바로가기2.36:14.5:1
#000000
#5A444A
Fail
span 광고3.89:14.5:1
#000000
#796474
Fail
a English3.87:14.5:1
#000000
#7B6373
Fail
a 中文2.31:14.5:1
#000000
#5B4245
Fail
a 日本語2.55:14.5:1
#000000
#614948
Fail
a عربي2.82:14.5:1
#000000
#654F5B
Fail
a Español1.74:14.5:1
#000000
#453133
Fail
a Français1.82:14.5:1
#000000
#493431
Fail
a Tiếng Việt21.00:14.5:1
#000000
#FFFFFF
Pass
strong 2026.04.2221.00:13.0:1
#000000
#FFFFFF
Pass
em (화)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 메뉴 열기21.00:14.5:1
#000000
#FFFFFF
Pass
a 최신뉴스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.

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 7 failing, 22 passed
REVIEW
77

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.content04 > h3 > a.title-type034 > strong.title01
연합뉴스 프리미엄 금융투자섹션 div.content04 > h3 > a.title-type034 > span.txt01
2.83% ul.list01 > li.infomax_stock_kospi200 > div.box > span.unit04
내 고향 살리는 1석3조 aside.aside-box410 > div.area01 > a > span.txt01
고향사랑기부 aside.aside-box410 > div.area01 > a > span.txt02
서미숙의 집수다 li > div.item-box01 > div.news-con > a.txt-tag41
이런말저런글 li > div.item-box01 > div.news-con > a.txt-tag41
글로컬 li > div.item-box01 > div.news-con > a.txt-tag41
인&아웃 li > div.item-box01 > div.news-con > a.txt-tag41
미세먼지보통 ul.list01 > li.swiper-slide > div.weather-today-info > strong.txt-dust
보통 li.swiper-slide > div.weather-today-info > strong.txt-dust > em.state02
12 div.btns-wrap11 > div.pager01 > span.count-box > span.txt-total

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#container > div.container501 > div.content04 > h3

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
div.area01 > div.ads-box > a > img div.area01 > div.ads-box > a > 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
aside.aside-box101 > div.area01 > div.ads-box > a aside.aside-box101 > div.area01 > div.ads-box > 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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
최신뉴스 정치 북한 경제 마켓+ 산업 사회 전국 세계 문화 건강 연예 스포츠 오피니언 비주얼뉴스 제보 재난포털 header.wrap-header02 > div.nav-type01 > nav#nav01 > ul#swiper-wrapper-ad3911015c27fb728
코스피 사상 최고치 마감…하이닉스는 '120만 닉스' 돌파 '마지막 국외 거주 유공자'…이하전 지사 유해 봉환 베트남 국빈방문…하노이 도착한 … section.box-type100 > div.list-type050 > div.swiper-area > ul#swiper-wrapper-7edbe12941ff2ab10
전체 사진 수 19 미·이란 협상 임박…경계 태세 강화하는 파키스탄 전체 사진 수 10 말레이시아 수상가옥 빈민촌에 큰불…집 1천여채 전소 전… section.box-type100 > div.list-type050 > div.swiper-area > ul#swiper-wrapper-ef106310cf10e3fbe96
영상 기사 [영상] 머스크의 선행?…'8개 질문' 남기고 떠난 소녀팬에 일일이 답변 재생시간 02:42 영상 기사 [영상] 美해군 6세대 함재… section.box-type100 > div.list-type021 > div.swiper-area > ul#swiper-wrapper-73d1cf635a158de5
미국·이란 전쟁 2342개의 뉴스 미국·이란 전쟁 유가·환율 급등 491개의 뉴스 유가·환율 급등 '학술용병' 논란 26개의 뉴스 '학술용병'… section.box-type101 > div.list-type051 > div.swiper-area > ul#swiper-wrapper-ac898158bb18b334
연합뉴스 연합뉴스 "컨디션 회복 중" 공개했는데…늑구, 식사영상에 쏟아진 반응 #shorts 재생시간 00:23 KOREA NOW KOREA … section.box-type101 > div.list-type032 > div.swiper-area > ul#swiper-wrapper-3aba1554995f27108
English Trump extends ceasefire with Iran amid uncertainty over prospects for p… section.box-type103 > div.list-type041 > div.swiper-area > ul#swiper-wrapper-3d9ed6f85071cbe0
강원일보 원주시장 후보 지지도 구자열 50.1%·원강수 34.7% 경북매일 주한미군사령관 “주한미군, 숫자보다 역량에 중점”…주둔병력 축소 의… section.box-type103 > div.list-type043 > div.swiper-area > ul#swiper-wrapper-105489efd2ab94481
English 中文 日文 عربي Español Français Tiếng Việt div#footer > section.footer-menu01 > div.lang-zone02 > ul#swiper-wrapper-555277926762310102

These are opportunities to improve the experience of reading tabular or list data using 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

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

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]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA input fields have accessible names
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●`[lang]` attributes have a valid value
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●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 `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○`<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.
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○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
30 headings, 1 skip(s)
PASS
30 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 연합뉴스
  • H3 마켓+연합뉴스 프리미엄 금융투자섹션 skipped
  • H3 핫뉴스
  • H3 포토
  • H3 화보
  • H3 영상
  • H3 브랜드뉴스
  • H3 연예
  • H3 스포츠
  • H2 주요뉴스03
  • H3 오피니언
  • H2 이슈
  • H3 많이 본 뉴스
  • H3 오래 머문 뉴스
  • H3 공감 많은 뉴스
  • H3 특파원 르포
  • H3 탐사 기획
  • H3 샷!
  • H3 오늘의 날씨
  • H3 팩트체크
  • H3 마켓+
  • H3 건강
  • H3 여행/레저
  • H3 youtube채널
  • H3 사람들
  • H3 다국어 톱뉴스
  • H3 지역지 톱뉴스
  • H3 로컬의 재발견
  • H3 전국 레이더
  • 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

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

Send Feedback