Files

T

Antigravity Agent 9a135bd19d docs(10_Wiki): Topic_Business/General/Graphic/Programming을 Topics/ 하위로 이동

최상위 10_Wiki/Topic_*였던 4개 카테고리 폴더를 10_Wiki/Topics/Topic_* 로 재배치.
콘텐츠 변경 없음(순수 폴더 이동) — Topics/ 하위 나머지 폴더는 이미 지난 커밋에서
전부 정리된 상태(잔존 항목은 에이전트 운영 상태 및 사용자가 보존을 요청한
업데이트0615/무제 3.canvas 뿐).

2026-07-05 00:44:01 +09:00

5.3 KiB

Raw Blame History

id, title, category, status, verification_status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, created_at, updated_at, review_reason, merge_history, tags, raw_sources, applied_in, github_commit

title

HTML Accessibility

🎯 한 줄 통찰 (One-line insight)

Always write HTML with accessibility in mind — use semantic elements for their intended purpose so all users get a good way to navigate and interact with your site. [S1]

🧠 핵심 개념 (Core concepts)

Accessibility-first mindset — always write HTML code with accessibility in mind, giving users a good way to navigate and interact with the site. [S1]
Semantic HTML — use the correct HTML element for its purpose; a semantic <button> carries suitable default styling, screen-reader recognition, focusability, and keyboard navigation that a <div> does not. [S1]
Headings convey structure — use headings (<h1>–<h6>) for headings only, not to make text big or bold. [S1]
Alternative text — provide descriptive alt text for images. [S1]
Declare the language — set the page language with the lang attribute on <html>. [S1]
Meaningful link text — links should describe where they lead, not say "Click here" or "Read more.." [S1]

🧩 추출된 패턴 (Extracted patterns)

Semantic vs non-semantic — non-semantic elements: <div>, <span>; semantic elements: <form>, <table>, <article> (and <button>). [S1]
Right element for the job — prefer <button>Report an Error</button> over <div>Report an Error</div>. [S1]
Heading hierarchy — order headings <h1>→<h6> to express document structure. [S1]
alt on every meaningful image — <img ... alt="descriptive text">. [S1]

📖 세부 내용 (Details)

Write with accessibility in mind Always write HTML code with accessibility in mind. Provide the user a good way to navigate and interact with your site. [S1]

Use semantic HTML Use the correct HTML element for the correct purpose. For example, a button should be a <button>, not a <div>: [S1]

<button>Report an Error</button>

rather than the non-semantic:

<div>Report an Error</div>

Benefits of using the semantic <button> include suitable default styling, screen reader recognition, focusability, and keyboard navigation support. Non-semantic elements include <div> and <span>; semantic elements include <form>, <table>, and <article>. [S1]

Use headings for structure Use HTML headings for headings only. Don't use headings to make text BIG or bold. [S1]

<h1>Heading 1</h1>
<h2>Heading 2</h2>
<h3>Heading 3</h3>
<h4>Heading 4</h4>
<h5>Heading 5</h5>
<h6>Heading 6</h6>

Provide alternative text for images

<img src="img_chania.jpg" alt="A narrow city street with flowers in Chania">

Declare the page language

<!DOCTYPE html>
<html lang="en">
<body>
...
</body>
</html>

Use meaningful link text Good links use descriptive text explaining where the link leads; bad links use generic text like "Click here" or "Read more..". [S1]

🛠️ 적용 사례 (Applied in summary)

The applied guidance is concrete: replace non-semantic <div> buttons with <button>, keep headings hierarchical and reserved for structure, add descriptive alt text, declare lang, and write meaningful link text. No external project/commit applications found in the source.

💻 코드 패턴 (Code patterns)

Semantic button (HTML):

<button>Report an Error</button>

Image with alternative text (HTML):

<img src="img_chania.jpg" alt="A narrow city street with flowers in Chania">

Document language declaration (HTML):

<html lang="en">

⚖️ 모순 및 업데이트 (Contradictions & updates)

No contradictions found in the source. Note this page does not cover ARIA attributes, <label for> form-input labels, tabindex, or color-contrast requirements — those topics are not addressed here (Not found in source). [S1]

✅ 검증 상태 및 신뢰도

상태: draft
검증 단계: conceptual (실제 적용 사례 발견 시 applied/validated로 승격 가능)
출처 신뢰도: B (W3Schools — widely used educational reference, not a primary standards body)
신뢰 점수: 0.87
중복 검사 결과: 신규 생성 (New discovery)

🔗 지식 그래프 (Knowledge Graph)

상위/루트: HTML Tutorial
관련 개념: HTML Semantics, HTML Headings, HTML Images, HTML Buttons
참조 맥락: Referenced whenever building markup that must be usable by screen readers, keyboards, and assistive technology.

📚 출처 (Sources)

[S1] W3Schools — HTML Accessibility — https://www.w3schools.com/html/html_accessibility.asp

📝 변경 이력 (Change history)

2026-06-23: Initial draft synthesized from the W3Schools "HTML Accessibility" page (Astra wiki-curation, P-Reinforce v3.1 format).

5.3 KiB Raw Blame History Unescape Escape