deer-sense

Audit digital interfaces for WCAG compliance using axe-core and manual testing.

5|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/AutumnsGrove/Lattice --skill deer-sense
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deer-sense
Source: https://github.com/AutumnsGrove/Lattice/tree/main/.claude/skills/deer-sense
Command: npx skills add https://github.com/AutumnsGrove/Lattice --skill deer-sense

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and helps fix accessibility barriers in digital interfaces, ensuring inclusivity for all users.

Core Features & Use Cases

  • Accessibility Auditing: Performs comprehensive checks for visual, motor, cognitive, and auditory accessibility issues.
  • Automated & Manual Testing: Integrates automated scanning tools (axe-core) with manual testing guidance for keyboard and screen reader users.
  • Use Case: When launching a new feature, use this Skill to audit its accessibility compliance against WCAG 2.1 AA standards, identifying and prioritizing fixes before release.

Quick Start

Use the deer-sense skill to audit the accessibility of the provided URL.

Frequently Asked Questions about deer-sense

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a digital interface for WCAG 2.1 AA compliance?

To audit a digital interface for WCAG compliance, this Skill guides you through listening, scanning, testing, guiding, and protecting phases. It integrates automated axe-core scanning with manual testing to identify visual, motor, cognitive, and auditory accessibility barriers.

What is the difference between automated and manual accessibility testing?

Automated accessibility testing uses tools like axe-core to scan code for common barriers, while manual testing involves verifying keyboard navigation and screen reader compatibility. This Skill integrates both methodologies to ensure digital environments are fully usable by individuals with diverse needs.

How do I check if my website supports keyboard navigation and screen reader compatibility?

You can check keyboard navigation and screen reader compatibility by following the manual testing guidance provided. The Skill addresses these specific inclusive design principles, helping you identify and fix motor and visual accessibility barriers that automated tools might miss.

Can I use axe-core alone for a complete inclusive design audit?

axe-core alone cannot perform a complete inclusive design audit because it only detects automated code-level issues. This Skill supplements automated axe-core scanning with manual testing methodologies to evaluate cognitive, auditory, and keyboard navigation barriers against WCAG standards.

What steps are involved in an accessibility audit for a new feature release?

An accessibility audit for a new feature involves scanning with automated tools, testing keyboard and screen reader interactions, and evaluating visual, motor, cognitive, and auditory barriers. This Skill prioritizes identified fixes against WCAG 2.1 AA standards to complete before release.

Why does my automated accessibility scan miss keyboard navigation issues?

Automated accessibility scans miss keyboard navigation issues because they cannot simulate manual user interactions. This Skill addresses this limitation by providing manual testing guidance alongside automated axe-core scans to ensure accurate screen reader and keyboard compatibility verification.