How kayla9011/accessibility-checker-app works
Accessibility Checker accepts a website URL, runs an accessibility audit, and presents scores, violations, passes, and remediation guidance. The analyze route prefers Backend-B and includes a local mock fallback; a separate scrape route uses Puppeteer to package page content. The supplied source does not show how the URL form submits or how the analyze route’s backend helpers are wired in its omitted sections, so those connections are left out. The README describes Australian accessibility requirements; the page also advertises WCAG 2.1 checks.
Main entry points: analyze/route.ts Analyze endpoint · page.tsx Audit home · scrape/route.ts Scrape endpoint · results-dashboard.tsx Results dashboard
Components 14
User interface
- Audit home
app/page.tsx - URL form
components/url-input-form.tsx - Results dashboard
components/results-dashboard.tsx - Remediation guidance
components/recommendation-card.tsx
Audit workflow
- Analyze API client
lib/api.ts - Analyze endpoint
app/api/analyze/route.ts - Mock analysis
app/api/analyze/route.ts - Audit result types
lib/types.ts
Page scraping
- Scrape endpoint
app/api/scrape/route.ts
Audit integration
- Backend-B client
lib/backendB.ts
Other components
- Website auditor
- Public website
- Backend-B service
- Puppeteer browser
Connections 12
- Website auditor → Audit home: opens
- Audit home → URL form: renders
- Audit home → Results dashboard: renders results
- Results dashboard → Remediation guidance: renders guidance
- Analyze API client → Analyze endpoint: POSTs URL
- Analyze endpoint → Backend-B client: imports audit helpers
- Analyze endpoint → Mock analysis: falls back
- Analyze endpoint → Audit result types: uses result types
- Scrape endpoint → Puppeteer browser: launches
- Puppeteer browser → Public website: loads and reads
- Scrape endpoint → Public website: returns page content
- Backend-B client → Backend-B service: creates and polls audits