Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 5 REVIEW 7 FIX

Alt Text Quality

Action

13 of 48 images have issues

FIX

13 of 48 images have issues

9 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

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

4 image(s) with filename as alt text

35 image(s) with good alt text

48 images 35 good alt text 4 generic 9 missing

Issue	Count
missing	9 image(s)
filename	4 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

Link & Button Quality

Action

33 issue(s) across 243 links and 26 buttons

FIX

33 issue(s) across 243 links and 26 buttons

26 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; javascript:;; javascript:;; javascript:;; https://www.patagonia.co.kr/shop/goodsList/001005001000000; https://www.patagonia.co.kr/shop/goodsList/001005081000000; https://www.patagonia.co.kr/shop/goodsList/001003003001000; https://www.patagonia.co.kr/shop/goodsList/001005007000000; https://www.patagonia.co.kr/shop/goodsList/001002003000000; https://www.patagonia.co.kr/shop/goodsList/001005014000000 (+16 more)

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: javascript:;; javascript:;

7 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.navigation-search (#261 on page); button.navigation-hamburger (#266 on page); button.navigation-search (#267 on page); button.navigation-hamburger (#271 on page); button.btnClose (#353 on page); button.back-gnb (#375 on page); button.back-gnb (#378 on page)

215 link(s) with descriptive text

243 links

26 empty

0 generic text

2 new tab

7 empty buttons

Element	Text	Issue	Suggested Fix
javascript:;	More D…	new tab	Add '(opens in new tab)' to text
javascript:;	Trade In	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
javascript:;	(empty)	empty	Add link text or aria-label
javascript:;	위시리스트 추가 …	img no alt	Add alt attribute to the image
javascript:;	(empty)	empty	Add link text or aria-label
javascript:;	(empty)	empty	Add link text or aria-label
https://www.patagonia.co.kr/shop/goodsLi…	(empty)	empty	Add link text or aria-label
https://www.patagonia.co.kr/shop/goodsLi…	(empty)	empty	Add link text or aria-label
https://www.patagonia.co.kr/shop/goodsLi…	(empty)	empty	Add link text or aria-label
https://www.patagonia.co.kr/shop/goodsLi…	(empty)	empty	Add link text or aria-label
https://www.patagonia.co.kr/shop/goodsLi…	(empty)	empty	Add link text or aria-label
https://www.patagonia.co.kr/shop/goodsLi…	(empty)	empty	Add link text or aria-label
https://www.patagonia.co.kr/shop/goodsLi…	(empty)	empty	Add link text or aria-label
https://www.patagonia.co.kr/shop/goodsLi…	(empty)	empty	Add link text or aria-label
https://www.patagonia.co.kr/shop/goodsLi…	(empty)	empty	Add link text or aria-label
/stories/filmDetail/275	(empty)	empty	Add link text or aria-label
/stories/view/266	(empty)	empty	Add link text or aria-label
/stories/filmDetail/265	(empty)	empty	Add link text or aria-label
/stories/filmDetail/264	(empty)	empty	Add link text or aria-label
/stories/filmDetail/263	(empty)	empty	Add link text or aria-label
/stories/filmDetail/262	(empty)	empty	Add link text or aria-label
/stories/filmDetail/261	(empty)	empty	Add link text or aria-label
/sports/community/003007001000000	(empty)	empty	Add link text or aria-label
/sports/community/003004001000000	(empty)	empty	Add link text or aria-label
/sports/community/003002001000000	(empty)	empty	Add link text or aria-label
/sports/community/003003001000000	(empty)	empty	Add link text or aria-label
/sports/community/003005001000000	(empty)	empty	Add link text or aria-label
/sports/community/003001001000000	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

234 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; javascript:;; javascript:;; javascript:;; https://www.patagonia.co.kr/shop/goodsList/001005001000000; https://www.patagonia.co.kr/shop/goodsList/001005081000000; https://www.patagonia.co.kr/shop/goodsList/001003003001000; https://www.patagonia.co.kr/shop/goodsList/001005007000000; https://www.patagonia.co.kr/shop/goodsList/001002003000000; https://www.patagonia.co.kr/shop/goodsList/001005014000000 (+16 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

javascript:;; javascript:;

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.navigation-search (#261 on page); button.navigation-hamburger (#266 on page); button.navigation-search (#267 on page); button.navigation-hamburger (#271 on page); button.btnClose (#353 on page); button.back-gnb (#375 on page); button.back-gnb (#378 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-iracrt

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://patagonia.co.kr/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://patagonia.co.kr/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

No <nav> landmark found

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

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

Heading Hierarchy

21 headings, 1 skip(s)

REVIEW

21 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)
H2 main visual section
H3 Capilene® Cool Sun
H3 Capilene® Cool Sun
H2 카테고리 배너
H2 midBanner section
H3 Baggies™
H3 Baggies™
H2 카테고리 배너
H2 최신글
H2 Sports Category Slide
H4 Footer skipped
H5 모든 제품을 보증합니다.
H5 사회와 환경에 책임을 다합니다.
H5 환경 단체를 지원합니다.
H5 제품을 오래 쓸 수 있습니다.
H5 수익을 지구에 바칩니다.
H6 파타고니아코리아 멤버십 가입하기
H6 Need Help?
H6 더보기
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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 2 pass AA only

title 파타고니아코리아

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a 퀄리티랩

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 main visual section	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 카테고리 배너	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 midBanner section	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 카테고리 배너	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 최신글	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Sports Category Slid…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Baggies™	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Baggies™	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 제목	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title 파타고니아코�…	1.00:1	4.5:1	#000000	#000000	Fail
a 퀄리티랩	3.66:1	4.5:1	#000000	#666666	Fail
a 풀뿌리 환경 운…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 스토리즈	8.07:1	4.5:1	#000000	#73A6CD	Pass
strong Free Shipping on Ord…	4.59:1	3.0:1	#000000	#3F79B2	Pass
p Orders are shipped w…	4.97:1	4.5:1	#000000	#447FB8	Pass
a More …	5.52:1	4.5:1	#000000	#4E87BD	Pass
strong Let Your Gear Live A…	6.54:1	3.0:1	#000000	#6494C0	Pass
p Why not trade it in?…	7.86:1	4.5:1	#000000	#80A2C2	Pass
a Trade In	10.38:1	4.5:1	#000000	#B7B6B6	Pass
span 메뉴 닫기버튼	8.64:1	4.5:1	#000000	#A8A6A2	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.

Lighthouse Accessibility Audits

Action

Score 77/100 — 6 failing, 21 passed

REVIEW

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.

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#navigation > div.fb__header__menu > div.ptg__drawer__menu-container > button.navigation-hamburger `div#navigation > div.fb__header__menu > div.ptg__drawer__menu-container > button.navigation-hamburger`

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.card__inner > div.card__products > div.card__image-wrapper > img `div.card__inner > div.card__products > div.card__image-wrapper > img`
div.card__inner > div.card__products > div.card__image-wrapper > img `div.card__inner > div.card__products > div.card__image-wrapper > img`
div.card__inner > div.card__products > div.card__image-wrapper > img `div.card__inner > div.card__products > div.card__image-wrapper > img`
div.card__inner > div.card__products > div.card__image-wrapper > img `div.card__inner > div.card__products > div.card__image-wrapper > img`
div.card__inner > div.card__products > div.card__image-wrapper > img `div.card__inner > div.card__products > div.card__image-wrapper > img`
div.card__inner > div.card__products > div.card__image-wrapper > img `div.card__inner > div.card__products > div.card__image-wrapper > img`
div.card__inner > div.card__products > div.card__image-wrapper > img `div.card__inner > div.card__products > div.card__image-wrapper > 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.fb__header__menu > div.ptg__drawer__menu-container > h1.logo > a `div.fb__header__menu > div.ptg__drawer__menu-container > h1.logo > a`
ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link `ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link`
ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link `ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link`
ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link `ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link`
ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link `ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link`
ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link `ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link`
ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link `ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link`
ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link `ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link`
ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link `ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link`
ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link `ul.swiper-wrapper > li.swiper-slide > div.card__wrap > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`
div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link `div.swiper > ul.swiper-wrapper > li.swiper-slide > a.ptg__category__block-link`

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.

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
Footer `body#main > footer#footer > footer.ptg__footer > h4.hidden`

These are opportunities to improve keyboard navigation in your application.

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

●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

●Background and foreground colors have a sufficient contrast ratio

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

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

●Deprecated ARIA roles were not used

●All heading elements contain content.

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

○`<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

○Form elements have associated labels

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

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

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "제목"

Got: 1 ≤2-char heading(s)

8 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 8 all-caps heading(s)

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

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

Got: <input type="text" id="devHeaderSearchText">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#devHeaderSearchText	text	(none)	none

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

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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "devHeaderSearchText" should use type="search" (currently type="text")

Field name "devHeaderSearchText" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "ko"

PASS

Lang attribute set to "ko"

<html lang="ko"> is set and valid

Got: ko

A+

Tabindex Anti-Patterns

9 explicit tabindex attribute(s) checked, no anti-patterns

PASS

9 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 4 visible text node(s) render at >= 12 CSS pixels

PASS

All 4 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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