Marketing Site Versus Product App
A public marketing-site scan is only the starting point. Product accessibility also depends on authenticated screens, workflows, roles, data tables, notifications, and custom components.
Enterprise buyers may ask for evidence, roadmap, exception handling, support process, and VPAT documentation.
High-Risk SaaS Components
Review tables, filters, dropdowns, modals, tabs, charts, drag-and-drop, keyboard shortcuts, date pickers, onboarding checklists, and toast notifications.
Custom design-system components should be tested once and then reused consistently.
Procurement Readiness
Create a remediation backlog, owner map, test evidence folder, accessibility statement, support channel, and VPAT-readiness checklist before major enterprise reviews.
Frequently asked questions
Can a public website scan assess a SaaS product?
Only partly. It can inspect public pages, but authenticated workflows and product UI need a scoped manual review.
When should SaaS teams start accessibility work?
Start before procurement asks. Accessibility is much easier when design-system components and QA habits are already in place.