Accessify

Accessify is a web accessibility scanning platform built with .NET services, a Next.js frontend, and .NET Aspire orchestration. It crawls sites, runs browser-based accessibility checks, streams scan progress in real time, and supports review and remediation workflows. The platform is deployed to Kubernetes with a GitLab CI/CD pipeline and Python-based deploy tooling.

The project helps teams find accessibility issues earlier and inspect scan results in one place. Its distributed design separates crawling, scanning, realtime updates and API concerns into microservices, so each part can evolve independently.

• accessify-ai.AppHost: local orchestration for the full stack
• accessify-ai.Server: main backend API
• accessify-ai.Crawler: site crawling service
• accessify-ai.AccessibilityEngine: accessibility scan engine
• accessify-ai.RealTime: realtime updates and notifications
• accessify-ai.Proxy: gateway for frontend and backend traffic
• accessify-ai.ServiceDefaults: shared telemetry, health checks and service discovery
• accessify-ai.*MigrationService: EF Core migration runners for each database
• accessify-ai.frontend: Next.js user interface
• infra/: container builds, Kubernetes manifests and CI scripts

• .NET 10 SDK
• Node.js 18 or newer
• Python 3.10 or newer (deploy scripts and CI tooling)
• Docker
• PostgreSQL
• RabbitMQ
• Redis
• Browserless Chromium for browser automation
• kubectl and kubeseal (for cluster operations and secret management)

1. Start the full local stack with the Aspire host:

dotnet run --project accessify-ai.AppHost

2. Start the frontend separately if you want to work on the UI in isolation:

cd accessify-ai.frontend
npm install
npm run dev

3. Common frontend scripts:

npm run build
npm start
npm run lint
npm run typecheck
npm run generate-api

• Database, RabbitMQ, Redis, Mailpit, and Browserless are wired up by the AppHost for local development.
• The AppHost configures three databases: server-db, crawler-db, and accessibility-engine-db.
• Each database has a dedicated migration service that runs at startup to apply schema changes.
• Frontend API generation uses orval and disables TLS verification for local development.
• Production deployments target k3s via manifests in infra/k8s/base/ and are applied automatically by GitLab CI.

This is a Chas Challenge project, meaning that outside contributions are not allowed.

This repository is maintained by Team Kermit of Chas Academy

Frontend/Backend department

• Elvira Mariesdotter
• Emma Karlholm
• Gustav Keller
• Johannes Flodin
• Theo Lilliesköld

DevOps department

• Sam Jaudat

UI/UX department

• Jenny Précenth
• Rabbiya Waqar