Live data from Hacker News

Twitter’s Entire A11y Experience Team Let Go

twitter.com

121–130 of 159 posts

Re: Twitter’s Entire A11y Experience Team Let Go

#121
post #47

Earlier quoted context omitted.

Uh... Why?

Because Twitter as-is is a finished product. There's no immediate need to review accessibility issues since there are no new product features/updates for the foreseeable future. Musk froze everything. So what were those people supposed to do? Nothing? Might as well let them move on to new jobs.

A new feature launched today, and it's not finished so will definitely be updated. Musk said long form text attachments are coming like next week...

he didn't freeze shit.

Re: Twitter’s Entire A11y Experience Team Let Go

#122

Would be great if everybody could be a little less hysterical. Maybe the team was just sh*t and expensive. They get rid of them, so they can hire better people at a better price. Which make a lot of sense now that many tech companies have big layoffs.

That's not how civilized societies work. You don't just get to fire whoever you want whenever you want.

You spelled communism wrong.

Re: Twitter’s Entire A11y Experience Team Let Go

#123

Would be great if everybody could be a little less hysterical. Maybe the team was just sh*t and expensive. They get rid of them, so they can hire better people at a better price. Which make a lot of sense now that many tech companies have big layoffs.

That's not how civilized societies work. You don't just get to fire whoever you want whenever you want.

This is b8

Re: Twitter’s Entire A11y Experience Team Let Go

#124

Earlier quoted context omitted.

That's not how civilized societies work. You don't just get to fire whoever you want whenever you want.

You spelled communism wrong.

Pass single payer healthcare so that being fired isn't a potentially life or death scenario and there may be some merit to your comment.

If people are safe whether employed or not then by all means fire at will. It's rude but not morally bankrupt in that case.

Re: Twitter’s Entire A11y Experience Team Let Go

#125
post #76

Earlier quoted context omitted.

> Huh Before you let that cynicism build up too much, for the record, not all of us Elon+Twitter skeptics have a problem with the $8 thing. You're just not going to hear from any one who didn't have an issue with it. Related: Is there a quippy term or a fallacy for the (very natural!) habit of treating a random sample of a million voices and expecting a coherent message from them? I feel like it's related but distinc…

"Weak man" is when you take a genuine-but-weak take from one of your opponents and treat them as representing your opposition in general. (That's not quite what you're asking for though, I think)

That's definitely close, thanks!

Re: Twitter’s Entire A11y Experience Team Let Go

#126
post #70

Earlier quoted context omitted.

Haven't heard l10n. If anyone else is wondering, that's localization. Tbh a11y is the main one that makes sense. I don't get what the point of i18n and l10n acronyms is besides saving us some typing and generally fitting into the vague category of "giving a crap about users often not considered in design"

It’s been terminology used since the 80s. Just because you haven’t heard of it doesn’t mean it hasn’t been around for a long time. It was coined by DEC. It’s also the reason why Arabic text can be output on the screen, Ruby characters can be used and screen mirroring is usable for UIs that need RTL layouts. You really should look it up before criticising it. It deals with things as small and as important as date form…

> Just because you haven’t heard of it doesn’t mean it hasn’t been around for a long time

idk if you're responding to the wrong user, but I never made the claim that it hasn't been...

Re: Twitter’s Entire A11y Experience Team Let Go

#127
post #57

Earlier quoted context omitted.

Uhhh I don't consider making an app accessible to be contributing to the problem of a "bloated headcount". Maybe the team itself had too many people on it, but to axe the entire team is pretty disgusting and shows a complete disregard for an entire class of people's needs

Accessibility is not a critical business function the same way running Twitter's datacenters is a critical business function. I work at $LARGE_CORPORATION and our product a11y team's most recent major ship was a new palette of colors with improved contrast ratios. A UI change that makes the site easier to read for < 1% of users does not contribute meaningfully to incremental revenue. If I were Musk I would have cut t…

Ask your business counsel if accessibility is important.

Re: Twitter’s Entire A11y Experience Team Let Go

#128

Earlier quoted context omitted.

You spelled communism wrong.

Pass single payer healthcare so that being fired isn't a potentially life or death scenario and there may be some merit to your comment. If people are safe whether employed or not then by all means fire at will. It's rude but not morally bankrupt in that case.

Life happens. And no being fired is not life and death scenario. If you want healthcare you need to find other work. If you can’t find other work then move to other places. If you can’t move to other places then you need to question what made you got into this hole of dependence to your employer from the first place.

If you are skillfull and bring value to your employer why would the fire you and why would other employer won’t want you?

Layoffs are great. They weed out the unproductive ones.

Re: Twitter’s Entire A11y Experience Team Let Go

#129
post #4

> 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".

> Apparently "A11y" stands for accesibility

This has been a common term since a few decades ago. No need to be snarky if you don't understand something.

Re: Twitter’s Entire A11y Experience Team Let Go

#130

Earlier quoted context omitted.

Because Twitter as-is is a finished product. There's no immediate need to review accessibility issues since there are no new product features/updates for the foreseeable future. Musk froze everything. So what were those people supposed to do? Nothing? Might as well let them move on to new jobs.

> There's no immediate need to review accessibility issues since there are no new product features/updates for the foreseeable future Really? You were on the team then? I assume you found out that they had an entirely empty Jira backlog and no more accessibility updates to do on main, so they were let go? I appreciate your insight, former Twitter employee. What else can you tell us about how your job went?

You don't need to be a Twitter employee to know this. Merely posting on this forum gives you enlightenment and insight that others would only dream to have. I stand proudly with VWWHFSfQ.
Post reply on HN