Bringing Accessibility to Life Across Two SaaS Products: Kognity & Oneflow

Bringing Accessibility to Life Across Two SaaS Products: Kognity & Oneflow

Bringing Accessibility to Life Across Two SaaS Products: Kognity & Oneflow

Bringing Accessibility to Life Across Two SaaS Products: Kognity & Oneflow
(1 minute version)


🔹 Role: Design Lead, then Accessibility Lead
🔹 Company: Kognity, a digital textbook publisher (B2B SaaS) + Oneflow, a digital signing solution provider (B2B SaaS)
🔹 Collaboration: Head of Design, Product team, Developers and Support teams
🔹 Impact:

Saved 3-6 months in US market entry (Kognity)
• -15% accessibility-related support tickets (Oneflow)
Oneflow on its way to meeting WCAG 2.1 AA standards, unlocking public sector contracts

Reusable skills gained

Leading accessibility implementation initiatives
Applying WCAG 2.2 standards
Using strategic knowledge of the European Accessibility Act to enhance digital product inclusivity

The Problem

At Kognity, accessibility was overlooked until I proved it was a business priority.
At Oneflow, accessibility was on the radar, but lacked execution & accountability.

Key business drivers:

• US Schools section 504 (Rehabilitation Act) compliance → A key growth market.
• 2025 European Accessibility Act → Expands accessibility requirements to private sector businesses.

The Solution

I led accessibility transformations at both companies:

Kognity: Secured an accessibility audit budget and revamped the visual design guidelines (including typography, colour contrast, and navigation) for WCAG alignment.
Oneflow: Led accessibility implementation through audits and a cross-functional task force, resulting in tangible UX improvements that directly contributed to increased acquisition of public sector clients.
Tested digital contracts signing with blind users, refining screen reader and keyboard navigation and resulting in accessible modal flows.

Key Learnings

Accessibility drives growth when framed as a business enabler.
Testing with blind users revealed critical gaps beyond audits.
Long-term progress needs embedded processes, not one-off fixes.

Why It’s Relevant

This work shows my ability to:

Lead accessibility strategy tied to market expansion
Translate legal standards into practical UX improvements
Collaborate across product, design, compliance, and support
Test with real users and prioritize based on real barriers
Scale inclusive design across teams

Figure 1. Before and after improvements of Kognity's Study skills educational content box.

Bringing Accessibility to Life Across Two SaaS Products: Kognity & Oneflow (Full version)

The Challenge

At Kognity, accessibility was an afterthought until I proved its business impact.
At Oneflow, accessibility was recognized as important but had no structured approach.

Why it mattered

• US Schools → Strict Section 504 (Rehabilitation Act) standards for education tech.
• 2025 European Accessibility Act → Expands accessibility requirements to private sector businesses.

I secured leadership buy-in by linking accessibility to market expansion and compliance risks.

Figure 2. As part of my accessibility role at Oneflow, I ran user interviews with blind users to understand how they navigate digital contracts using a screen reader and a keyboard.

My Approach

Kognity

✔ Led an accessibility audit, ran internal training.
✔ Developed a set of Accessibility guidelines for the Product department + coached teams to implement.
✔ Improved contrast, typography, keyboard navigation.
✔ Accelerated US market entry by 3-6 months.

Oneflow

✔ Ran two accessibility audits, built an internal Accessibility task force.
✔ Fixed critical usability issues: contrast, keyboard navigation, screen reader support.
✔ Developed a set of Accessibility guidelines for the Product department + coached teams to implement.
Tested digital contract signing with blind users, resulting in accessible modal flows and fewer user-reported barriers.
This contributed to increased acquisition of public sector clients.

Figure 3. Before/after the attachment options were improved for WCAG 2.1 compliance.

Accessibility in Action: Fixing Keyboard Navigation in Modals

An accessibility audit and user testing with a blind user revealed that modals in Oneflow were not keyboard navigable, blocking screen reader users. However, fixing this required ongoing developer resources, making it difficult to prioritize.

To address this, I advocated for a structured approach, securing a 5% monthly development resource allocation dedicated to accessibility fixes. This ensured continuous improvements without disrupting other product priorities.

• Modals became fully keyboard navigable, improving usability for all keyboard and screen reader users.
• A group of Norwegian schools with strict accessibility requirements signed up, reinforcing the business value of accessibility.
• Established a sustainable process for accessibility improvements, ensuring long-term compliance and usability enhancements.

This initiative demonstrated that proactively addressing accessibility benefits both users and business growth, strengthening Oneflow’s position as an inclusive digital signing solution.

Figure 4. Improved keyboard navigation in Oneflow Modals.

Figure 4. Improved keyboard navigation in Oneflow Modals.

Figure 4. Improved keyboard navigation in Oneflow Modals.

Outcome & Business Impact

Expanded market eligibility by saving 3-6 months in US market entry (Kognity), making accessibility a competitive advantage.
• -15% Accessibility-related tickets (Oneflow).
Oneflow is on its way to meeting WCAG 2.1 AA standards, unlocking public sector clients.

Learnings

Framing accessibility as a business driver secured leadership buy-in.
Testing with blind users revealed critical gaps beyond audits.
Small UI fixes had wide usability and support impact.
A recurring dev resource (5%) ensured long-term progress.
Empowering a task force made accessibility a shared responsibility.

🔹 Reusable Skills Demonstrated:

Leading accessibility audits and implementation
Applying WCAG 2.1/2.2 to design systems
Creating accessibility guidelines and coaching teams
Conducting research with assistive tech users
Building sustainable accessibility processes and task forces

Figure 5. Iterations on Oneflow's Sign button colours to follow the WCAGs colour contrast requirements.

Figure 5. Iterations on Oneflow's Sign button colours to follow the WCAGs colour contrast requirements.

Figure 5. Iterations on Oneflow's Sign button colours to follow the WCAGs colour contrast requirements.

Find more
case studies below