Automated accessibility testing at Slack
slack.engineering
Automated accessibility testing at Slack
1–10 of 59 posts
Re: Automated accessibility testing at Slack
#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.
Re: Automated accessibility testing at Slack
#3>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 directly through accompanying visuals is hard to beat.
Re: Automated accessibility testing at Slack
#4>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 use native Cmd+Shift+5 to record video and then convert it to .mp4 with ffmpeg -i bug-report.mov bug-report.mp4
Re: Automated accessibility testing at Slack
#5I’ve set up automated accessibility tests like this at multiple companies I’ve worked at as well.
We didn’t have a dedicated accessibility team though, so I paired it with a shit list which the team worked through in less than a year.
Re: Automated accessibility testing at Slack
#6>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…
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.
Re: Automated accessibility testing at Slack
#7Earlier quoted context omitted.
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…
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.
Re: Automated accessibility testing at Slack
#8Slack have a rather good a11y experience. The few bugs that I've reported had been addressed rather promptly. The ux is also good with obvious consideration given to keyboard navigation. There are a few annoyances which separate it from perfect, but I rather like the app, especially compared to teams.
Re: Automated accessibility testing at Slack
#9Cypress has an excellent turn-key accessibility tool if you already use their product, and don't mind paying a lot for the accessibility feature. It uses your existing tests and makes evaluations based on that, with zero additional work.
Re: Automated accessibility testing at Slack
#10Slack have a rather good a11y experience. The few bugs that I've reported had been addressed rather promptly. The ux is also good with obvious consideration given to keyboard navigation. There are a few annoyances which separate it from perfect, but I rather like the app, especially compared to teams.
> Slack have a rather good a11y experience
But yet they hijack the standard Cmd-Z “insert link” shortcut for search, so you have to use their non-standard alternative. Not good.