Field notes, primers, and case-tested patterns from Rangle on agentic systems, design systems, frontend, and AI strategy.
Showing 1–6 of 6 posts
Service design can help HIEs increase patient adoption and unlock value-driven revenue streams. In this article, we discuss three service design principles for HIEs to consider for their strategy and operating model to ensure user-centricity and accessibility.
Align Product Strategy
Over the past couple of years working at Rangle, I’ve had the opportunity to work on a handful of design systems (DS). One consistent ask for the design systems I’ve worked on is to “make the design system accessible”, or get it to a point where they can certify that everything within the design system meets their minimum legal requirement for accessibility (like WCAG 2.x AA). On the surface, this sounds achievable, but this doesn’t mean what they think it means.
Scale Design
On the web, forms are the linchpins of ecommerce, social interactions, and most productivity-based applications. Forms are often overlooked. They're that boring part of a website where you fill in your details to get the information you want. Because they've been around for so long, some designers presume forms are a problem that's already been solved — not true! And when you consider accessibility, many forms don't pass the test. In fact, a recent WebAim survey listed complex forms as being one of the most problematic areas for screen reader users.
As a developer, I've noticed ever since starting out that a lot of us are intimidated by building accessible apps. The fact of the matter is, it doesn't have to (and shouldn't) be that way. Accessibility is just like building 🏗 any other feature — and there needs to be greater awareness around this. 🤯
Frontend Development
Animations help bring an application to life. When done properly, they can be an essential part of the user experience and accessibility.
Frontend Development
Today is Global Accessibility Awareness Day (GAAD), a day to raise awareness about accessibility and encourage development teams to make accessibility part of their practice. At Rangle, this is something that we are striving to do. We have helped several of our clients build accessibly, but it still represents a competing priority for many software projects. What developers, scrum masters and product owners should know is that like any other new practice, the initial cost incurred while ramping up ultimately saves time and leads to a more robust outcome.
Build Engineering Capability