better-accessibility
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.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу 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.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «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.
Аудит безопасности
Безопасно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.
Факторы риска
⚙️ Внешние команды (40)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/jakubkrehel-better-accessibility/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](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 [component] for accessible names, native semantics, and visible focus. Explain each barrier and recommend the smallest fix.
Review and fix [form] labels, autocomplete, validation, and pending submission behavior. Preserve project conventions and report checks you cannot verify.
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 [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?
Which accessibility standard does it use?
Can it fix project code?
Does it include automated accessibility testing?
Does it measure color contrast?
Does a successful review guarantee compliance?
Сведения для разработчиков
Автор
jakubkrehelЛицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Ссылка
e406bf64b5db6e514879399e87b346fa7ff7c2fb
Актуальность поддержки
11.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов