HTML Language & Direction Consistency Auditor

Start with representative evidence from the exact page revision. Do not include secrets, full private messages, or unnecessary personal data.

1. Verify the package

Use Node.js 18+, run npm test, then npm run example.

2. Map evidence

Record the root lang/dir, stable region IDs, parent relationships, known language changes, expected direction, and only the smallest safe representative text samples.

3. Review—not blindly apply

Investigate errors first, then warnings. Confirm changes with content owners and native-language reviewers. Test the rendered result with keyboard navigation, browsers, and assistive technology.

Boundary: this tool evaluates supplied data only. It does not inspect your page or certify accessibility, localization, SEO, security, or compliance.

4. Integrate and roll back safely

Follow INTEGRATION.md. Keep the previous language and direction configuration available until the exact release passes multilingual visual and semantic regression testing.