dbjorge

6 ms·

1.
by dbjorge 2y ago
Screenshots of issues is something we support in many of our paid offerings, but not in axe-core itself. It sounds like the Slack folks implemented their own version of it. If you have general questions about axe-core, the best place to ask
2.
by dbjorge 2y ago
I am one of the maintainers of the axe accessibility testing engine the Slack team is using. It's awesome to see such a detailed writeup of how folks are building on our team's work! We publish the engine (axe-core) and the "
3.
by dbjorge 5y ago
I think that even just on private machines, this would make some types of legal compliance needlessly difficult. If you ever need to delete that data, for example to comply with a corporate retention policy or in response to a request from
4.
by dbjorge 5y ago
I used the Matias Ergo Pro for exactly 14 months. After the first month I bought a second for home. At 13 months (ie, one month out of warranty), the first one started having reliability issues with the quiet click switches failing. At 14 m
5.
by dbjorge 5y ago
This is a neat tool, but unfortunately, text art like this generates is extremely unfriendly to folks that use screen readers. If you do use this for comment documentation, consider making sure that there is also a written description above
6.
by dbjorge 5y ago
This is a neat concept! One not-so-obvious accessibility issue with keyboard shortcuts on websites is that if they're too simple (especially single-character), it's easy for them to conflict with assistive technologies like screen
7.
by dbjorge 5y ago
Living in constant fear that a Google algorithm may someday decide to ban our extension without providing a reason, advance notice, or a meaningful appeals process. It feels like there's some new horror story describing this situation
8.
by dbjorge 5y ago
My team is still using yarn v1 because we want both dependabot support (rules out yarn v2+ and pnpm) and support for overriding transitive dependency versions to force security fixes (eg, yarn resolutions). We would love to explore other op
9.
by dbjorge 5y ago
Yes, navigation links that don't behave like normal links are also an accessibility problem[1]. That's a separate issue, though; I don't think it is a reasonable argument against supporting reflow based on perceived window
10.
by dbjorge 5y ago
I don't think the article is using unclear wording; I think it is clearly arguing the exact opposite of what you're describing. I think the clearest demonstration of this is the concluding section, where the author specifically ta
11.
by dbjorge 5y ago
This article starts with a pretty big assumption: > Now, I think we can all agree that, on our desktop computers, we prefer viewing the full-width layout of most web pages. This assumption is not reflective of current accessibility resea
12.
by dbjorge 6y ago
The article explains the technical details of the render process escape. Contrary to all the current replies to this comment, it does not look to me that this is using a generalized Electron escape; rather, it is using specific main/re
13.
by dbjorge 6y ago
I work for Microsoft on a moderately complex chromium extension. We've investigated porting it to Firefox (we've had a small but nonzero minority of users ask about it, and several of our engineers have a personal interest in it),
14.
by dbjorge 6y ago
The article notes near the top that extensions are supported, and also answers your other questions.
15.
by dbjorge 7y ago
On Android I use an app called Materialistic, which has a dark mode
16.
by dbjorge 7y ago
Highcharts has put a lot of effort into designing charts to be accessible. They did a presentation about it at my workplace a few months ago and I was impressed by the passion and level of user testing they had done. https://www.
17.
by dbjorge 7y ago
My team at Microsoft maintains an open source browser extension for this called Accessibility Insights ( https://accessibilityinsights.io ), which is what Microsoft recommends internally for its own teams developing websites. It o
18.
by dbjorge 7y ago
The most popular FOSS screen reader by a very, very large margin is NVDA ( https://www.nvaccess.org ). It is Windows specific, though.
19.
by dbjorge 7y ago
Rolling your own CAPTCHA is very , very likely to introduce accessibility issues for your site. It is the accessibility equivalent of "rolling your own cryptography" for security. Among surveys of screen reader users, CAPTCHAs
20.
by dbjorge 7y ago
There are lots of options for automated accessibility scans, but there are many common accessibility issues that aren't feasible to test for with automation. My team at Microsoft recently open sourced a tool called Accessibility Insigh
21.
by dbjorge 7y ago
Microsoft recently open sourced[1] one of the main tools they use for web accessibility testing. Accessibility Insights for Web ( https://accessibilityinsights.io ) is a Chrome extension that guides you through doing an accessibil