Test design, vulnerability assessment, and quality assurance (13K skills)
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.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.