Codex MCAF Non-Functional Requirements for Keyboard Accessibility
Turn broad quality goals into verifiable acceptance conditions and record them in the relevant feature or architecture document.
中文Install in Codex
Codex with PrompterOne or a project using MCAF conventions, a feature spec, and an identified quality attribute.
- Copy the entire pinned `.codex/skills/dotnet-mcaf-nfr/` directory to `.agents/skills/dotnet-mcaf-nfr/` in the target checkout.
- Open Codex in that checkout and invoke `$dotnet-mcaf-nfr` with the example task and desired output.
Example task
Invoke `$dotnet-mcaf-nfr` for a practice settings form. Define keyboard focus order and how the error feedback will be checked.What to check
The spec lists repeatable keyboard steps, expected focus movement, and a check for perceivable validation errors.
Original SKILL.md on GitHub · Updated
Frequently asked question
How do I make ease of use testable?
Choose a concrete user journey and record observable behavior and how to verify it.