Compétences better-accessibility

📦

better-accessibility

Name: better-accessibility
Author: jakubkrehel

Révision du contenu r1 Sûr ⚙️ Commandes externes

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.

Prend en charge: Claude Codex Code(CC)

🥉 77 Bronze

Maintain this Skill? Claim it 🥉 77 Bronze

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/jakubkrehel-better-accessibility.md manifest signé GET /api/skills/jakubkrehel-better-accessibility/manifest lockfile signé GET /api/skills/jakubkrehel-better-accessibility/lockfile

Tester

Utilisation de « better-accessibility ». Review an icon-only delete control that has no accessible name.

Résultat attendu:

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.

Utilisation de « better-accessibility ». Review a form that shows errors through red borders alone.

Résultat attendu:

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.

Utilisation de « better-accessibility ». Review a success toast whose polite announcement region appears with its message.

Résultat attendu:

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.

Audit de sécurité

Sûr

v1 • 09/10/2026 Ouvrir le rapport versionné

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.

Fichiers analysés

700

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

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

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

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>

Carte intégrable

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

Citations académiques (APA · BibTeX · CFF)

Citation APA

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

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

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces prompts

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.

Bonnes pratiques

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.

Éviter

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.

Foire aux questions

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.