No post body was provided.
Twitter’s Entire A11y Experience Team Let Go
11–20 of 159 posts
Re: Twitter’s Entire A11y Experience Team Let Go
#12Re: Twitter’s Entire A11y Experience Team Let Go
#13> Twitter’s Entire A11y Experience Team Let Go A8y "A11y" s4s f1r accesibility. (Apparently "A11y" stands for accesibility). "Twitter is better in the app" is not a sign of "accesibility". Sign in is not a sign of "accesibility".
[deleted]
Re: Twitter’s Entire A11y Experience Team Let Go
#14The extreme and somehow flowery language in all these posts from Twitter engineers is so indicative to me of some kind of delusional rot. “My team worked SO hard every single day to Change The World, the smartest people on the planet Earth, the greatest engineers ever to touch a keyboard, no one has our scale, no one has our problems.” So caught up in their own bullshit that they are like fat, happy hens who don’t see the fox in their midst named Elon. It reminds me of Billy Bob Thornton in Fargo Season One. “The maps used to say ‘there be dragons here’. They don’t anymore, but the dragons are still there.” These people live in a bubble where they reinforce each other.
Re: Twitter’s Entire A11y Experience Team Let Go
#15I mean if I need to lower costs ASAP, nice to haves like A11y would be the first to get cut.
saying a11y is a nice-to-have is like saying Unicode is a nice-to-have. if you cut Unicode support, the only thing you'll personally notice is lack of emojis, but Chinese/Hindi/Russian speakers won't be able to use it at all, without resorting to Pinyin or something.
Re: Twitter’s Entire A11y Experience Team Let Go
#16Accessibility shouldn't be a separate team. It should be a consideration for all product development. And as far as experiences go, Twitter has a pretty small surface area.
Re: Twitter’s Entire A11y Experience Team Let Go
#17Re: Twitter’s Entire A11y Experience Team Let Go
#18I mean if I need to lower costs ASAP, nice to haves like A11y would be the first to get cut.
saying a11y is a nice-to-have is like saying Unicode is a nice-to-have. if you cut Unicode support, the only thing you'll personally notice is lack of emojis, but Chinese/Hindi/Russian speakers won't be able to use it at all, without resorting to Pinyin or something.
And if you don’t have customers who use those, it won’t be a huge loss. That covers the vast majority of businesses.
Probably not Twitter though.
Re: Twitter’s Entire A11y Experience Team Let Go
#19Accessibility shouldn't be a separate team. It should be a consideration for all product development. And as far as experiences go, Twitter has a pretty small surface area.
> Accessibility shouldn't be a separate team. It should be a consideration for all product development.
Teams generally don't have expertise in all areas, which is why cross-functional teams with deep experience in a specific area can be a great way to organize resources. This is why design teams, performance teams, security teams, etc. exist.
Re: Twitter’s Entire A11y Experience Team Let Go
#20Earlier quoted context omitted.
Is A11y a nice to have? Doesn't the ADA mandate a certain level of accessibility on companies of a certain size.
Not the ADA specifically, but American courts have generally held that large commercial websites do need to be accessible in terms of the ADA. That's aside from the cruelty of diminishing accessibility on a major social platform, slowly cutting off disabled users, despite its cost likely being a rounding error in the greater scheme of things.
I’m very impressed by the use of ‘cruelty’.