What Livana Does and Why We Built It
Livana is an accessibility consultancy and tooling company. We run audits, help teams fix their accessibility issues, and build tools to make ongoing compliance less painful. This post explains who we are, what we do, and why we started.
Who we are
Livana was founded by three brothers. We are all developers. We have worked across frontend, backend, and infrastructure, and we have spent years dealing with accessibility in our own projects before making it the focus of a company.
We started Livana because we kept seeing the same problem. Teams would build a product, get close to launch, then scramble to make it accessible at the last minute. The results were predictably poor: bolted-on fixes that barely passed automated checks and did nothing for actual users with disabilities.
We thought there was a better way to do it, and we wanted to build the tools and processes to prove it.
What we do
Our work falls into three areas.
Accessibility audits. We test sites and applications against WCAG 2.2, using real assistive technology. That means screen readers, keyboard-only navigation, voice control, and magnification. We deliver findings as structured tickets with remediation guidance, not a PDF that collects dust.
Consultancy. We work with development teams to embed accessibility into their existing workflows. That could mean training, code reviews, design system guidance, or pairing on tricky ARIA patterns. The goal is to get teams to a point where they can handle accessibility themselves without needing us.
Lumi. This is our accessibility management platform. It scans your site with five engines, but it does more than produce a report. Every issue becomes an assignable ticket with evidence, remediation guidance, and AI-generated code fixes. Your team tracks progress through a backlog, syncs with Jira, gets Slack alerts on regressions, and exports branded PDF reports for stakeholders. When we run a manual audit, the findings go straight into Lumi as tickets alongside the automated scan results, so everything lives in one place.
How we approach the work
The single biggest thing we push for is getting accessibility into the development process early, rather than treating it as a final check before launch.
Retrofitting accessibility is expensive and the results are usually mediocre. When a component is designed and built with accessibility in mind from the start, the implementation is cleaner and the user experience is better. It also costs far less than reworking something that was built without it.
We offer automated scanning through Lumi, and it is useful for catching structural issues like missing labels, broken ARIA, and contrast failures. But scanning is not where the real work happens. Automated tools miss around 60% of WCAG issues, particularly anything involving interaction, reading order, or cognitive accessibility.
What separates a genuinely accessible product from one that passes a few automated checks is manual testing with real assistive technology. A person using NVDA, navigating by keyboard, or testing with voice control will find the issues that no scanner ever will. That human work is what we are built around. When we run a manual audit, the findings go straight into Lumi as actionable tickets alongside any automated scan results, so your team works from one place.
Get in touch
If you want to know where your site stands, run a scan with Lumi for a baseline. If you need a thorough assessment, have a look at our accessibility audits. And if you want help building accessibility into your team's process, see our consultancy services.
