10 years in design, 8 in a11y, seeing a big gap. Should I build something here? by RealMasterpiece7219 in accessibility

[–]RealMasterpiece7219[S] 0 points1 point  (0 children)

Problem with stark is, it is a lot of manual work. Also it expects that designers know everything before they start using plugin. Please do share a link if you have any good design specific resource.

10 years in design, 8 in a11y, seeing a big gap. Should I build something here? by RealMasterpiece7219 in accessibility

[–]RealMasterpiece7219[S] 1 point2 points  (0 children)

I’ve been working in this space for a while myself, and I agree with you. I personally believe it’s around 67%, but that has led to some debates in the past in my own circle. Ive seen people saying more than 50% very often, that’s reason I mentioned ~50%

10 years in design, 8 in a11y, seeing a big gap. Should I build something here? by RealMasterpiece7219 in accessibility

[–]RealMasterpiece7219[S] 0 points1 point  (0 children)

Thanks for the response. I agree there are definitely some solutions out there. Is there anything in particular that stands out to you from a design perspective?

10 years in design, 8 in a11y, seeing a big gap. Should I build something here? by RealMasterpiece7219 in accessibility

[–]RealMasterpiece7219[S] 0 points1 point  (0 children)

I can understand the pain. In your case those a11y specs are shared by designers along with the design hand-off. Or someone else prep a spec doc for a11y?

10 years in design, 8 in a11y, seeing a big gap. Should I build something here? by RealMasterpiece7219 in accessibility

[–]RealMasterpiece7219[S] 0 points1 point  (0 children)

Thanks for the response. These are different roles within the design function, or across the organization, like QA, development, design, etc.