ARIA Name Explainer: Public Worked Example

Explain where every control's accessible name comes from — and, when there is no name, which sources were tried and what each one produced.

This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.

Run the checked-in example

node bin/aria-name-explainer.mjs --snapshot examples/checkout-clean.json

Read the result

(The last paragraph is one line in the real output; it is wrapped here.)

Where this check stops

Every limit is enforced, reported when it is hit, and tested: --max-file-bytes, --max-nodes, --max-depth, --max-controls, --max-label-refs and --max-findings. An unknown limit name is rejected. Defaults are in docs/naming-rules.md.

Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.

Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.