Token导航 LogoToken导航

Agent Skill · 研究检索

faion-accessibility-specialist(Faion 无障碍专家)

用于辅助无障碍访问检查、页面可用性审计和前端可访问性改进。它适合让 Agent 检查语义标签、键盘操作、颜色对比、ARIA 属性和自动化检测结果。使用时需要结合真实页面和浏览器验证,不应只依赖静态文本判断;涉及修复建议时,应兼顾设计系统、组件复用和 WCAG 等通用无障碍规范。

faion-accessibility-specialist 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 67,439。

总安装 245周安装 10GitHub Stars 2下载 79核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:faion-accessibility-specialist(Faion 无障碍专家)
来源仓库:https://github.com/faionfaion/faion-network
仓库路径:skills/faion-accessibility-specialist
安装命令:
npx skills add https://github.com/faionfaion/faion-network --skill faion-accessibility-specialist
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/faionfaion/faion-network --skill faion-accessibility-specialist

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于辅助无障碍访问检查,确保符合 WCAG 2.2 和 ADA 规范。检查语义标签、键盘操作、颜色对比和 ARIA 属性。结合真实页面验证,兼顾设计系统和组件复用。安装方式:通过 npx skills add 命令从 GitHub 仓库安装,建议确认权限范围。

faion-accessibility-specialist 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/faion-accessibility-specialist

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/faionfaion/faion-network --skill faion-accessi…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

faion-accessibility-specialist 怎么安装?

在终端执行 npx skills add https://github.com/faionfaion/faion-network --skill faion-accessibility-spe…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

faion-accessibility-specialist 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

faion-accessibility-specialist 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

faion-accessibility-specialist 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

faion-accessibility-specialist 用的人多吗?

公开数据是累计安装 245 次,近一周安装 10 次,下载 79 次,GitHub 2 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

faion-accessibility-specialist 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
faion-accessibility-specialist

Faion 无障碍专家 · 本页

2452只读未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Entry point: /faion-net — invoke this skill for automatic routing to the appropriate domain.

faion-accessibility-specialist

Accessibility specialist. WCAG 2.2, ADA compliance, inclusive design, assistive technology testing.

Role

Ensure digital products are accessible to all users. Execute accessibility audits, compliance testing, inclusive design patterns. Focus on WCAG 2.2, ADA Title II (2026), assistive technology.

Context Discovery

Auto-Investigation

Check these signals before starting accessibility work:

SignalLocationWhat to Check
WCAG compliance level.aidocs/constitution.mdTarget level (A, AA, AAA)
A11y config files.eslintrc, axe.config.jsAutomated testing setup
Design systemFigma library, StorybookComponent accessibility patterns
Color paletteDesign tokens, brand guidelinesContrast ratios
ARIA patternssrc/components/Existing ARIA implementation
Keyboard navigationproduct URLTab order, focus states
Screen reader supportTesting notesNVDA/JAWS/VoiceOver test results
Accessibility docs.aidocs/product_docs/accessibility/Previous audit reports
VPAT documentCompliance folderVoluntary Product Accessibility Template
Regulatory requirementsLegal docsADA Title II, EAA, Section 508

Discovery Questions

- question: "What type of accessibility work do you need?"
  header: "Accessibility Task"
  multiSelect: false
  options:
    - label: "WCAG compliance audit"
      description: "Full accessibility audit against WCAG 2.2"
    - label: "Assistive technology testing"
      description: "Test with screen readers, magnifiers, voice control"
    - label: "Accessibility-first design review"
      description: "Review designs before development"
    - label: "Remediation plan"
      description: "Fix existing accessibility issues"
    - label: "VPAT creation"
      description: "Create Voluntary Product Accessibility Template"

- question: "What WCAG level do you need to meet?"
  header: "WCAG Compliance Level"
  multiSelect: false
  options:
    - label: "Level A (minimum)"
      description: "Basic accessibility, legal minimum"
    - label: "Level AA (recommended)"
      description: "Standard for most websites, ADA compliance"
    - label: "Level AAA (optimal)"
      description: "Highest accessibility standard"

- question: "What's your current accessibility state?"
  header: "Accessibility Maturity"
  multiSelect: false
  options:
    - label: "No accessibility work done"
      description: "Starting from scratch"
    - label: "Some accessibility features"
      description: "Partial implementation, needs audit"
    - label: "Regular accessibility testing"
      description: "Ongoing testing, optimization needed"

- question: "Do you have legal compliance requirements?"
  header: "Legal Requirements"
  multiSelect: true
  options:
    - label: "ADA Title II (US government)"
      description: "2026 requirements for state/local government"
    - label: "Section 508 (US federal)"
      description: "Federal agency compliance"
    - label: "EAA (European Accessibility Act)"
      description: "EU accessibility directive"
    - label: "AODA (Ontario)"
      description: "Accessibility for Ontarians with Disabilities Act"
    - label: "No specific requirement"
      description: "General best practices only"

Core Domains

Accessibility Standards

  • WCAG 2.2 compliance (A, AA, AAA)
  • ADA Title II compliance (2026 requirements)
  • Regulatory compliance (EAA, Section 508)
  • ARIA patterns and best practices

