Why did we build AuditIn? Before AuditIn, we kept hearing the same request: “Can you audit our website for accessibility?” The traditional process was often manual, time-consuming and expensive. Days of testing, followed by a detailed report — which could already be outdated as soon as the website was updated. We wanted to change that. We started building AuditIn around a simple idea: accessibility should be something you continuously work on, not something you check once a year. The first challenge was automating reliable accessibility testing against WCAG 2.2. We integrated two complementary testing engines, Lighthouse and axe-core, to scan websites and identify accessibility issues at the level required — A, AA or AAA. Then we realised that a website is much more than its HTML. The content published on it matters too. PDFs, videos and other digital materials can create significant accessibility barriers, so we expanded AuditIn to analyse PDF documents according to ISO 14289-1 (PDF/UA) and to help teams address accessibility beyond the webpage itself. From there, the platform evolved further: AI-powered suggestions for fixing issues directly in the code, accessibility statement generation, continuous monitoring of multiple pages and websites, and tools such as a widget and contrast checker. Throughout the process, one principle remained at the centre: We don't want to give you another accessibility report to archive. We want to give you a tool you actually use — every time you publish something new. AuditIn is our attempt to make digital accessibility more continuous, practical and actionable. We're excited to finally share it with the Product Hunt community! 🚀 Try it here: https://auditin.eu

AuditIn

New: PDF/UA Accessibility Audit

New: PDF/UA Accessibility Audit