Results for “access”

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.

The English summary is being prepared. Showing the original description.

Load this skill immediately whenever a project contains an ACCESSIBILITY.md file, or whenever you are contributing to the mgifford/ACCESSIBILITY.md repository. Absolutely always read ACCESSIBILITY.md before proposing or writing any changes. Under no circumstances skip this skill when an ACCESSIBILITY.md file is present. This skill governs when and how all other accessibility topic skills must be loaded.

The English summary is being prepared. Showing the original description.

Reviews the text and structure of a document, slide deck or web page against the accessibility rules the user supplies, or a default set covering heading structure, image alternative text, colour used as the only cue, link text, reading order, tables and language, and returns numbered findings with location, rule, severity and a ready-to-apply fix for the author, plus proposed alt text and a list of checks that need a tool or a person. Use when the user asks to "check this document for accessibility", "review the alt text in this deck", "is this page accessible", "run an accessibility check on these slides", "find accessibility issues before I publish" or "check my headings and link text". Do not use for brand or template compliance of slides, use branded-deck-builder instead. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Support audio accessory features like automatic switching using AudioAccessoryKit. Use when implementing automatic audio routing for connected accessories, managing audio accessory sessions, registering device capabilities and placement, providing connected audio source identifiers, or configuring audio accessories connected to iOS devices.

The English summary is being prepared. Showing the original description.

Discover and configure Bluetooth and Wi-Fi accessories using AccessorySetupKit. Use when presenting a privacy-preserving accessory picker, defining discovery descriptors for BLE or Wi-Fi devices, handling accessory session events, migrating from CoreBluetooth permission-based scanning, or setting up accessories without requiring broad Bluetooth permissions.

The English summary is being prepared. Showing the original description.

Design, audit, and improve accessibility and inclusive user experiences. Use when Codex is asked about WCAG, keyboard navigation, focus states, screen readers, ARIA, contrast, captions, reduced motion, forms, semantic HTML, accessible UI, game accessibility, inclusive design, accessibility QA, or compliance-sensitive accessibility work.

The English summary is being prepared. Showing the original description.

This skill enables Claude to perform comprehensive accessibility audits. It uses the accessibility-test-scanner plugin to identify WCAG 2.1/2.2 compliance issues, validate ARIA attributes, check keyboard navigation, and assess screen reader compatibility. Use this skill when the user requests an accessibility scan, audit, or compliance check, or when terms like "WCAG", "ARIA", "screen reader", "accessibility testing", or "a11y" are mentioned. It provides actionable insights for improving web application accessibility.

The English summary is being prepared. Showing the original description.

Discover and configure Bluetooth and Wi-Fi accessories using AccessorySetupKit. Use when presenting a privacy-preserving accessory picker, defining discovery descriptors for BLE or Wi-Fi devices, handling accessory session events, migrating from CoreBluetooth permission-based scanning, or setting up accessories without requiring broad Bluetooth permissions.

The English summary is being prepared. Showing the original description.

Android Accessibility Service security analysis and pentesting. Use this skill whenever the user mentions Android security testing, accessibility service abuse, RAT detection, malware analysis, ClayRat, PlayPraetor, overlay phishing, credential harvesting, or any Android app security assessment involving AccessibilityService APIs. This skill helps detect malicious accessibility services, analyze abuse patterns, and harden apps against accessibility-based attacks.

The English summary is being prepared. Showing the original description.

Accessibility implementation guide for SwiftUI apps. Use when implementing VoiceOver support, adding accessibilityLabel/Hint/Value, supporting Dynamic Type, ensuring color contrast, testing accessibility, or reviewing accessibility in PRs. Covers iOS accessibility APIs, WCAG guidelines, and testing tools.

The English summary is being prepared. Showing the original description.

Find and identify the CBaseEntity_GetChangeAccessorPathInfo_1 virtual function in CS2 binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the second GetChangeAccessorPathInfo override by scanning CBaseEntity vtable slots near the known CBaseEntity_GetChangeAccessorPathInfo_2 slot for an implementation identical to CBaseEntity_GetChangeAccessorPathInfo_2. Trigger: CBaseEntity_GetChangeAccessorPathInfo_1

The English summary is being prepared. Showing the original description.

Compare button and link text with accessible names, the names assistive technology uses for controls. Identify mismatches and suggest ARIA label changes so people using voice control can refer to the words they see.

• Comparing visible button text with accessible names
• Reviewing links that are hard to activate by voice
• Checking label fixes with accessibility tools

Review TypeScript settings and indexed access to arrays and objects to find values that may be undefined. Enable compiler checks and update unsafe code so potential failures become visible before the code runs.

• Audit TypeScript safety settings
• Review array access in data processing
• Investigate unexpected undefined errors

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

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

Draft or review manuscript statements explaining where data and code can be accessed. Organize repository choices, access restrictions, identifiers, and dataset citations, and check metadata that helps others find and reuse the research data.

• Draft data and code availability statements
• Choose repositories and access routes for research data
• Review dataset citations and metadata

Design a role permission matrix showing which business areas each role should view or edit, including confidentiality levels. Get a review workflow and, on request, empty CSV templates, SQL table definitions, JSON Schema, or Notion mappings.

• Defining viewing and editing permissions by role
• Planning access rules for confidential records
• Preparing a quarterly access review template

Organize primary and backup administrators, two-factor authentication, shared logins, and access review dates for each system. Get a practical register design or request empty templates in CSV, SQL, JSON Schema, or a Notion property mapping.

• Reviewing administrator access each quarter
• Checking accounts left behind by former employees
• Creating an administrator register template

Compare accessibility findings between two versions of a web page. Identify newly introduced and fixed issues, count existing findings, and report evidence and suggested fixes without editing application code.

• Check accessibility before committing local changes
• Compare a page against a branch baseline
• Confirm which accessibility issues a change fixed

Check whether the iMessage channel can read messages on a Mac and review who is allowed to contact the assistant. Get guidance on required permissions, current access rules, and the next setup step.

• Check initial iMessage channel setup
• Investigate why texts do not reach the assistant
• Review approved senders and access rules

Trace mailbox abuse in a CTF sandbox, a controlled security challenge environment. The skill connects OAuth permissions, forwarding rules, delegated access, and message logs to concrete mail effects, documenting the smallest reproducible sequence and supporting evidence.

• Trace how OAuth consent enables mailbox access
• Investigate forwarding and inbox rule effects
• Verify shared mailbox and delegated access

Investigate signs of Mimikatz credential theft using command lines, access to Windows authentication memory, file indicators, and known modules in memory. Correlate endpoint and security logs to assess suspicious alerts, document evidence, and recommend response actions.

• Investigating alerts about Windows authentication memory access
• Hunting for signs of credential theft
• Assessing compromise scope during incident response