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

21–30 of 59 posts

Re: Automated accessibility testing at Slack

#21

Post by nicbou »

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

Re: Automated accessibility testing at Slack

#22

Post by TypingOutBugs »

rhzdgaf wrote: post #12

[flagged]

The EU has an Accessibility Act coming into play from June this year, so a subset of companies working on things like travel booking systems will have to test to make sure they meet those new requirements.

https://www.epinova.se/en/blog/2024/understanding-the-europe...

Re: Automated accessibility testing at Slack

#23

Post by shafyy »

steve_adams_86 wrote: post #3
skeptrune wrote: post #2

>A few developers gave us early feedback and requested screenshots of the pages where accessibility violations occurred. It's amazing how much a screenshot will do for my motivation to fix a frontend bug. Visually identifying severity is much easier than reading and making a mental judgement.

I like using video as well. The whole "picture is worth 1000 words" adage is true, and it makes all kinds of bugs far easier to recognize. I'm sure other tools are great too but I find Cleanshot on macOS makes it super convenient to do it, so there's no excuse not to document reports with images and/or videos. I do the same with pull requests. Words are almost always essential, but demonstrating bugs/changes/features…

I love Cleanshot!

Re: Automated accessibility testing at Slack

#25

Post by sofixa »

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 automatically creates a chat group for every Teams calendar event. This can include external attendees

Great, so each conversation is spread out and siloed. Thankfully Teams has good search and you can find stuff, right? Right?

> 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 and other enriched content types through add-ins

Slack Canvas kind of does this. I'm not convinced having all your documentation in your chat/meeting app makes sense, but it could be useful.

> The ability to seamlessly transfer a Teams meeting connection between arbitrary devices (laptop -> desktop, phone -> laptop, etc).

Zoom does this too, and has for years. I think I've seen Slack huddles offer the same option too.

Re: Automated accessibility testing at Slack

#26

Post by sofixa »

LtWorf wrote: post #15
rhzdgaf wrote: post #12

[flagged]

Well it's mandatory to get government contracts. That's the only reason companies do it. They have no interest for disabled people.

Not only government contracts, some very big orgs have accessibility requirements in all their vendor contracts too.

Re: Automated accessibility testing at Slack

#27

Post by robin_reala »

TypingOutBugs wrote: post #22
rhzdgaf wrote: post #12

[flagged]

The EU has an Accessibility Act coming into play from June this year, so a subset of companies working on things like travel booking systems will have to test to make sure they meet those new requirements. https://www.epinova.se/en/blog/2024/understanding-the-europe...

things like travel booking systems

Any ecommerce, including selling services, is included. It’s not a small subset. You can see the scope at https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A...

Re: Automated accessibility testing at Slack

#28

Post by eckmLJE »

rhzdgaf wrote: post #12

[flagged]

Web accessibility describes specific requirements for people with disabilities to be able to use your website. If you don't implement these features, blind people, colorblind people, people who can't use a mouse, etc., won't be able to use your website. You can make a strategic choice not to support these users for reasons like ROI. But obviously there are plenty of situations where either we make the affirmative choice not to exclude people with disabilities, or we're required by law to accommodate them. In my personal opinion, we should always build on the web with the modern features that support assistive technologies, and that building inaccessible web experiences is synonymous with building poor quality web experiences. Many of the (mostly native) features that enable an experience accessible to people with disabilities improve the experience for all users.

Re: Automated accessibility testing at Slack

#30

Post by robertlagrant »

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…

> 1. Teams automatically creates a chat group for every Teams calendar event. This can include external attendees.

This happens in Zoom as well, without the extra Teams downside of external attendees being 4th class citizens.

> 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 and other enriched content types through add-ins.

This is really simple in demos, but tends towards sharing documents via email again (for external attendees) or growing the channel size massively (for internals who need the documents but aren't obviously needed in the team).

Post reply on HN