quality-accessibility

To audit CLI output for accessibility, you verify that critical interaction paths do not rely on color alone and provide text labels. This ensures color-blind users and screen readers can effectively interact with the interface.

NO_COLOR support means the CLI rendering must gracefully degrade to plain text when the environment variable is set. This accessibility standard ensures that color-coded output does not hinder operators who cannot perceive color distinctions.

Running an accessibility audit on markdown documentation requires reviewing the files for proper alt text, header continuity, and table semantics. This verifies that screen readers can accurately navigate and interpret the generated docs.

Yes, you can assess interactive dashboard widgets for low-vision and screen-reader compatibility. The audit evaluates the interactive UI to ensure non-visual alternatives are available for all operator-facing surfaces.

To fix CLI interfaces depending on Unicode characters, you must identify the Unicode dependence and propose text labels as alternatives. This removes barriers for environments lacking full Unicode rendering support.