'design-system' 검색 결과

Review decorative images and icons to prevent unnecessary screen reader announcements. Check empty alt text, aria-hidden, and relevant keyboard behavior, then suggest fixes for concrete accessibility issues without flagging decorative assets solely because they exist.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking decorative images for unnecessary announcements
• Reviewing accessibility of SVGs and icons
• Checking shared decorative component patterns

Find empty links, unlabeled icon links, and broken destinations. Add descriptive text or labels that screen readers can announce, and fix or remove broken links so users can understand where each link leads.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding empty links across a page
• Adding destination labels to icon links
• Reviewing and fixing broken link destinations

Review GIFs, videos, and CSS animations for rapid flashing that may trigger seizures in photosensitive users. Check flash frequency and screen area, then suggest removing or slowing effects or replacing them with fades or static content.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking flashing effects in animated GIFs
• Reviewing rapid flashing in videos and CSS animations
• Replacing flashing effects with fades or static content

Review links, buttons, and form fields for duplicate HTML IDs. Identify affected controls, suggest unique IDs, and explain how to verify keyboard navigation, focus movement, and screen reader behavior after the fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking HTML IDs in forms
• Investigating unexpected keyboard focus
• Reviewing shared interactive components

Review rendered HTML for duplicate IDs used by ARIA attributes, which connect elements to labels and descriptions for assistive technology. Identify ambiguous references, correct IDs and their links, and explain how to verify the changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating incorrect labels read by screen readers
• Checking repeated components for duplicate IDs
• Reviewing ARIA references in a design system

Check HTML definition lists, which pair terms with descriptions, for structural problems. Identify invalid child elements and unclear relationships, suggest markup fixes, and explain how to verify that screen readers group the information correctly.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing HTML structure in glossaries
• Checking term and description relationships
• Fixing definition lists that confuse screen readers

Review where keyboard focus, the current target for keyboard input, moves when dialogs open, views change, or content updates. Identify misplaced or lost focus and propose changes that help keyboard and screen reader users continue navigating.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking focus when dialogs open and close
• Reviewing focus after SPA navigation
• Keeping keyboard navigation usable during content updates

Review keyboard focus, the element currently selected for interaction, to check that Tab navigation follows the page’s visual order. Identify HTML ordering issues and verify focus stays within dialogs and returns to their triggers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing a page’s Tab navigation order
• Checking focus when dialogs open and close
• Reviewing HTML order and tabindex values

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check page usability with CSS disabled
• Review reading order and heading structure
• Inspect form labels, instructions, and errors

Review buttons for missing or unclear names, including controls that contain only icons. Add text or labels that explain each action to screen reader users, and replace buttons used for page navigation with links.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding buttons without descriptive names
• Labeling icon-only buttons for screen readers
• Checking whether navigation controls should be links

Check whether aria-hidden on the document body hides an entire page from screen readers, tools that read content aloud. Identify problematic states and suggest limiting hiding to specific background containers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking accessibility when a modal opens
• Investigating why a page is missing from screen readers
• Reviewing body attributes across UI state changes

Review HTML for deprecated ARIA roles, which describe elements to assistive technology, and abstract roles that should not appear in markup. Suggest recommended replacements or native HTML elements and explain potential browser and screen reader compatibility issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find deprecated ARIA roles in existing code
• Review whether native HTML can replace custom roles
• Inspect role usage in shared UI components

Review ARIA roles, labels that tell assistive technology what page elements do, and correct invalid values. Prefer standard HTML controls where suitable, then check keyboard behavior, focus movement, and screen reader output to verify the changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding invalid or misspelled ARIA role values
• Replacing custom widgets with standard HTML controls
• Reviewing accessibility in shared UI components

Review dynamic page updates so screen reader users hear status changes without moving focus. Check ARIA live regions, areas that announce updates, choose suitable announcement urgency, and identify markup or interaction issues to verify with accessibility tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking announcements of form results and errors
• Making cart updates audible to screen reader users
• Reviewing loading and status announcements

Review dialogs to check whether screen readers can announce their purpose when they open. Identify missing or unclear labels, suggest title or label associations, and explain how to verify the changes with accessibility tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking names on modal dialogs
• Reviewing labels on alert dialogs
• Auditing shared dialog components

Review forms for autofocus that moves users past introductory content when a page loads. Suggest removing it or moving focus after user interaction, while considering exceptions for login pages and pages dedicated to search.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing forms with introductory content
• Investigating unexpected scrolling on page load
• Moving focus after a user action

Check whether ARIA attributes, which describe interface elements to assistive technology, are supported by each element’s role. Review rendered HTML and interactive states, identify invalid combinations, and suggest removals or corrections to support accurate screen reader interpretation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking ARIA attributes in shared components
• Reviewing accessibility in a design system
• Investigating incorrect screen reader output

Review same-page links for accessible scrolling. Check that reduced-motion preferences disable animated scrolling, provide guidance for instant navigation, and verify that keyboard focus moves to the destination so users can continue navigating there.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing same-page navigation links
• Checking scrolling with reduced motion enabled
• Fixing keyboard focus at anchor destinations

Review progress bars to ensure screen reader users can tell which task they represent. Add descriptive accessible names, check progress semantics, and verify value attributes when the current progress is known.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check progress bars for missing accessible names
• Label loading indicators with their task
• Review progress values and ranges

Check HTML for misspelled or nonexistent ARIA attributes, which convey interface information to assistive technology. Replace invalid names with standard attributes and explain how to verify that screen readers can interpret element roles and states.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking HTML for misspelled ARIA attributes
• Investigating interface states missing from screen reader output
• Reviewing accessibility attributes in shared components

Check buttons, links, and other controls for clear accessible names, the labels used by assistive technology. Identify missing or vague names and suggest descriptive text or aria-label attributes that explain each action or destination.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find buttons and links with missing names
• Replace vague labels with descriptive wording
• Review accessible names in shared components

Review ARIA attributes, which describe interface elements to assistive technology, for invalid values and missing ID references. Get specific corrections and guidance for checking that element states and labels are communicated correctly.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking ARIA values in interactive components
• Finding missing IDs referenced by ARIA attributes
• Reviewing accessibility fixes before release

Review videos for information conveyed only through images, such as actions, expressions, and on-screen text. Identify missing audio descriptions and outline options for a separate description track, an extended version, or descriptions within the main narration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking product demos for information missing from the audio
• Planning audio descriptions for actions and on-screen text
• Reviewing video description markup and player interactions

Inspect hidden page regions for links, buttons, or inputs that still receive keyboard focus. Identify elements that screen readers cannot announce, suggest focus handling changes, and explain how to verify the resulting keyboard behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking hidden regions for focusable controls
• Investigating silent focus during keyboard navigation
• Reviewing accessibility in shared UI components