It's been like a week, the @SlackHq quick switcher is still broken, and it Still Sucks
-
-
W odpowiedzi do @anaisbetts
Hi, Ani!
This was an intended change on our side. The reason for this is to improve accessibility for those who use Slack with a Screen Reader. Prior to this, the first item would be skipped over where it's now included.1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @SlackHQ
Throwing all of your sighted customers under the bus in the name of a11y is unnecessary! You can make both work, I promise
1 odpowiedź 0 podanych dalej 2 polubione -
W odpowiedzi do @anaisbetts @SlackHQ
Yeah guys... just make enter on a blank input, you know, simply select the first item. This change is BRUTAL and unnecessary and poorly executed.
2 odpowiedzi 1 podany dalej 3 polubione -
W odpowiedzi do @chriscardinal
Thanks for sharing your thoughts. We don't have any immediate plans to change the behaviour but are actively gathering feedback which we will take and look at on a closer level.
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @SlackHQ
You guys introduced a bug by breaking engrained functionality. I've seen dozens of replies you've had to make to people explaining it's for a11y as if there isn't a way to have your cake & eat it too. But this was a REALLY poorly executed product change and I hope you'll fix it
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @chriscardinal
Sorry Chris. You're right, we didn't think it would disrupt as many folks' workflows as it has.
For context, in addition to a11y, this aligns us more with Google and other major search engines. But we're tracking feedback closely and will think on it for future improvements!1 odpowiedź 0 podanych dalej 1 polubiony -
W odpowiedzi do @SlackHQ
Did you guys push a fix for this yesterday? Thank you so much for listening to that feedback!
1 odpowiedź 0 podanych dalej 0 polubionych
Hi Chris, we did indeed release a fix! Thank you for giving us that feedback :D
Wydaje się, że ładowanie zajmuje dużo czasu.
Twitter jest przeciążony lub wystąpił chwilowy problem. Spróbuj ponownie lub sprawdź status Twittera, aby uzyskać więcej informacji.