테스트·보안 스킬

Check website behavior across Chrome, Firefox, Safari, and Edge, and fix browser-specific problems. Review desktop and mobile test coverage alongside CI, the automated checks run during development, to identify gaps that let regressions pass.

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

• Checking layouts and features across major browsers
• Reviewing desktop and mobile browser test coverage
• Finding gaps in automated browser checks

Review whether analytics and advertising trackers stay blocked until users consent to non-essential cookies. Check rejection, withdrawal, and access to cookie settings, and get implementation guidance tied to actual browser behavior.

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

• Checking whether trackers run before consent
• Reviewing cookie rejection and withdrawal behavior
• Keeping cookie preferences accessible after banner dismissal

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.

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

• Reviewing accessibility across the sign-in process
• Checking verification code paste and autofill
• Inspecting password reset and account recovery

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

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

• Reviewing form error announcements
• Checking success message display duration
• Auditing live update notifications

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

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

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 custom tabs, menus, lists, and similar controls for required ARIA child roles, which describe interface elements to assistive technology. Identify missing roles and structural wrappers that prevent screen readers from recognizing the items.

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

• Reviewing the structure of custom tabs and menus
• Investigating items missing from screen reader output
• Checking lists and selectors built with div or span elements

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

Find JavaScript that executes strings as code, including eval(), new Function(), and string-based timers. Review how it runs in the browser and suggest alternatives for parsing data, choosing operations, and scheduling functions to reduce code injection risks.

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

• Finding eval() and other string execution
• Replacing eval() used to parse JSON
• Changing string-based timers to function references

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

Check a page for duplicate accesskey values, which define keyboard shortcuts for elements. Identify conflicting assignments, suggest unique values or removal, and describe how to verify keyboard behavior with browser accessibility tools or assistive technology.

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

• Finding duplicate keyboard shortcut assignments
• Reviewing keyboard access to interactive elements
• Checking accessibility after shortcut changes

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

Check form fields for accessible names, the labels used by screen readers and voice controls. Identify missing or placeholder-only labels and suggest fixes using associated labels or ARIA attributes that supply or reference label text.

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

• Finding missing labels in forms
• Fixing fields that rely only on placeholder text
• Checking names on custom form controls

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 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 links and external resources for domains that ad blockers commonly block. Find navigation and loading failures, test behavior with uBlock Origin, and suggest direct links, self-hosted scripts, or server-side forwarding where appropriate.

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

• Investigate links that fail with ad blockers enabled
• Check loading of external scripts and images
• Review tracking redirects in navigation links

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

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

Benchmark how CodeGraph affects an agent investigating a real codebase. Choose a version, language, repository, and execution mode, then compare cost, tool calls, file reads, and answer correctness with and without CodeGraph.

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

• Evaluating a local development build
• Auditing a published CodeGraph version
• Comparing investigation cost and file reads