Wednesday February 21, 2024

Incident

Screen readers are not announcing unread messages when using the Ctrl + K command on Windows.

Issue summary:
On February 21, 2024 from 6:30 PM PST to 8:00 PM PST, customers using the JAWS or NVDA screen readers on Windows may have experienced issues with announcements for unread messages in the Quick Switcher (Ctrl + K).

A recent code change inadvertently introduced a conflict with an HTML label for an interactive element.

We reverted the code change, fixing the issue and restoring normal announcement behaviour.

5:46 PM PST

We've rolled out a fix and screen readers are now working as expected. If you're still encountering any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Thank you for your patience while we sorted out this issue.

9:40 AM PST

Some customers who use screen readers on Windows are reporting they can no longer hear their unread messages when they use the Ctrl + K command. Our team are investigating the root cause of this issue. We’ll be back with another update as soon as we have more information to share.

7:19 PM PST

Features affected

Messaging

Notifications

Search

Status

Incident

Incident

Trouble with password resets

Issue Summary:

Between 1:18 AM PST on February 21, 2024, and 5:35 AM PST on February 22, 2024, some users experienced issues resetting their passwords, especially when trying to set up two-factor authentication.

We traced the issue to a recent backend code change and reverted the change, which fixed the issue for all affected users.

Thank you for your patience while we resolved this and we apologize for any disruption to your work day.

6:32 AM PST

Users should no longer be experiencing any trouble with password resets. Thank you very much for your patience while we worked on getting this fixed.

5:55 AM PST

Some users may be experiencing issues resetting their passwords, particularly when trying to set up two-factor authentication. We're investigating and we're very sorry for the disruption.

11:46 PM PST

Features affected

Login/SSO

Status

Incident