RippleBlog
Welcome to the Ripple Blog!
Join us as we explore the latest trends, share our experiences, and highlight the lessons we've learned from working on the Ripple Design System for the Watermark Impact Suite. We're passionate about solving the unique challenges that come with creating a comprehensive and accessible design system that empowers teams to collaborate, innovate, and drive positive change.
Latest Post
Two focus management pitfalls
Watch for these common and often overlooked edge cases
Focus management is an essential part of accessibility. If a web page cannot be navigated sequentially (advancing focus with a keyboard interface), it fails one of the most basic accessibility requirements, focus order (WCAG 2.4.3, level A).
Recent Posts
-
WCAG Reflow Guideline: Preventing Horizontal Scrolling
A detailed look at some common reflow issues and their solutions. -
The web isn't a visual medium
I was a teenager when the internet arrived in my household. I remember it as a window opening to the world. All of a sudden I had at my disposal more information than I could fathom, instantly. -
A Few Remarks on Using ARIA
ARIA is a recommendation defining a way to make web content and web applications more accessible to users relying on assistive technologies. It provides additional information about web elements to improve usability and understanding. In this article we'll look at what ARIA does (and doesn't do), and how to use it appropriately. -
Semantic HTML
Watermark is committed to making our digital experiences usable for all. Among the steps our web developers can take towards this commitment is writing semantic code. Semantic is defined as “relating to meaning in language,” and for the purposes of this article, that means writing code that renders HTML based on its meaning and not how it looks. -
Redesigning Ripple’s Navigation
As with any significant design challenge, research, testing, and feedback are essential for creating a strong solution. While this process is a core part of a designer’s problem-solving approach, there are often obstacles, such as insufficient time for thorough user research or a lack of resources for testing and gathering feedback.
