Skip to content
https://snu.ac.kr

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://snu.ac.kr/site.webmanifest contains invalid JSON. Browsers cannot parse it.
Got: https://snu.ac.kr/site.webmanifest

Manifest contains invalid JSON.

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
Heading Hierarchy
Action
18 headings
REVIEW
18 headings
Warning::
Multiple H1 headings (11 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
5 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 서울대학교
  • H2 네비게이션
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H1 서울대생을 위한 벚꽃 맛 스티커 duplicate H1
  • H1 yellow yellow yellow duplicate H1
  • H1 Flower Walk at SNU duplicate H1
  • H1 제66주년 4·19혁명 희생자 추모 duplicate H1
  • H1 중간고사 A+ 맞는 주파수 duplicate H1
  • H1 Full Blossom at SNU duplicate H1
  • H1 눈부신 봄날의 캠퍼스 duplicate H1
  • H1 26학번 새내기 앙케이트 duplicate H1
  • H1 교수님! 출연해주세요! duplicate H1
  • H1 샤대타로 duplicate H1
  • H2 섹션명

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 1 pass AA only
title 서울대학교
2.02:1
#000000
on
#1B3B86
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 서울대생을 위…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 yellow yellow yellow21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Flower Walk at SNU21.00:13.0:1
#000000
#FFFFFF
Pass
h1 제66주년 4·19혁…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 중간고사 A+ 맞…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Full Blossom at SNU21.00:13.0:1
#000000
#FFFFFF
Pass
h1 눈부신 봄날의 …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 26학번 새내기 …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 교수님! 출연해…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 샤대타로21.00:13.0:1
#000000
#FFFFFF
Pass
h2 네비게이션14.36:13.0:1
#000000
#D6D5D7
Pass
h2 섹션명21.00:13.0:1
#000000
#FFFFFF
Pass
title 서울대학교2.02:14.5:1
#000000
#1B3B86
Fail
a 본문 영역 바로…5.15:14.5:1
#000000
#6B7DAC
Pass
span 메뉴열기14.52:14.5:1
#000000
#DDD5D2
Pass
span 서울대학교15.52:14.5:1
#000000
#DFDDDD
Pass
span 교육15.80:14.5:1
#000000
#DFDFE3
Pass
a 대학15.91:14.5:1
#000000
#E3DFE1
Pass
a 학부대학16.43:14.5:1
#000000
#E5E3E3
Pass
a 대학16.67:14.5:1
#000000
#E5E5E5
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 5 failing, 22 passed
REVIEW
80

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
인스타그램 yellow yellow yellow 캠퍼스는 지금 노랑노랑노랑! ul.instaslide > div.slick-list > div.slick-track > li.slick-slide
인스타그램 Flower Walk at SNU 꽃으로 만개한 봄날의 캠퍼스, 함께 걸을까요? ul.instaslide > div.slick-list > div.slick-track > li.slick-slide
인스타그램 제66주년 4·19혁명 희생자 추모 제66주년 4·19 혁명 희생자 추모행사가 금일 오전, 서울대학교 4·19 혁명 희생자 추모공… ul.instaslide > div.slick-list > div.slick-track > li.slick-slide
인스타그램 중간고사 A+ 맞는 주파수 여러분의 중간고사 대박을 응원합니다! ul.instaslide > div.slick-list > div.slick-track > li.slick-slide
인스타그램 Full Blossom at SNU 완연히 만개한 서울대학교 봄 풍경 ul.instaslide > div.slick-list > div.slick-track > li.slick-slide
인스타그램 눈부신 봄날의 캠퍼스 눈부시게 빛나는 봄날의 캠퍼스 풍경 ul.instaslide > div.slick-list > div.slick-track > li.slick-slide
인스타그램 26학번 새내기 앙케이트 26학번 새내기에게 묻는다! 서울대학교 입학 후 가장 하고싶었던 일은?! ul.instaslide > div.slick-list > div.slick-track > li.slick-slide
인스타그램 교수님! 출연해주세요! 교수님! 〈샤로잡다〉에 추천해주세요! 학생들이 직접 추천한 교수님들?! 누가 있을까요~? ul.instaslide > div.slick-list > div.slick-track > li.slick-slide
인스타그램 샤대타로 여러분의 1학기 운세, 지금 샤대타로에서 확인해보세요! ul.instaslide > div.slick-list > div.slick-track > li.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.

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
08826 서울시 관악구 관악로 1 서울대학교 div.information-info > div.information-info-area > div.area-address > span
TEL. (02) 880-5114 div.information-info > div.information-info-area > div.area-address > span
(02) 880-5114 div.information-info-area > div.area-address > span > a.tel
FAX. (02) 885-5272 div.information-info > div.information-info-area > div.area-address > span
Copyright 2026 Seoul National University All Rights Reserved. div.information-info > div.information-info-area > div.area-copy > p

These are opportunities to improve the legibility of your content.

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
이전 인스타그램 서울대생을 위한 벚꽃 맛 스티커 서울대생을 위한 벚꽃 맛 스티커 등장! 인스타그램 yellow yellow yellow … main.ly-main > div#skip-content > section.ly-section > ul.instaslide
정보공시 교내기관 안내 서울대포털 클린행정센터 개인정보처리방침 이메일무단수집거부 복지보조금 부정 신고 사이트맵 div.information-footer > div.information-footer-inner > div.information-terms > ul.terms-ul

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
인스타그램 서울대생을 위한 벚꽃 맛 스티커 서울대생을 위한 벚꽃 맛 스티커 등장! ul.instaslide > div.slick-list > div.slick-track > li.slick-slide

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

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
●Image elements have `[alt]` attributes
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●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
●Links are distinguishable without relying on color.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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
○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
○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+
Alt Text Quality
All 63 images OK
PASS
All 63 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
62 image(s) with good alt text
63 images 62 good alt text
IssueCount
too long1 image(s)
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search2text검색어 입력for/id
#searchtext검색어 입력for/id
selectselect(none)none

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

<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

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

Send Feedback