To Create More Accessible Outcomes, We Need Better Design Tools.
Nik Jeleniauskas explores some interesting ideas on how Figma could improve to help designers build more accessible products. This would include, for example: have properties for non-visual information built in the tool (semantic roles, accessible names, and behavior properties, etc.).
https://uxdesign.cc/to-create-more-accessible-outcomes-we-need-better-design-tools-a113fe57576c
=> More informations about this toot | More toots from stephaniewalter@front-end.social
Also, adding accessibility simulation, extending the prototyping options to more real world behavior like focus, etc. He also created a prototype of how this could work in Figma.
Full article: https://uxdesign.cc/to-create-more-accessible-outcomes-we-need-better-design-tools-a113fe57576c
=> More informations about this toot | More toots from stephaniewalter@front-end.social
Shameless plug: until Figma decides to add such things, you can do a lot with plugins and documentation, and, I got a whole talk and article on it: How to check and document design accessibility in your mockups, using Figma plugins and annotation kits: https://stephaniewalter.design/blog/how-to-check-and-document-design-accessibility-in-your-figma-mockups/
=> More informations about this toot | More toots from stephaniewalter@front-end.social
Last but not least, @eric wrote an excellent article on how annotation kits can be a useful tool for communicating intent about how an interface should be operated. But, they might also cause more harm when misused, where they fall short and how to overcome the limits: https://ericwbailey.website/published/accessibility-annotation-kits-only-annotate/
=> More informations about this toot | More toots from stephaniewalter@front-end.social This content has been proxied by September (3851b).Proxy Information
text/gemini