Review whether pages remain understandable and usable without CSS. Check reading order, headings, form labels, instructions, and errors, then suggest HTML changes that preserve meaning when styles fail or users apply their own.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when reviewing rendered HTML, layout components, or design-system patterns that may depend on presentation for meaning. Check the DOM order, semantic structure, form relationships, and whether CSS generated content carries essential information.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Users can browse with custom styles, high contrast modes, reader tools, or failed stylesheets. If the page only makes sense visually, content order, instructions, and task flow break as soon as presentation changes.
Find pages or components that rely on CSS for meaning. Verify the page still has a logical reading order, visible labels, instructions, error text, and operable primary actions when author styles are disabled or replaced by user styles.
Use semantic HTML and DOM order to preserve headings, lists, labels, field groups, helper text, and error messaging without relying on CSS positioning, pseudo-elements, or visual-only cues.
Explain why semantic HTML and meaningful DOM order let content remain understandable when CSS fails to load or users apply their own styles.
Review templates, rendered HTML, and component markup related to Ensure content remains usable without CSS. Flag where meaning, reading order, labels, instructions, or task flow depend on CSS rather than semantics, and note how to verify the fix with styles disabled.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/content-without-css
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.