Results for “access”

World-class accessibility design expertise combining the inclusive design principles of Microsoft's Inclusive Design team, the technical rigor of the W3C WCAG working group, and the lived experience perspective of disability advocates. Accessibility is not a feature - it's a fundamental quality attribute that makes products usable by everyone. Great accessibility design is invisible to those who don't need it and essential to those who do. It benefits everyone: captions help in noisy environments, keyboard navigation helps power users, high contrast helps in bright sunlight. When you design for the extremes, you improve the experience for all. Accessibility is not a checklist - it's a mindset that asks "who are we excluding?" at every design decision. Use when "accessibility, a11y, wcag, screen reader, keyboard navigation, color contrast, alt text, aria, focus management, skip link, assistive technology, inclusive design, ada compliance, section 508, accessible, voiceover, nvda, jaws, tab order, focus trap, accessibility, a11y, wcag, inclusive-design, screen-reader, keyboard-navigation, color-contrast, aria, focus-management, assistive-technology" mentioned.

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

Turns an access export (accounts, entitlements, grant and last-used dates per system) into a draft access review pack, one section per system owner: who has what, since when, anomalies to confirm and the decision each line needs, with a blank column for the owner's decision. Never decides, revokes or rates access. Use when the user asks to "prepare the access review pack", "split this entitlement export by system owner", "who has access to what in this system", "build the recertification pack from this export" or "draft the access attestation for the owners". Do not use for a single request for a tool or access, use software-request-review instead. Drafts for human review; never approves, authorises or signs off.

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

This skill enables Claude to audit access control implementations in various systems. It uses the access-control-auditor plugin to identify potential vulnerabilities and misconfigurations related to access control. Use this skill when the user asks to "audit access control", "check permissions", "assess access rights", or requests a "security review" focused on access management. It's particularly useful for analyzing IAM policies, ACLs, and other access control mechanisms in cloud environments, applications, or infrastructure. The skill helps ensure compliance with security best practices and identify potential privilege escalation paths.

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

Adds comprehensive accessibility testing to CI/CD pipelines using axe-core Playwright integration or pa11y-ci. Automatically generates markdown reports for pull requests showing WCAG violations with severity levels, affected elements, and remediation guidance. This skill should be used when implementing accessibility CI checks, adding a11y tests to pipelines, generating accessibility reports, enforcing WCAG compliance, automating accessibility scans, or setting up PR accessibility gates. Trigger terms include a11y ci, accessibility pipeline, wcag ci, axe-core ci, pa11y ci, accessibility reports, a11y automation, accessibility gate, compliance check.

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

Handle questions and requests about Muse's general early access program, including joining, checking request delivery or membership status, and withdrawing a request. It distinguishes program membership from access to particular features or priority in testing.

• Learning how Muse's early access program works
• Submitting a request to join the general program
• Checking request delivery and membership status

Audit a live web page for accessibility issues and produce a fix worklist with exact element selectors, evidence, and suggested changes. Findings include impact counts and source locations when available, without editing the application.

• Check accessibility after a UI change
• Locate contrast and accessible-name issues
• Prepare a fix worklist with element selectors

Check web pages and components for accessibility issues against WCAG 2.2, web accessibility guidelines. Receive a report prioritized by user impact, or request targeted code fixes followed by verification of resolved and newly introduced issues.

• Get a prioritized accessibility report for a page
• Audit accessibility patterns across components
• Fix reported issues and verify the changes

Manage access to a Telegram channel integration by approving pairing codes, updating allowed users, and setting direct-message and group policies. Check pending requests and adjust reply behavior through configuration files read by the channel server.

• Approve or deny a Telegram pairing request
• Review and update allowed users
• Change direct-message access policies

Manage who can contact an assistant through the iMessage channel. Update approved senders, approve pairing codes, and configure direct message and group access rules by editing the channel’s local settings.

• Add or remove approved iMessage senders
• Approve or reject a pending pairing code
• Set group access and mention requirements

Manage access to a Discord channel integration by approving pairing codes, updating allowed users, and setting direct-message and channel policies. Check pending requests and adjust reply behavior through configuration files read by the channel server.

