技能 better-accessibility

📦

better-accessibility

Name: better-accessibility
Author: jakubkrehel

內容修訂 r1 安全 ⚙️ 外部命令

Review and Fix Web Accessibility

Web interfaces can block users who rely on keyboards, screen readers, or zoom. This skill guides targeted fixes and reports WCAG 2.2 criteria with verification limits.

支援: Claude Codex Code(CC)

🥉 77 銅級

Maintain this Skill? Claim it 🥉 77 銅級

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

Review the Skillstore skill "better-accessibility" from https://skillstore.io/skills/jakubkrehel-better-accessibility.md and its manifest at https://skillstore.io/api/skills/jakubkrehel-better-accessibility/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/jakubkrehel-better-accessibility.md 已簽名 manifest GET /api/skills/jakubkrehel-better-accessibility/manifest 已簽名 lockfile GET /api/skills/jakubkrehel-better-accessibility/lockfile

測試它

正在使用「better-accessibility」。 Review an icon-only delete control that has no accessible name.

預期結果:

High severity: The delete control has no accessible name, so screen-reader users cannot identify its action.
WCAG 4.1.2: Give the control a descriptive accessible name and hide its decorative icon from assistive technology.
Verification: Source review identifies the missing name. Browser accessibility-tree inspection and screen-reader testing are not verified.

正在使用「better-accessibility」。 Review a form that shows errors through red borders alone.

預期結果:

The form communicates validation errors only through color, creating a barrier for users who cannot distinguish the border state.
WCAG 1.4.1 and 3.3.1: Add inline error text, associate it with each failing field, and focus the first invalid field after submission.
Verification: Confirm that errors are announced with their fields. Target browser and screen-reader behavior is not verified without testing.

正在使用「better-accessibility」。 Review a success toast whose polite announcement region appears with its message.

預期結果:

The newly mounted polite region may not announce the success message consistently.
Keep an empty status region mounted before updates, then change its text when the operation completes.
Verification: Test repeated announcements with the target screen readers. Leave keyboard focus on the current control.

安全審計

安全

v1 • 2026/10/9 開啟版本化報告

All 50 static findings are false positives from Markdown formatting, CSS, HTML attributes, or accessibility review terminology. The reviewed files contain accessibility guidance, not shell execution or system reconnaissance. No evidence found of prompt injection, credential collection, data exfiltration, or other malicious intent.

已掃描檔案

700

分析行數

複核項目

已忽略的誤報

最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。

審計單位: codex

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

https://skillstore.io/skills/jakubkrehel-better-accessibility/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/jakubkrehel-better-accessibility/security.svg)](https://skillstore.io/skills/jakubkrehel-better-accessibility?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/jakubkrehel-better-accessibility?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jakubkrehel-better-accessibility/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/jakubkrehel-better-accessibility.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

學術引用 (APA · BibTeX · CFF)

APA 引用

jakubkrehel. (2026). better-accessibility security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jakubkrehel-better-accessibility/audits/1

BibTeX 引用

@techreport{jakubkrehel-jakubkrehel-better-accessibility-2026,
  author = {jakubkrehel},
  title = {better-accessibility security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/jakubkrehel-better-accessibility/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "better-accessibility security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "jakubkrehel"
date-released: "2026-10-09"
url: "https://skillstore.io/skills/jakubkrehel-better-accessibility/audits/1"
identifiers:
  - type: other
    value: "skillstore:jakubkrehel-better-accessibility:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 評分

評分依據證據置信度: 中

架構

可維護性

內容

社群

規範符合度

你可以打造什麼

Fix Keyboard Barriers in Components

Review dialogs, tabs, and navigation for keyboard paths, visible focus, and focus restoration before release.

Verify Accessible User Flows

Check form submission, error announcements, and status updates through keyboard and screen-reader workflows.

Review Shared Interface Patterns

Assess shared controls for names, roles, states, target sizes, and reduced-motion behavior across a component library.

試試這些提示

Review a Single Control

Review [component] for accessible names, native semantics, and visible focus. Explain each barrier and recommend the smallest fix.

Fix an Accessible Form

Review and fix [form] labels, autocomplete, validation, and pending submission behavior. Preserve project conventions and report checks you cannot verify.

Audit an Interactive Flow

Audit [flow] for keyboard navigation, modal focus, live announcements, and zoom. Cite applicable WCAG 2.2 criteria and separate observed failures from unverified checks.

Review a Shared Component Library

Review [component library] for systemic accessibility barriers. Fix shared root causes, group findings by principle and severity, and list all affected locations.

最佳實務

Provide the component scope and affected user flow, then request findings tied to WCAG criteria or concrete task barriers.
Preserve native HTML behavior and project styling conventions when applying accessibility fixes.
Combine source review with keyboard and screen-reader testing, and clearly mark checks that remain unverified.

避免

Treating a source-only review or automated audit as proof of complete accessibility conformance.
Adding ARIA roles to generic elements instead of using suitable native controls.
Removing focus indicators, blocking paste, or preventing zoom to preserve a visual design.

常見問題

Which AI tools support this skill?

The marketplace lists support for Claude, Codex, and Claude Code. Available project access and testing tools depend on your environment.

Which accessibility standard does it use?

It uses WCAG 2.2 Level A and AA criteria. It distinguishes recommendations and AAA targets from required thresholds.

Can it fix project code?

The instructions guide code fixes using existing project conventions. Applying changes requires an AI environment with access to the relevant files.

Does it include automated accessibility testing?

No testing engine is bundled. The guidance calls for automated audits when browser tools are available and marks unavailable checks as unverified.

Does it measure color contrast?

It identifies applicable contrast requirements but delegates rendered contrast measurement to better-colors. Color changes require a request.

Does a successful review guarantee compliance?

No. Results cover inspected components and completed checks only. Full conformance requires broader assessment, including manual testing with assistive technology.