# inclusive design A design approach that aims to ensure everyone who needs a service can use it as easily as possible, considering potential exclusion from the start. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## On the Edge of Burnout... Again DevFeed: [On the Edge of Burnout... Again]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:32.669000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [inclusive design](), [Job]() Tags: [accessibility](), [burnout](), [inclusive-design](), [work]() ### AI overview A personal account of recovering from burnout while working as the first accessibility specialist at Oura. The author describes how role miscommunication, unclear expectations, and a brain injury contributed to burnout, and how conversations, time off, and a clearer understanding of the role helped restore their energy and motivation. ### Source excerpt I've been super tired during the spring. Again. I could write a blog post about how disappointed I am that I've let myself into this situation - again. But this blog post is not about it. It's about how I got further away from that edge and started finding myself - and the spark - again. So, to give some context: About eight months ago, I wrote a blog post about my first month as an accessibility specialist at Oura. At that point, I was still in the honeymoon phase, and the realities of being the first-ever accessibility specialist in the company weren't apparent. You see, being the first in any role, especially in a role whose goal is purely to change existing things, is not easy. If there are any miscommunications about the position, it makes it even harder. And if you don't know what's expected of you, well, that's certainly a risk for burnout. I should have known better - hey, I've been here before, and I know I'm more at risk because of my brain injury than someone else without the same history. I realized I'd lost my spark. Not just for the work but also for anything outside the job. I used to love sharing what I've learned, but writing and submitting proposals for conferences didn't feel good. I thought, "What's the point? Nothing's going to change anyway". Now that I'm in a better position, I'm a bit sad because I missed some conference applying deadlines I had been waiting for for a long time. For example, I didn't submit a proposal to Inclusive Design 24 - I just didn't have the energy. I'm better now I'm better now. But it took some time, conversations, and challenging moments before I could be honest about the situation. And again, I could use the word "again." I've been here before. I tried to raise the problems throughout the spring. I think it was a short sickness leave that made the people at the company understand that this is pretty serious. After that, we had multiple conversations about my role. I understood some miscommunications about my positi ## Building a more collaborative design process DevFeed: [Building a more collaborative design process]() Original publisher: [Read original article]() Author: Wayne Ng Published: 2021-08-18T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [inclusive design]() Tags: [building](), [design](), [partners](), [process](), [product-design](), [work](), [workflows]() ### AI overview Figma's product design team uses FigJam to support earlier-stage ideation and closer collaboration among designers, product managers, engineers, and other cross-functional partners. The article describes how this workflow encourages brainstorming over pixel-perfect refinement and helped the team develop FigJam features such as cursor chat, emoji reactions, and stamps. ### Source excerpt We asked our product design team how they use FigJam to work closer together as a team, and with their cross-functional partners. ## Behind the plugin: Cards for Humanity DevFeed: [Behind the plugin: Cards for Humanity]() Original publisher: [Read original article]() Author: Beez Africa Published: 2021-07-14T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma plugin](), [inclusive design](), [Accessibility](), [User interface design]() Tags: [accessibility](), [community](), [design](), [developer](), [features](), [figma-plugin](), [inclusive-design](), [plugin](), [workshops]() ### AI overview This article profiles Cards for Humanity, an online card game created by Idean to help teams design accessible and inclusive products. It explains how the team adapted the game into a Figma plugin and website, using character cards paired with needs, disabilities, or personal challenges to encourage empathy and reduce assumptions in design discussions. ### Source excerpt We interviewed the creative team behind Cards for Humanity, a tool for inclusive and accessible design. ## Enabling keyboard culture with No Mouse Days DevFeed: [Enabling keyboard culture with No Mouse Days]() Original publisher: [Read original article]() Author: Marcy Sutton Published: 2020-10-15T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [Accessibility](), [inclusive design](), [front-end-development](), [npm](), [CSS]() Tags: [accessibility](), [css](), [front-end-development](), [inclusive-design](), [npm](), [processes](), [tooling](), [web]() ### AI overview The article advocates regular mouse-free testing to reveal keyboard and screen reader accessibility problems in websites and applications. It introduces No Mouse Days, an npm package that hides the mouse cursor with CSS, and encourages teams to use the practice to identify inaccessible controls and missing focus outlines early. ### Source excerpt Wouldn't it be great if designers and developers tested their digital experiences for keyboard accessibility on the regular? And by extension, screen reader accessibility? That's where the #NoMouse challenge and No Mouse Days come in. The DO-IT Center at University of Washington originally started the No Mouse challenge, complete with its own website, logo, and hashtag to spread awareness about the need for keyboard-accessible websites and applications. The challenge is pretty straight-forward: Step 1. Use the Web without a mouse. Can you access all features? Can you reach and operate all interactive controls? Can you easily tell where you are on the page? Step 2. Learn more about accessible web design. Step 3. Spread the Word! Building on that initiative came No Mouse Days, an npm package that disables the mouse cursor on web pages with CSS. It started as a cheeky joke, and then it actually became popular. The idea of No Mouse Days was to make it easy to hide the mouse cursor so it would become extremely obvious when a user interface didn't support the keyboard, perhaps disabling it automatically for front-end development one day a week. If you have further ideas for No Mouse Days or other culture-changing techniques, contributions are always welcome on GitHub and Twitter! No matter how you go about it, establishing a mouse-free development day at least once a week could work wonders for people who can't use a mouse at all. You might find interactive controls that aren't actually interactive for large segments of the population and lacking visible focus outlines which make keyboard navigation difficult. Surfacing issues with keyboard-support early and often will give teams something to react to, and hopefully dedicated tooling and processes can make it second nature through more inclusive design and development.