accessibility-engineering
Audit and Fix Web Accessibility Issues
Automated checks miss barriers that affect users navigating by keyboard or screen reader. Combine scanner findings with manual tests to prioritize fixes and verify them.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "accessibility-engineering" from https://skillstore.io/skills/addyosmani-accessibility-engineering.md and its manifest at https://skillstore.io/api/skills/addyosmani-accessibility-engineering/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "accessibility-engineering". Review a form with an unlabeled email input and an error message shown only in red.
Expected outcome:
- The email input needs an associated visible label so assistive technology can announce its purpose.
- Add error text and associate it with the input. Verify the error without relying on color.
- Screen reader behavior remains untested until someone checks it with a named browser and screen reader.
Using "accessibility-engineering". Summarize an audit in which axe completed but pa11y did not return a valid report.
Expected outcome:
- The URL audit is incomplete. Axe completed, but pa11y did not produce a valid report.
- Do not report a combined violation count. Resolve the pa11y failure and rerun the audit.
Security Audit
Medium RiskMost alerts describe Markdown formatting, documentation links, or routine report handling. The script embeds environment-derived paths in JavaScript, automatically runs npm packages, and opens user-supplied targets with no enforced audit scope. Page content enters the reports, but the reviewed files show no evidence of deliberate data exfiltration or embedded prompt injection.
Confirmed security concerns (3)
Capability review items (15)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (16)
๐ Filesystem access (26)
๐ Network access (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/addyosmani-accessibility-engineering/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/addyosmani-accessibility-engineering?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/addyosmani-accessibility-engineering?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-accessibility-engineering/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/addyosmani-accessibility-engineering.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
addyosmani. (2026). accessibility-engineering security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-accessibility-engineering/audits/1BibTeX citation
@techreport{addyosmani-addyosmani-accessibility-engineering-2026,
author = {addyosmani},
title = {accessibility-engineering security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/addyosmani-accessibility-engineering/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: "accessibility-engineering security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-11-19"
url: "https://skillstore.io/skills/addyosmani-accessibility-engineering/audits/1"
identifiers:
- type: other
value: "skillstore:addyosmani-accessibility-engineering:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Fix an inaccessible form
Verify missing labels and keyboard problems in an existing form. Make targeted fixes and retest the affected controls.
Verify a release candidate
Pair scanner reports with manual checks on a staging page. Record the browser, assistive technology, and checks that could not be run.
Prioritize accessibility findings
Review verified barriers and separate them from untested items. Use the impact on key user tasks to decide what should be fixed first.
Try These Prompts
Review this form for missing labels, unclear errors, and keyboard access. Explain each issue and list the manual checks I should run.
Review these axe-core and pa11y findings. Group reports of the same issue, identify the affected controls, and say how to verify each issue manually.
Plan a keyboard and screen reader retest for this checkout modal. Check initial focus, Escape, focus return, and error announcements. Mark unavailable checks as untested.
Audit the approved staging page using existing local tools. Ask before installing anything. Compare scanner findings with manual results and separate verified failures from checks that were not run.
Best Practices
- Verify each automated finding in the browser before changing the interface.
- Use native HTML controls where possible and retest behavior after each fix.
- Record the browser, assistive technology, and checks that were not run.
Avoid
- Claiming conformance after a clean automated scan.
- Adding ARIA labels to custom controls without fixing their keyboard behavior.
- Running an audit on an unapproved target or sharing raw reports without checking for sensitive content.
Frequently Asked Questions
Can this skill certify WCAG 2.2 AA conformance?
Which tools run in URL and file modes?
What do I need to run the wrapper?
What happens when a scanner fails?
Will the skill verify screen reader behavior for me?
Can a report contain sensitive page content?
Developer Details
Author
addyosmaniLicense
Unknown
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
b801e7ae7b71c5eca7822ed69f7a16176f3b6ed1
Maintenance freshness
11/20/2026
Usage
0 downloads ยท 0 views
File structure