Pluro provides developer-oriented workflows that can complement accessibility scanning and remediation. This guide outlines how teams should document use of the VS Code accessibility copilot; exact installation and commands must be confirmed against the released extension.
Recommended developer workflow
- Confirm that your team uses the current, officially released Pluro VS Code extension.
- Open the relevant repository and select a focused component or accessibility issue.
- Review suggested changes for semantic correctness, keyboard interactions, and side effects.
- Run project linting, unit tests, and relevant accessibility tests.
- Validate in the browser and record a manual test when the issue involves interaction.
Review standards
- Do not introduce hard-coded labels that are incorrect for the interface.
- Do not add tabindex values or ARIA attributes without verifying the accessible behavior.
- Treat any generated patch as untrusted until reviewed and tested.
- Keep credentials and customer data out of prompts or issue examples unless authorized.
Further reading
Product verification before publication: Confirm marketplace listing, release version, commands, supported languages, authentication, and safety-validation capabilities before publishing instructions.