• Approve or deny a Discord pairing request
• Review and update allowed users
• Change direct-message access policies

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

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

Deploy a Software-Defined Perimeter that connects verified users to authorized applications. Configure single-packet authorization, mutual certificate authentication, access policies, and monitoring, then test whether unauthorized connections and access between applications are blocked.

• Building zero trust access to internal applications
• Hiding services from unauthenticated network scans
• Testing certificate authentication and access restrictions

Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.

• Review accessibility before design handoff
• Check text and interface color contrast
• Review keyboard navigation and focus behavior

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

• Audit a web application before release
• Fix contrast and keyboard navigation issues
• Prepare accessibility reports for stakeholders

Check whether AI crawlers, the bots that collect web content for AI services, can access a website. Get a crawler access table, an assessment score, and recommendations based on robots.txt, page tags, HTTP headers, and rendering requirements.

• Checking which AI crawlers can access a website
• Reviewing unintended blocks in robots.txt
• Investigating content that requires JavaScript to display

Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.

• Review accessibility before design handoff
• Check text and interface color contrast
• Review keyboard navigation and focus behavior

Assess Kubernetes security from an existing pod or API access point. Covers permission checks, exposed node services, secrets, host access, and cloud metadata to explain how configuration weaknesses can expand access across a cluster.

• Review service account permissions and RBAC settings
• Assess host access and secrets exposure from pods
• Trace access paths from a cluster to cloud infrastructure

Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.

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

WCAG 準拠のアクセシビリティチェックをチェックリスト駆動で実行するスキル。 コンポーネント・ページ・PR に対して Pass/Fail/N/A/Needs review の構造化レポートを 生成し、エビデンスと修正案を提示する。 「アクセシビリティチェック」「a11y チェック」「WCAG をチェック」「a11y レビュー」 「アクセシビリティ監査」「WCAG 準拠確認」「アクセシビリティレポート」への言及、 または PR やコンポーネントのアクセシビリティレビュー依頼で発動する。 English: "check accessibility", "a11y audit", "a11y check", "WCAG review", "accessibility report", "screen reader test", "review for a11y", "review this PR for accessibility", "axe audit"

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

Apply platform accessibility best practices to SwiftUI, UIKit, and AppKit code. Essential companion to any SwiftUI, UIKit, or AppKit skill — always use together. Use whenever writing, editing, or reviewing ANY SwiftUI views, UIKit view controllers, AppKit views/window controllers, or platform UI — even when the user doesn't mention accessibility. Also use when the user mentions VoiceOver, Voice Control, Dynamic Type, Reduce Motion, screen reader, a11y, WCAG, accessibility audit, Nutrition Labels, accessibilityLabel, UIAccessibility, NSAccessibility, assistive technologies, or Switch Control. Not for server-side Swift, non-UI packages, or CLI tools.

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

Implement, review, or improve accessibility in iOS/macOS apps with SwiftUI and UIKit. Use when adding VoiceOver support with accessibility labels, hints, values, and traits; when grouping or reordering accessibility elements; when managing focus with @AccessibilityFocusState; when supporting Dynamic Type with @ScaledMetric; when building custom rotors or accessibility actions; when auditing a11y compliance; or when adapting UI for assistive technologies and system accessibility preferences.

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

Expert guidance on iOS accessibility best practices, patterns, and implementation. Use when developers mention: (1) iOS accessibility, VoiceOver, Dynamic Type, or assistive technologies, (2) accessibility labels, traits, hints, or values, (3) automated accessibility testing, auditing, or manual testing, (4) Switch Control, Voice Control, or Full Keyboard Access, (5) inclusive design or accessibility culture, (6) making apps work for users with disabilities.

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

This skill should be used when the user asks for an accessibility review, accessibility audit, a11y check, WCAG compliance review, screen reader audit, "is this accessible?", "does my site meet WCAG?", "check my component for accessibility", "accessibility overview of this page", "review accessibility of", "check for a11y issues", "fix accessibility issues", or any request to audit a web page, component, or codebase for WCAG 2.2 AA compliance.

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