Accessibility linting guides

Practical workflows for finding semantic accessibility issues in the editor, local scripts, and CI without treating static analysis as a replacement for rendered or manual testing.

• How to use an accessibility linter in VS Code

  Set up ZemDomu in VS Code to catch semantic accessibility issues, scan a workspace, and fix HTML, JSX, TSX, and Vue findings earlier.

• React accessibility linting across components

  Learn how to lint React and TSX accessibility across component boundaries, including heading hierarchy, accessible names, and CLI checks.

• Vue accessibility linting across components

  Find semantic accessibility issues in Vue templates and imported components with examples, setup steps, and clearly stated limitations.

• How to find cross-component accessibility issues

  See how accessibility bugs escape single-file linting and how ZemDomu checks the same component tree in the editor, CLI, and CI.

• Accessibility linting with GitHub Actions

  Add ZemDomu to GitHub Actions to lint HTML, JSX, TSX, and Vue, annotate pull requests, and troubleshoot failed checks.