Build an Accessibility SaaS Platform in two phases: Phase 1 – Accessibility Plugin (User Assistive Overlay Tool) Phase 2 – Accessibility Scanning, Dashboard & Remediation Module Platform must align with automated-detectable criteria of Web Content Accessibility Guidelines 2.1 / 2.2 Level AA Scanning engine to leverage established open-source libraries (e.g., axe-core / Pa11y) — not build from scratch. PHASE 1 – Accessibility Plugin (Overlay Tool) 1. Objective Develop a JavaScript-based accessibility plugin that website owners can embed via script tag. The plugin enhances user accessibility experience but does NOT claim full WCAG compliance. 2. Functional Requirements A. Plugin Deployment JavaScript snippet integration Async loading CDN-hosted Lightweight (minimal performance impact) Compatible with React / Angular / Vue / static websites B. Accessibility Features (User-Side Controls) Visual Adjustments Text size increase/decrease Line height adjustment Letter spacing adjustment High contrast mode Dark/light mode Grayscale mode Highlight links Highlight headings Dyslexia-friendly font toggle Navigation Assistance Focus highlight Keyboard navigation enhancement Skip-to-content support Reading guide Pause animations Larger cursor option C. Plugin UI Requirements Fully keyboard accessible Screen-reader compatible WCAG-compliant UI structure Proper ARIA usage Proper focus management Meets contrast standards D. Technical Requirements Shadow DOM isolation (preferred) No conflict with host site Responsive design Cross-browser support Works on dynamic SPA sites Configurable branding (logo, colors) E. Admin Panel (Basic) Account registration/login Site registration Script snippet generation Basic usage stats 3. Non-Functional Requirements Secure hosting Scalable architecture Multi-tenant Logging Error monitoring 4. Deliverables (Phase 1) Plugin script Admin dashboard Deployment guide Basic documentation PHASE 2 – Accessibility Scanning & Compliance Module (Lean MVP) 1. Objective Build an automated accessibility scanning module using established open-source engines aligned with WCAG 2.1/2.2 Level AA (automated-detectable criteria only). Single-site focus for MVP. Manual scan trigger only. 2. Technical Approach Use axe-core or equivalent open-source library Use headless browser (Puppeteer/Playwright) Backend-based scan orchestration Store results in database Build reporting dashboard 3. Functional Requirements A. Automated Accessibility Scanning URL-based scan Crawl basic internal pages (define max depth – vendor to propose) Manual scan trigger Detect automated WCAG violations Severity classification: Critical Major Minor Store scan history (basic retention) Page-level issue breakdown Handle dynamic SPAs B. Simplified Compliance Dashboard (Lean MVP) Overall accessibility score Total issues by severity WCAG principle grouping: Perceivable Operable Understandable Robust Page-level issue list CSV export only No advanced PDF reporting (deferred) C. Remediation Module (Critical Issues Only) For detected critical issues: Issue description Why it matters WCAG reference mapping Suggested fix guidance Sample code snippet (generic HTML level) No AI-based fix generation. No automatic DOM fixing. No workflow system in MVP. 4. Out of Scope (Phase 2 MVP) Multi-site portfolio management Scheduled scans Enterprise workflow AI remediation Auto-fix engine Branded executive PDF reporting Legal certification TECHNICAL STACK EXPECTATIONS (Vendor to Propose) Preferred: Backend: Node.js Puppeteer or Playwright REST API PostgreSQL or MongoDB Frontend: React / Vue (vendor suggestion welcome) Infrastructure: AWS / GCP / Azure Dockerized deployment Basic scalability design SECURITY REQUIREMENTS Isolated headless browser execution Timeout handling Malicious page protection HTTPS only Basic authentication & RBAC PERFORMANCE EXPECTATIONS Scan execution time target (vendor to propose) Max page limit per scan (vendor to define) Memory management strategy ESTIMATION REQUEST TO VENDORS Please provide separately: Phase 1: Timeline Cost Team structure Assumptions Phase 2 (Lean MVP): Timeline Cost Infrastructure estimate Technical architecture approach Limitations Ongoing Maintenance Estimate (Monthly)