Comment by Shad Mirza on "Ask Anything UI/UX and Design Systems to this group of Amazing Devs"

Hello everyone
Thanks for doing the AMA

My question is

Should accessibility come under a feature of the design system or it should be taken care by the developer itself?
If I am making a component that has variations of it. While all the variations do the same job but are completely different from each other on the basis of UI, UX, and implementation logic having 90% of the props similar (does the same job).
Does it make sense to make them as separate components or go with type="something" approach? (Note: I am following Base variant approach for building it so they are already in different files)

Would love to know your thoughts on this.

I think a previous answer I gave re. accessibility can help with the first question and that was about how accessibility sometimes falls outside of the realms of the 'UI' so perhaps it's about optimising download sizes for folks on data contracts that they have to monitor closely because of cost. So sometimes it's about understanding users deeper as you build design systems and as you develop.

I think the best tools and teams are those that take an interest in what your colleagues do. I always make an effort to understand the tech stack as much as I can and include devs in user research.

Accessibility and inclusion is everyone's responsibility and concern :)

Should accessibility come under a feature of the design system or it should be taken care by the developer itself?

Like Eriol said, it's everyone's responsibility :)

You can't get one without the other. You need base components from the design system to provide an accessible foundation (I'm thinking of an Icon Button that has a aria-labelledby and a tooltip). At the same time, you'll need the application's context to put a useful message in the tooltip.

Part 2 of your question is very subjective :) There is no 1 true correct answer.

My personal approach is to keep things that do the same job in the same component even if they look different (that what variants are). Things that look the same but serve different purposes go in different components.

This was help Eriol Fox Sid Thank you. I think I got my answer.

Search Hashnode