Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Automated accessibility testing at Slack

slack.engineering

Post reply on HN
Print view View original

31–40 of 59 posts

Re: Automated accessibility testing at Slack

#31

Post by quectophoton »

nicbou wrote: post #21
quectophoton wrote: post #19

They still have that 3-4 second delay during login though. I open Slack directly from a browser, I login from a browser, yet I have to wait until they decide to ask me if I really want to continue with the browser I've been using for literally all the steps so far. It's not much but it feels like when I'm on YouTube with a device that doesn't have adblock and a short ad plays before the video. It's not related to acc…

> Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. https://news.ycombinator.com/newsguidelines.html

My bad, I thought that rule was about the medium (i.e. the post itself). I didn't it also applied beyond that (e.g. commenting about Slack's UX on a post whose topic is a subset of Slack's UX).

I'll keep it in mind, thanks.

Re: Automated accessibility testing at Slack

#32

Post by LtWorf »

j16sdiz wrote: post #24
LtWorf wrote: post #16

I'm the author of localslackirc, to bridge slack and IRC. Probably most IRC clients are more accessible.

If you consider the real-time text-only chat, maybe. As soon as you start thinking about the side features. they are not comparable.

for example?

Re: Automated accessibility testing at Slack

#33

Post by ch4s3 »

eitally wrote: post #18
password4321 wrote: post #13

Earlier quoted context omitted.

> I rather like the app, especially compared to teams Pretty sure just about every other option is pretty likeable compared to Teams!

Yet there are Teams features that nobody else has emulated yet and which quickly become almost indispensable for business use. I'll name two: 1. Teams automatically creates a chat group for every Teams calendar event. This can include external attendees. 2. Teams is useful for chat & meetings, but Teams spaces are hugely helpful as document repositories, too, and it's additionally easy to add things like Gantt charts…

I'm strongly of the opinion that 1. is an anti-feature. It creates a ton of clutter.

Re: Automated accessibility testing at Slack

#34

Post by agos »

MontagFTB wrote: post #7
PyWoody wrote: post #6

Earlier quoted context omitted.

If you don't need to edit the screenshot, Command+Control+Shift+4 will bring up crosshairs that will put the screenshot selection in your clipboard and won't save it to disk. It's super handy for doing a ton of quick, one-offs.

If it helps, hitting the spacebar will toggle screenshotting a window.

and it includes the shadow, with trasparency! looks great

Re: Automated accessibility testing at Slack

#35

Post by datadrivenangel »

eitally wrote: post #18
password4321 wrote: post #13

Earlier quoted context omitted.

> I rather like the app, especially compared to teams Pretty sure just about every other option is pretty likeable compared to Teams!

Yet there are Teams features that nobody else has emulated yet and which quickly become almost indispensable for business use. I'll name two: 1. Teams automatically creates a chat group for every Teams calendar event. This can include external attendees. 2. Teams is useful for chat & meetings, but Teams spaces are hugely helpful as document repositories, too, and it's additionally easy to add things like Gantt charts…

Teams spaces are just embedded sharepoint, which has many awkward edges.

Re: Automated accessibility testing at Slack

#36

Post by ternnoburn »

rhzdgaf wrote: post #12

[flagged]

Your position is really "fuck disabled people", really?

Your ever seen a blind person try to use the internet? You ever seen a person with essential tremors try to use their phone?

Go and educate yourself a little.

These standards are all built from the experiences of users who were unable to access things and they benefit way more than the 15% of people who have disabilities. Ever used closed captioning, automatic doors, or curb cuts? Those things all started as accessibility features.

Re: Automated accessibility testing at Slack

#37

Post by SilasX »

quectophoton wrote: post #31
nicbou wrote: post #21

Earlier quoted context omitted.

> Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. https://news.ycombinator.com/newsguidelines.html

My bad, I thought that rule was about the medium (i.e. the post itself). I didn't it also applied beyond that (e.g. commenting about Slack's UX on a post whose topic is a subset of Slack's UX). I'll keep it in mind, thanks.

IMHO, your original interpretation is correct. The rule is about the UX of the article itself. In a story about Slack UX with respect to accessibility ... general issues with Slack UX seem topical enough.

Re: Automated accessibility testing at Slack

#39

Post by bravetraveler »

ch4s3 wrote: post #33
eitally wrote: post #18

Earlier quoted context omitted.

Yet there are Teams features that nobody else has emulated yet and which quickly become almost indispensable for business use. I'll name two: 1. Teams automatically creates a chat group for every Teams calendar event. This can include external attendees. 2. Teams is useful for chat & meetings, but Teams spaces are hugely helpful as document repositories, too, and it's additionally easy to add things like Gantt charts…

I'm strongly of the opinion that 1. is an anti-feature. It creates a ton of clutter.

Indeed. Instead of a dedicated set of channels for a topic... we have this breaking things up. This 'feature' absolutely kills focus.

The old ways - curating channels - are the best ways.

Re: Automated accessibility testing at Slack

#40

Post by egypturnash »

quectophoton wrote: post #19

They still have that 3-4 second delay during login though. I open Slack directly from a browser, I login from a browser, yet I have to wait until they decide to ask me if I really want to continue with the browser I've been using for literally all the steps so far. It's not much but it feels like when I'm on YouTube with a device that doesn't have adblock and a short ad plays before the video. It's not related to acc…

Here is a way to get around this annoying behavior: Type “sla” in your address bar (or however many characters of “slack” it takes to get it to autocomplete with Slack URLs). Cursor down into saved URLs for actual Slack channels. Hit return. Skip all that bullshit.

Discord does the same bullshit and this works there too.

(This assumes you’re not logging out when closing the slack/discord tab. Sometimes it just doesn’t work with Slack and you have to do a full login.)

Post reply on HN