'keyboard' 검색 결과

Review form fields for code that blocks pasting, then remove those restrictions. The skill helps check password manager use, keyboard interactions, and accessibility so people can paste passwords and other long values into inputs.

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

• Checking why passwords cannot be pasted
• Reviewing credit card fields for paste restrictions
• Improving form accessibility

Review pagination markup so people using screen readers or keyboards can understand their current page and move between pages. Check navigation labels, current-page attributes, focusable controls, and announcements when the page changes.

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

• Reviewing pagination in search results
• Checking keyboard navigation between pages
• Improving screen reader labels for pagination

Review links embedded in body text to check whether readers can recognize them without relying on color alone. Identify CSS issues with underlines, color contrast, and hover or keyboard focus states, then suggest specific fixes.

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

• Review body text links after removing underlines
• Check contrast between links and surrounding text
• Inspect hover and keyboard focus cues

Review large tables, feeds, and lists for rendering overhead. Introduce virtualization, which renders only visible items and a small buffer, while preserving keyboard access, selection, and expected scrolling behavior.

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

• Investigate sluggish admin tables
• Review long search result lists
• Reduce rendering overhead in feeds

Review links so their destinations are clear even without surrounding text. Identify vague wording, improve names announced by screen readers, and check keyboard behavior and download details such as file type and size.

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

• Replace vague link text with clear destination names
• Review links for screen reader users
• Check download links for file type and size

Review and fix HTML form fields so their input types match the data being entered. Check autocomplete settings and the final browser markup to support suitable mobile keyboards, built-in validation, and browser autofill.

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

• Reviewing input types in an existing form
• Improving mobile keyboards for email and phone fields
• Adding autocomplete settings for browser autofill

Review drag-and-drop interfaces for keyboard and screen reader access. Inspect the rendered HTML, identify missing alternative controls and status announcements, and guide changes so users can perform equivalent actions through different input methods.

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

• Reviewing keyboard alternatives to dragging
• Checking screen reader status announcements
• Inspecting rendered drag-and-drop markup

Review file upload interfaces for clear labels, accepted formats, size limits, and accessible progress and error messages. Check that keyboard and screen reader users can complete uploads, including alternatives to drag and drop.

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

• Review labels and instructions on file upload forms
• Check keyboard alternatives to drag and drop
• Improve upload progress and error announcements

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

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

Check whether sticky headers, banners, or chat widgets hide controls reached with the keyboard. Review tab order, zoomed views, and mobile layouts, then suggest spacing or scrolling changes that keep the focused control and its indicator visible.

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

• Checking keyboard navigation around sticky headers
• Testing pages with cookie banners and chat widgets open
• Reviewing overlap in zoomed and mobile layouts

Review rotating slideshows for accessibility and guide fixes to pause controls, keyboard navigation, and screen reader announcements. Check the rendered HTML and ensure the carousel respects users who request reduced motion in their device settings.

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

• Review pause controls for autoplay slideshows
• Check carousel navigation using only a keyboard
• Review screen reader announcements of slide changes

Review rendered HTML for links, buttons, or inputs inside role="text" containers. Identify controls hidden from screen readers, suggest markup changes, and explain how to check keyboard access and screen reader output after fixing them.

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

• Reviewing links and buttons inside text containers
• Investigating controls missing from screen reader output
• Checking accessibility in design system components

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 accessibility coverage for shared components
• Add accessibility checks to page flow tests
• Run accessibility tests in CI

Review tooltips so keyboard and screen reader users can access their explanations. Check the rendered HTML, accessible associations, hover and focus behavior, Escape dismissal, and contrast, then identify the elements and attributes that need fixes.

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

• Checking keyboard access to tooltips
• Reviewing tooltip associations for screen readers
• Checking hover, focus, and Escape behavior

Build interactive terminal screens with OpenTUI using its core API, React, or Solid. Guides framework selection, components, layout, keyboard input, animations, and testing, with references for project setup and troubleshooting.

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

• Starting an OpenTUI project with React or Solid
• Building terminal forms and selection menus
• Adapting layouts to terminal dimensions

Customize Claude Code keyboard shortcuts while preserving existing settings. Change submission keys, add chords—shortcuts entered as a sequence of keystrokes—and remove default bindings, with checks for invalid settings and terminal or operating system conflicts.

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

• Change the shortcut for opening an external editor
• Add a shortcut entered as a sequence of keystrokes
• Change the key used to submit chat messages

Audit web or mobile pages and user journeys against an agreed WCAG accessibility standard. Combine automated scans with manual checks to document barriers, prioritize fixes, and record retest results alongside any remaining gaps.

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

• Audit keyboard access through checkout
• Check screen-reader access, focus, and contrast
• Prioritize accessibility fixes

Build and review interfaces against WCAG 2.2 accessibility guidelines. Covers keyboard navigation, screen readers that read interface content aloud, accessible forms, mobile support, and display preferences, helping identify and fix barriers to using a website or app.

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

• Audit an interface for accessibility issues
• Add keyboard navigation and focus management
• Improve screen reader support for forms

Find answers about Codewhale commands, settings, skills, and keyboard shortcuts using the installed help and configuration tools. For environment problems, consult diagnostic output to explain what the current installation actually supports.

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

• Check how to use a Codewhale command
• Find settings and keyboard shortcuts
• Diagnose configuration and credential issues

Build AI agents that inspect screenshots, choose actions, and operate a mouse and keyboard. Covers the observation and action loop, desktop control examples, and isolated environments that restrict access to files, credentials, and networks.

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

• Build an AI agent that operates desktop screens
• Connect screenshot analysis to mouse and keyboard actions
• Design an isolated environment for automation

Test Qwen Code through realistic keyboard interactions in tmux, a terminal session tool. Capture readable screen snapshots at each step and produce a report documenting dialogs, commands, outcomes, and observed side effects.

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

• Testing authentication dialogs and keyboard navigation
• Checking slash command interactions
• Reviewing intermediate screens for regressions

Create and run tests for interactive command-line tools and terminal interfaces using @microsoft/tui-test. Simulate keyboard input, check visible text, and compare screen snapshots in a separate terminal environment for each test.

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

• Testing selection prompts with arrow keys and Enter
• Checking terminal screen snapshots
• Automating text entry and keyboard navigation

Review Handsontable code changes for architecture, code quality, performance, accessibility, and test coverage. Findings include severity, confidence, and file locations, helping developers assess whether changes follow project rules and demonstrate the intended behavior.

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

• Review a Handsontable branch or pull request
• Check architecture before or during core changes
• Review keyboard access and performance concerns