Skip to content
https://chosun.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
45
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
D
Alt Text Quality
Action
3 of 32 images have issues
FIX
3 of 32 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
12 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
32 images 17 good alt text 12 decorative 3 missing
IssueCount
missing3 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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
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 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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
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::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 68/100 — 8 failing, 20 passed
FIX
68

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Marketinng_banner_pc div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Marketinng_banner_pc div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Marketinng_banner_pc div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Marketinng_banner_pc div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Marketinng_banner_pc div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Marketinng_banner_pc div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
div.slick-slider > div.slick-list > div.slick-track > div.slick-slide div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
div.slick-slider > div.slick-list > div.slick-track > div.slick-slide div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
div.slick-slider > div.slick-list > div.slick-track > div.slick-slide div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
div.slick-slider > div.slick-list > div.slick-track > div.slick-slide div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
div.slick-slider > div.slick-list > div.slick-track > div.slick-slide div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
div.slick-slider > div.slick-list > div.slick-track > div.slick-slide div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
div.slick-slider > div.slick-list > div.slick-track > div.slick-slide div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
div.slick-slider > div.slick-list > div.slick-track > div.slick-slide div.slick-slider > div.slick-list > div.slick-track > div.slick-slide

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.carousel--controls > div > span > button div.carousel--controls > div > span > button
div.carousel--controls > div > span > button.btnActive div.carousel--controls > div > span > button.btnActive
div.carousel--controls > div > span > button div.carousel--controls > div > span > button
div.carousel--controls > div > span > button div.carousel--controls > div > span > button
div.carousel--controls > div > span > button.btnActive div.carousel--controls > div > span > button.btnActive
div.carousel--controls > div > span > button div.carousel--controls > div > span > button
div.carousel--controls > div > span > button div.carousel--controls > div > span > button

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.today-chosun-wrapper > div.today-chosun-box > div.left-item > img div.today-chosun-wrapper > div.today-chosun-box > div.left-item > img
div.today-chosun-wrapper > a.today-chosun-box > div.left-item > img div.today-chosun-wrapper > a.today-chosun-box > div.left-item > img
div.today-chosun-wrapper > a.today-chosun-box > div.left-item > img div.today-chosun-wrapper > a.today-chosun-box > div.left-item > 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.mem--home-banner > div.mem--home-banner__bar > div.menu-bar-wrapper > a.menu-bar-logo div.mem--home-banner > div.mem--home-banner__bar > div.menu-bar-wrapper > a.menu-bar-logo
div.width--100 > div.article-print-sty1 > div.article-print-sty2 > a div.width--100 > div.article-print-sty1 > div.article-print-sty2 > 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.

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.story-card > div.story-card-block > div.story-card-component > span
중국 과학계가 세계 최고 권위 미국 학회와 갈등을 빚으면서 미·중 패권 경쟁이 학계로까지 확장되고 있다. 중국 최대 과학계 단체가 미국 신경정… div.story-card > div.story-card-block > div.story-card-component > span
미국과 이란이 종전 합의에 다가서고 있다는 신호가 이어지면서 뉴욕 증시가 상승했다. 특히 대형주 위주의 S&P500 지수는 사상 처음(종가 기… div.story-card > div.story-card-block > div.story-card-component > span
도널드 트럼프 미국 대통령이 자신이 호르무즈 해협을 영구적으로 개방하고 있다며 “중국이 매우 기뻐하고 있다”고 했다. 다음 달 열릴 미·중 정… div.story-card > div.story-card-block > div.story-card-component > span
사설 div.story-card-component > a.story-card__headline > div.left__label__box > span.left__label
사설 div.story-card-component > a.story-card__headline > div.left__label__box > span.left__label
사설 div.story-card-component > a.story-card__headline > div.left__label__box > span.left__label
경제포커스 div.story-card-wrapper > div.story-card > div.story-card-block > div.story-card-component
기자의 시각 div.story-card-wrapper > div.story-card > div.story-card-block > div.story-card-component
윤희영의 News English div.story-card-wrapper > div.story-card > div.story-card-block > div.story-card-component
박찬용의 물건만담 div.story-card-wrapper > div.story-card > div.story-card-block > div.story-card-component
만물상 div.story-card-wrapper > div.story-card > div.story-card-block > div.story-card-component
전남 무안국제공항 일대에서 제주항공 여객기 참사 희생자들의 미수습 유해를 찾기 위한 재수색이 지난 13일부터 다시 시작됐다. 하지만 첫날 현장… div.story-card > div.story-card-block > div.story-card-component > span

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
"美 무기 사" 방위비 분담 압박… 'K-방산'의 씨앗 됐다 div.flex-chain-wrapper > section.flex-chain > div.flex-chain__column > li.related-links__item
"韓, 태평양 전초기지"… 한미동맹이 바꾼 美 군사 지도 div.flex-chain-wrapper > section.flex-chain > div.flex-chain__column > li.related-links__item

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 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-*]` 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
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●The page contains a heading, skip link, or landmark region
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○Heading elements appear in a sequentially-descending order
○`<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.
○`[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.
○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.
C
Landmark Structure
Action
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (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

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

B
Heading Hierarchy
1 headings
REVIEW
1 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H5 콘텐츠판

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

A
Form Accessibility
1 of 12 controls have issues
PASS
1 of 12 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="text">
Info::
11 control(s) properly labeled
12 controls
11 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#opinionradio오피니언for/id
#politicsradio정치for/id
#internationalradio국제for/id
#nationalradio사회for/id
#economyradio조선경제for/id
#sportsradio스포츠for/id
#enterradio건강for/id
#enterradio건강for/id
#cultureradio문화·연예for/id
#membersradio조선리더스for/id
#DBchosunradio조선몰for/id
inputtext(검색어를 입력하세요)placeholder only

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

<input type="text">

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
title 조선일보 - 1등 …21.00:14.5:1
#000000
#FFFFFF
Pass
span 2026년 4월 16일(…21.00:14.5:1
#000000
#FFFFFF
Pass
a 신문구독21.00:14.5:1
#000000
#FFFFFF
Pass
a English21.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
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 사회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
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
a BEMIL 군사세계21.00:14.5:1
#000000
#FFFFFF
Pass
a 헬스조선21.00:14.5:1
#000000
#FFFFFF
Pass
a IT조선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.

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

Send Feedback