writing-test-library-entries

name	writing-test-library-entries
description	Guidelines for writing accessibility test library entries including tests and subtests with proper descriptions and automation notes

Writing Test Library Entries

Use this skill when: Creating new test entries, editing existing test descriptions, or reviewing test library content for consistency.

Test library files:

• src/_data/accessibility-tests/test-library/1-perceivable.yml
• src/_data/accessibility-tests/test-library/2-operable.yml
• src/_data/accessibility-tests/test-library/3-understandable.yml
• src/_data/accessibility-tests/test-library/4-robust.yml
• src/_data/accessibility-tests/test-library/_config.yml

Complete Guidelines

All guidelines for writing and editing test library entries live in:

src/_data/accessibility-tests/test-library/README.md

Read the following sections before creating or editing entries:

• Test Structure — Required and optional fields for each test entry
• Writing Test and Subtest Entries — Detailed guidelines for description_short, description_full, and automation_notes with good/bad examples
  • Subsections: description_short, description_full, automation_notes, Plain Language Principles, Finding Good Examples, Review Checklist
• Adding New Tests — Step-by-step workflow for adding new test entries

Key Reminders for AI Agents

1. description_short: Concise, plain language, present tense, no "When you..." format
2. description_full: ALWAYS use "When you [action], you [result]" format
3. automation_notes: Required for full and partial automation coverage; describe what can be automated and what requires manual testing
4. Validate YAML: Ensure proper YAML syntax before saving changes
5. Cross-reference examples: Check existing entries in the YAML files for patterns