This guide explains the recommended workflow for finding accessibility issues, planning corrections, and validating the result in Pluro. Automated scanning provides evidence for remediation, but does not replace manual testing with a keyboard, screen reader, and realistic user tasks.
1. Choose your website and page
- Sign in to MyPluro and open the licensed website from the Portal.
- Select the page to assess. Confirm the URL and the environment before making changes.
- Check that access and permissions are appropriate for your organization.
2. Scan and review
- Run a scan on the selected page using the Scanner.
- Review each finding, its affected element, the rule or description, and the available evidence.
- Prioritize issues by impact, recurrence, and the affected user journey.
For report access and role restrictions, see HTML Report page functionality.
3. Plan remediation
Choose an appropriate response: a source-code change by a developer, an AI-assisted suggestion for review, or a Pluro Fixer remediation where supported. Treat generated suggestions as proposed work, not verified fixes.
See Introducing Pluro AI Insight for the distinction between AI suggestions, review-required work, and manual fixes.
4. Test and validate
- Review any proposed JavaScript or CSS and test in a suitable environment.
- Check the affected flow using keyboard navigation and applicable assistive technologies.
- Run the scanner again and compare findings.
- Record what was changed, the test evidence, and unresolved issues.
Next steps
- Use a dev/stage environment
- Review SPA-specific considerations
- Test real user flows with Behavior Scan
Product verification before publication: Confirm the current Portal navigation, exact Scan/Reports labels, and fix deployment flow against the live product.