Inspiration

An accessibility error list doesn't show the whole journey. We wanted to show where someone navigating without sight gets stuck while trying to complete a task.

What it does

Give Blindspot a URL and a task. A Nemotron agent navigates Chrome using keyboard actions and a simulated screen reader based on Chrome's accessibility tree. The app streams the journey, identifies blockers, runs axe-core checks and suggests code fixes grounded in accessibility guidance retrieved with Tavily. A built-in rail-booking demo has broken and fixed versions for comparison.

How we built it

Next.js and TypeScript provide the app. Playwright controls Chrome. Nebius Token Factory hosts the Nemotron models used for navigation, diagnosis and fix generation. Tavily retrieves supporting guidance from sources including W3C and MDN. The deployment uses Vercel and serverless Chromium.

Challenges

Keeping keyboard navigation separate from visual information, checking quoted markup against captured code, and fitting browser sessions within serverless time limits.

Accomplishments

Combining the navigation journey, accessibility checks, diagnosis and suggested fixes in one interface, with a broken/fixed demo to make the differences visible.

Built With

  • axe-core
  • nebius-token-factory
  • nemotron
  • nextjs
  • playwright
  • tavily
  • typescript
  • vercel
Share this project:

Updates

Submission history