'screen-reader' 검색 결과

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

Review tooltips so their extra information is available to screen reader users. Check accessible names, meaning labels available to assistive technology, and links to the elements that trigger them, then suggest fixes and verification steps.

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

• Checking whether tooltip information can be read aloud
• Reviewing links between tooltips and their triggers
• Auditing shared tooltip components

Inspect web pages for automatically playing audio and video, then remove autoplay or adjust required playback with muted defaults and accessible pause controls. Review keyboard access so users can stop media promptly.

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

• Review audio and video autoplay on page load
• Add muted playback and pause controls
• Check keyboard access to media controls

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

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

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

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.

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

• Reviewing tables for screen reader accessibility
• Checking header relationships in tables with merged cells
• Reviewing table patterns in a design system

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

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

Check checkboxes, radio buttons, and switches for descriptive names that screen readers can announce. Identify missing or unclear labels, suggest appropriate HTML or ARIA labeling, and explain how to verify the changes with accessibility tools.

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

• Checking labels on checkboxes and radio buttons
• Reviewing whether switch names explain their purpose
• Fixing missing or unclear accessible names

Review meter elements for accessible names, the labels screen readers use to explain what a value measures. Identify missing labels, add aria-label or aria-labelledby, and describe checks using browser accessibility tools or assistive technology.

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

• Check labels for battery and storage meters
• Add accessible names to meter elements
• Review meters in shared UI components

Check that ARIA roles, which describe interface elements to assistive technology, include their required attributes. Identify missing state or value information in rendered HTML and get guidance on fixes and accessibility verification.

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

• Checking required attributes on custom sliders
• Reviewing shared interface components for accessibility
• Verifying state information conveyed to screen readers

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

Guide web app testing with screen readers such as VoiceOver, NVDA, and JAWS. Check forms, dialogs, keyboard navigation, and spoken update notifications to identify accessibility problems across desktop and mobile browser combinations.

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

• Checking form labels and error announcements
• Testing dialog focus behavior
• Verifying announcements for changing content

Review and fix interface accessibility against WCAG 2.2, a web accessibility standard. Check keyboard navigation, focus, screen reader labels, forms, motion, and zoom, then report failures with their criteria and implement fixes using the project's existing styling system.

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

• Check flows using only the keyboard
• Fix control names and screen reader announcements
• Improve form labels and error feedback

Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity and specific fixes. Use when the user wants an accessibility check, contrast verification, keyboard/screen-reader review, or wants to confirm a component meets POUR.

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

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

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

Audit web pages and components for WCAG 2.2 accessibility compliance. Use when a user asks to check accessibility, find a11y issues, audit for WCAG compliance, fix screen reader problems, check color contrast, ensure keyboard navigation works, or prepare for accessibility regulations like the European Accessibility Act or ADA.

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

Accessibility isn't a feature - it's a fundamental quality of good software. 1 in 4 adults has a disability. Many more have temporary impairments or situational limitations. Your users include people who can't see, can't hear, can't use a mouse, or can't process information the way you do. This skill covers WCAG guidelines, ARIA patterns, keyboard navigation, screen reader compatibility, and automated testing. Key insight: accessible code is better code. The constraints of accessibility lead to simpler, more semantic, more maintainable implementations. 2025 lesson: Accessibility lawsuits are at an all-time high. "We'll add it later" is both ethically wrong and legally risky. Start accessible, stay accessible. Use when "accessibility, a11y, wcag, aria, screen reader, keyboard navigation, focus trap, alt text, color contrast, skip link, accessible, accessibility, a11y, wcag, aria, screen-reader, keyboard, inclusive, semantic-html" mentioned.

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

World-class accessibility design expertise combining the inclusive design principles of Microsoft's Inclusive Design team, the technical rigor of the W3C WCAG working group, and the lived experience perspective of disability advocates. Accessibility is not a feature - it's a fundamental quality attribute that makes products usable by everyone. Great accessibility design is invisible to those who don't need it and essential to those who do. It benefits everyone: captions help in noisy environments, keyboard navigation helps power users, high contrast helps in bright sunlight. When you design for the extremes, you improve the experience for all. Accessibility is not a checklist - it's a mindset that asks "who are we excluding?" at every design decision. Use when "accessibility, a11y, wcag, screen reader, keyboard navigation, color contrast, alt text, aria, focus management, skip link, assistive technology, inclusive design, ada compliance, section 508, accessible, voiceover, nvda, jaws, tab order, focus trap, accessibility, a11y, wcag, inclusive-design, screen-reader, keyboard-navigation, color-contrast, aria, focus-management, assistive-technology" mentioned.

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

Use when auditing a user-facing app — web, mobile (iOS/Android/React Native/Flutter), desktop, CLI, or games — for accessibility barriers or WCAG 2.2 conformance, before shipping UI changes, or in response to concerns about screen-reader, keyboard, low-vision, motor, cognitive, or photosensitive users. Not for general bug hunting or code correctness.

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

Implements accessibility fixes in code. Use when remediating semantic HTML, ARIA, focus, keyboard support, or screen-reader behavior.

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

Builds accessibility testing for WCAG 2.2 audits, CI gates, mobile audits, and EAA/ADA/VPAT evidence. Use when adding axe-core, Lighthouse, or screen-reader tests; not fixes.

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