'keyboard' 검색 결과

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 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 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 whether ARIA roles, which describe interface elements to assistive technology, have the required parent roles. Find misplaced menu items, tabs, or list items, suggest suitable containers, and explain how to verify the corrected structure.

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

• Checking parent roles for menu items
• Reviewing tab and list structures
• Auditing design-system components

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

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

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 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 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 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 buttons, links, and menu items to check whether screen readers announce their purpose. Identify missing accessible names, meaning labels available to assistive technology, and suggest fixes using text or ARIA attributes, with guidance for verification.

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

• Checking labels on buttons and links
• Reviewing accessibility in a design system
• Verifying screen reader output after label fixes

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

Apply shared visual and writing rules to course pages, figures, and manuals. Check colors, fonts, labels, layouts, plain technical English, dark themes, keyboard focus, touch targets, and reduced-motion behavior against defined reference values.

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

• Applying consistent colors and fonts to course pages
• Checking dark theme colors and text readability
• Standardizing figure labels and card layouts

Add mouse, touch, and keyboard interaction to Three.js scenes. Implement object picking, camera navigation, dragging, and transform handles, with examples for selection feedback, coordinate conversion, and limiting the cost of interaction checks.

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

• Select 3D objects with clicks or touch
• Add camera rotation and zoom controls
• Drag, rotate, and scale objects

Check opencode commands, HTTP server behavior, lifecycle events, and terminal startup with purpose-built scripts. Find stored sessions by ID, title, or scoped message searches, and export conversations as JSON for further inspection.

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

• Check CLI commands and HTTP server health
• Observe lifecycle events associated with plugin hooks
• Check terminal startup and keyboard input

Design agents that operate desktop or browser software through screenshots, mouse actions, and keyboard input. Compare ways to locate interface elements, diagnose coordinate errors, handle changing screens, and evaluate task completion, operating speed, and safety boundaries.

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

• Designing screen-based automation for software without APIs
• Comparing methods for locating interface elements
• Investigating misclicks and coordinate scaling errors

Build web interfaces with floating cards, spatial depth, and translucent glass effects using GSAP and 3D CSS. Add scroll animations while preserving keyboard navigation and providing static states for users who request reduced motion.

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

• Building a landing page with floating cards
• Adding depth to a dashboard
• Creating scroll-linked animations

Refine AI-generated web interfaces by improving colors, spacing, typography, and action priorities while preserving existing behavior. Uses four visual styles and a seven-part review to check usability, interaction feedback, accessibility, and mobile layouts.

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

• Polish an AI-generated prototype
• Simplify dashboard controls and repeated metrics
• Restyle a page using a reference screenshot

Design reusable interface components in React, Vue, and Svelte. Organize how components fit together, define clear configuration options, and choose styling approaches while addressing accessibility, responsive layouts, and maintenance across component libraries or design systems.

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

• Build a reusable UI component library
• Standardize component options across a design system
• Refactor complex existing components

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

Audit websites against WCAG 2.2, guidelines for making web content accessible. Combine automated checks with manual verification to identify barriers, prioritize issues by impact, and guide fixes to page structure and interactive components.

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

• Audit a website for accessibility barriers
• Review keyboard access and form labels
• Fix contrast and heading structure issues

Learn GitHub Copilot CLI through guided lessons, multiple-choice quizzes, and practical scenarios. Track progress with experience points, review commands and settings, and check understanding with a final exam.

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

• Learning GitHub Copilot CLI step by step
• Reviewing slash commands and keyboard shortcuts
• Practicing CLI features through scenario challenges

Perform live Windows or macOS desktop tasks that dedicated tools cannot complete. The skill guides app and window selection, clicks, text entry, and keyboard actions, checking fresh screen information and verifying the requested result.

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

• Completing desktop tasks without a suitable dedicated tool
• Entering and committing text in an app
• Selecting the correct window among similar windows