Empowering Access: How Logiqc's Latest UI Updates Reflect a Deep Commitment to Accessibility

We spoke with Bret Mannison, Co-Founder and Product Development Lead at Logiqc, about the company’s commitment to accessibility. He shared how international guidelines shaped their latest UI updates, why accessibility isn’t just a checkbox but an ongoing responsibility, and how these improvements benefit clients. With structured feedback, real-time user insights, and a long-term vision, Logiqc is ensuring accessibility remains at the core of its platform’s evolution.

What specific international accessibility standards were the primary drivers for this UI update, and why were they prioritised?

The W3C Web Content Accessibility Guidelines (WCAG) were the key driver for this UI (user interface) update, as they are the globally recognised standard for web accessibility. Prioritising WCAG compliance goes beyond simply ticking boxes on a checklist. It's about recognising that the digital landscape should be accessible to everyone, regardless of their abilities. Designing software with accessibility in mind benefits everyone by creating more intuitive interfaces and building a digital space that is more welcoming and functional for all users.

How did you gather and incorporate user feedback, particularly from users with accessibility needs, throughout the project?

We have a structured process in place for recording all customer feedback, primarily through our support desk, where users submit tickets and suggestions. Each piece of feedback is carefully documented, including details of who submitted it and when. We actively communicate with customers, letting them know their input is valued and considered, and that we respond to it.

Every month, we release software updates, often incorporating user suggestions. Over the years, we've received specific feedback regarding accessibility, and this latest UI update reflects our commitment to responding to those needs - while also taking things much further. We didn’t just want to acknowledge it; we saw it as an important responsibility. Software companies have a moral obligation to prioritise accessibility because it’s fundamentally about respecting diversity.

Beyond that, from a purely commercial standpoint, why release a product that only 90% of people can use? It makes far more sense to ensure accessibility for everyone and let the product stand on its own merits.

What were the key challenges you encountered during the project, and how were they overcome from a project management perspective?

One of the main challenges was ensuring that accessibility improvements enhanced the user experience for everyone without negatively impacting usability. For instance, while a font might need to meet a specific density requirement for accessibility, applying that rule across an entire software system isn't always straightforward. If not carefully implemented, it could unintentionally affect readability or disrupt the software’s intuitive design.

Another key challenge was balancing compliance with accessibility guidelines and maintaining an intuitive user experience. The WCAG standards are crucial, but they’re not UX guidelines - they focus on ensuring accessibility rather than dictating what makes software intuitive. Since the guidelines cover a broad range of elements, including audio consumption (which may not even be relevant to our platform), we had to carefully assess and apply the most relevant principles to our software.

We couldn’t take a one-size-fits-all approach, so we tackled the project in a structured way. First, we engaged the right experts: one internal staff member, Tim (Tim Grillmeier, Senior Frontend Developer at Logiqc) and an external contractor, Ariel (Ariel Beninca, experienced designer).

We also conducted a formal accessibility audit of the software against WCAG standards. This helped us identify various issues, which we then prioritised based on feasibility and impact. From there, we developed a structured roadmap to implement the necessary changes in a way that balanced accessibility with usability.

How do accessibility improvements benefit clients and their organisations?

Enhancing accessibility ensures that more employees within client organisations can effectively use the platform. This approach aligns with the broader principle of inclusivity, ensuring the software is as widely usable as possible.

Many of our clients operate in the disability services sector, including large NDIS organisations, where a significant number of employees may have accessibility needs. By prioritising accessibility, we help these organisations make the platform available to their entire team. And, as I mentioned before, designing software with accessibility in mind benefits everyone by creating digital spaces that are more welcoming.

How will the success of this accessibility update be measured and tracked moving forward? What metrics are being used?

Before releasing the update, we are conducting six client interviews to establish a benchmark and gather initial feedback comparing the old and new versions. This helps us gauge user sentiment and identify key areas of improvement.

We have also recently implemented a platform called UserPilot. This acts as a support layer within our software, providing contextual guidance through pop-up help videos and interactive prompts. More importantly, it gives us insights into areas of the software that users find difficult to use. This behavioural analytics data will help us assess the impact of our accessibility updates. Additionally, we have built-in mechanisms for gathering user feedback. When we release updates, we have a feedback button where users can share their thoughts directly, allowing us to refine the experience continuously.

From a compliance standpoint, accessibility standards have three levels: Level 1 (basic compliance), Level 2 (more advanced), and Level 3 (the highest). Many platforms fall short of full compliance. We strive to meet Level 2 and Level 3 where possible, which is a significant goal. We conducted an initial audit to determine where we currently stand in relation to Level 2. This provided us with a formal baseline, and we plan to conduct follow-up audits in the future to measure our progress and ensure we maintain or improve our compliance over time.

What future plans do you have for continued improvement of accessibility on the platform, and how will these be prioritised?

We believe accessibility should be embedded into our software as an ongoing commitment and a human obligation rather than a one-off project. While we may not always meet every best practice, we have made a significant effort to enhance accessibility, and we stand by that commitment. When we release the update in a few weeks, we will publicly share our approach and continue to uphold these principles.

Rather than treating accessibility as a box-ticking exercise, we intend to integrate it into our development process. Software is constantly evolving, and every new feature, form field, or design change requires accessibility considerations. Whether it’s determining font density, colour contrast, or interactive elements, these decisions must align with accessibility guidelines at every stage of development. We rely on a style guide to maintain consistency, but there will always be new challenges requiring careful assessment.