'a11y' 검색 결과

Expert guide for Web Accessibility (WCAG a11y) and Internationalization (i18n) / Panduan ahli untuk Aksesibilitas Web dan Internasionalisasi.

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

Implement web accessibility (a11y) best practices following WCAG guidelines to create inclusive, accessible user interfaces.

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

Implement accessibility. TRIGGERS - Use when user needs help with a11y-implementation-guide related tasks.

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

Audit web pages and components for WCAG 2.2 accessibility compliance. Use when a user asks to check accessibility, find a11y issues, audit for WCAG compliance, fix screen reader problems, check color contrast, ensure keyboard navigation works, or prepare for accessibility regulations like the European Accessibility Act or ADA.

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

Autonomous comprehensive review. Once-through pipeline over /review-health, /review-arch, /review-security, /review-perf, /review-a11y, /review-test, /review-release. Operator-configurable ticket creation at startup — when ON, auto-approves sub-skill ticket proposals per the orchestrator-family contract; when OFF, uniformly declines and surfaces findings in the consolidated report. Auto-detects sub-skills that do not apply (no web content → skip /review-a11y; no tests → skip /review-test).

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

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.

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

Regression check — diff a live page's web accessibility (a11y) violations against a baseline. By default it compares your uncommitted changes (stash-based); pass `--branch [<name>]` to compare against a branch. Reports the new WCAG violations introduced, the ones fixed, and the count of pre-existing ones. Use it for 'did my change break accessibility', 'what a11y issues did this PR add', or as a CI gate. For a full scan of one page use `accessibility-scan`; for a whole site use `accessibility-audit`.

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

Whole site or product — a full web accessibility (a11y) audit against WCAG 2.2, following the WCAG-EM methodology. Defines scope, samples representative pages and flows, runs the automated tier (`accessibility-scan`) and the hands-on manual tier (`accessibility-inspect`), and produces one conformance report. Grades each finding by severity and evidence basis, and states per-criterion conformance as pass, fail, or undetermined (needs a human). Use it for 'audit my site for accessibility', 'is this product accessible', 'a11y audit', 'WCAG or Section 508 conformance report', or any multi-page assessment. Assesses; does not fix (use `accessibility-fix`) or diff (use `accessibility-diff`). For a single page use `accessibility-scan`; for hands-on keyboard and screen-reader checks use `accessibility-inspect`.

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

Remediation only — repair web accessibility (a11y) violations against WCAG 2.2 with a baseline, edit, and verify loop. Takes a target (URL, files, directory) or a findings worklist from `accessibility-scan`/`accessibility-inspect`/`accessibility-audit`, applies mechanical fixes as given, leaves TODOs for visual or contextual judgment, and verifies by re-running the baseline check. It only fixes. To find issues use `accessibility-scan` (one page, automated), `accessibility-inspect` (one page, manual), or `accessibility-audit` (whole site, WCAG-EM); to check for regressions use `accessibility-diff`. Use it for 'fix the a11y issues in X', 'make this accessible', 'add missing alt text and labels', 'apply these accessibility fixes', 'remediate these violations'.

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

One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.

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

Revisa los cambios de UI en cuanto a accesibilidad — contraste de color, navegación por teclado, gestión del foco, uso de ARIA y texto alternativo. Úsalo cuando la persona pida una revisión de a11y/accesibilidad, verificar el cumplimiento de WCAG, el soporte de teclado, la compatibilidad con lectores de pantalla o el manejo del foco (p. ej. "¿es accesible este modal?", "audita la a11y del formulario").

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

Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.

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

日本語Web UIの素材集。既定配色は暫定標準カラー(ブルー基調・ライトのみ・色は役割トークンだけを参照し、主操作は action-primary-*、状態は status-* に固定)。明示指定時だけMode B Pop。タイポと数値表記・レスポンシブ4段・部品HTML/CSS・モーションとa11y・情報設計の工程と表示形式の導出・動く参照実装(assets/reference)・コントラスト検査/トークン生成/旧配色の自動移行スクリプトを持つ。設計判断と体験の規律は含めない(Skill ux-design から参照される後工程)。UIの実装・見た目のレビュー・配色の導入や移行で必ず参照する。

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

Production-grade accessibility skill for WCAG 2.2 AA compliance. Covers auditing, remediation, component authoring, and validation workflows. Auto-invoked for UI implementation, a11y fixes, and accessibility testing.

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

Use when you need to run real accessibility tests — Playwright keyboard interactions, axe-core scanning, visual regression, and WCAG 2.2 compliance checks. The measurement layer that feeds evidence into a11y-critic reviews.

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

Accessibility audit for CSS covering focus styles, color contrast, text sizing, screen reader support, and WCAG compliance. Provides actionable fixes. Use when auditing accessibility or fixing a11y issues.

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

Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.

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

Implement accessibility. TRIGGERS - Use when user needs help with a11y-implementation-guide related tasks.

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

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

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

Accessibility audit for CSS covering focus styles, color contrast, text sizing, screen reader support, and WCAG compliance. Provides actionable fixes. Use when auditing accessibility or fixing a11y issues.

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

Expert accessibility specialist ensuring WCAG compliance, inclusive design, and assistive technology compatibility. Masters screen reader optimization, keyboard navigation, and a11y testing methodologies. Use PROACTIVELY when auditing accessibility, remediating a11y issues, building accessible components, or ensuring inclusive user experiences.

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

Audits and implements web accessibility (a11y) following WCAG 2.1 guidelines with ARIA patterns, keyboard navigation, screen reader support, and contrast checking. Use when users request "accessibility audit", "a11y review", "WCAG compliance", "screen reader support", or "keyboard navigation".

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

Find links that use identical text but lead to different URLs. Review the rendered page and suggest distinct labels or consistent destinations so readers, including people using screen readers, can understand where each link goes.

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

• Find identical link text with different destinations
• Improve labels in screen reader link lists
• Review links in shared components

Find empty headings or headings containing only whitespace in rendered web pages. Guide fixes by adding descriptive text or removing unnecessary heading tags, helping screen reader users navigate a meaningful document structure.

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

• Find empty headings in web pages
• Review components that use headings only for styling
• Check heading navigation with a screen reader