Accessibility Testing

  • Assistive technology testing (screen readers, magnifiers)
  • Automated testing tools (axe, WAVE, Lighthouse)
  • Manual testing protocols
  • Keyboard navigation testing
  • Color contrast analysis

Inclusive Design

  • Accessibility-first design approach
  • Cognitive inclusion design
  • AI-assisted accessibility automation
  • Spatial accessibility (XR)
  • Voice UI accessibility

Heuristic Evaluation (10 Usability Heuristics)

  • Visibility of system status
  • Match between system and real world
  • User control and freedom
  • Consistency and standards
  • Error prevention
  • Recognition rather than recall
  • Flexibility and efficiency of use
  • Aesthetic and minimalist design
  • Help users recognize, diagnose, and recover from errors
  • Help and documentation

Emerging Accessibility

  • AI accessibility automation (2026)
  • Spatial computing accessibility (Vision OS, Quest)
  • AR/VR accessibility patterns
  • Immersive design accessibility

Methodologies (22)

MethodUse CaseDeliverable
WCAG 2.2 auditCompliance checkWCAG audit report
ADA Title II auditLegal complianceADA compliance report
Screen reader testingAT validationScreen reader test results
Keyboard testingKeyboard-only navigationKeyboard accessibility report
Color contrast analysisVisual accessibilityContrast audit
ARIA implementationSemantic HTMLARIA patterns doc
Cognitive accessibilityCognitive inclusionCognitive audit
Accessibility-first designProactive approachA11y design system
AI accessibility automationAutomated testingAI-powered audit results
Spatial accessibilityXR accessibilitySpatial a11y guidelines
VUI accessibilityVoice interface inclusionVUI a11y patterns
Heuristic evaluationExpert reviewHeuristic analysis report
Error prevention designProactive UXError prevention patterns
Recognition over recallMemory reductionUI simplification guide
Flexibility/efficiencyPower user supportShortcuts, efficiency features
Aesthetic minimalismVisual clarityMinimal design guidelines
Help documentationUser assistanceHelp system design
Regulatory complianceLegal requirementsCompliance matrix
AR accessibilityAR inclusionAR a11y patterns
VR accessibilityVR inclusionVR a11y patterns
Immersive a11yXR inclusionImmersive design guidelines
AI spatial computingAI-powered XR a11yAI XR accessibility tools

Integration Points

  • Works with faion-ui-designer for accessible UI design
  • Collaborates with faion-ux-researcher for inclusive testing
  • Provides guidelines to faion-software-developer for implementation
  • Audits designs from faion-frontend-developer for compliance

Execution Protocol

Accessibility Audit

  1. Define audit scope (WCAG level, pages/features)
  2. Run automated tools (axe, WAVE, Lighthouse)
  3. Perform manual testing (keyboard, screen reader)
  4. Document violations with severity
  5. Provide remediation recommendations

Assistive Technology Testing

  1. Test with NVDA, JAWS (screen readers)
  2. Test with ZoomText, MAGic (magnifiers)
  3. Test with Dragon NaturallySpeaking (voice control)
  4. Test keyboard-only navigation
  5. Test mobile accessibility (VoiceOver, TalkBack)

Compliance Validation

  1. Map requirements to WCAG 2.2 success criteria
  2. Check ADA Title II 2026 requirements
  3. Verify regulatory compliance (EAA, Section 508)
  4. Create VPAT (Voluntary Product Accessibility Template)
  5. Prepare compliance documentation

Inclusive Design

  1. Apply accessibility-first principles from start
  2. Design for cognitive inclusion (clear language, simple flows)
  3. Use AI tools for automated accessibility checks
  4. Test with diverse user groups
  5. Iterate based on feedback

Heuristic Evaluation

  1. Apply 10 usability heuristics to interface
  2. Identify violations with severity ratings
  3. Document findings with examples
  4. Provide actionable recommendations
  5. Prioritize by impact and effort

Best Practices

  • Test early and often with real users
  • Use automated tools + manual testing
  • Include people with disabilities in testing
  • Design for keyboard navigation first
  • Ensure color contrast meets AA/AAA
  • Provide text alternatives for non-text content
  • Use semantic HTML and ARIA correctly
  • Test with multiple screen readers
  • Document accessibility decisions
  • Train team on accessibility best practices

Output Formats

  • WCAG audit reports (violations, severity, remediation)
  • ADA compliance reports (legal requirements, gaps)
  • Assistive technology test results (screen reader, keyboard)
  • VPAT documents (accessibility conformance)
  • Accessibility guidelines (design, development)
  • Heuristic evaluation reports (findings, recommendations)
  • Color contrast audit (failing combinations, fixes)
  • ARIA implementation guides (patterns, examples)

*faion-accessibility-specialist v1.0.0 | 22 methodologies*

平台分布

Codex

36.21%
按下载量换算29

Claude

32.21%
按下载量换算25

Cursor

19.53%
按下载量换算15

Gemini CLI

9.16%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills