14 ms·
I think about this whenever someone posts about yet another new immediate mode UI library, or a custom layout engine they’ve built on top of HTML canvas. Genera
by josephg 5y ago
I think about this whenever someone posts about yet another new immediate mode UI library, or a custom layout engine they’ve built on top of HTML canvas. Generally all these kind of approaches make your app invisible to screen readers.
The amount of work Apple, Google and others have put into making all this work is staggering, and life changing for people who are blind. Please don’t throw all that work away in your apps just because you think some UI toolkit is shiny.
- inamiyar 5y agoThis as of now also applies to most Rust UI libs, hence why I don't use them. At least in that community each UI kit has an 'accessibility' issue though so hopefully improvements to come.
- mumblemumble 5y agoI was recently shopping for cross-platform desktop GUI toolkits, and discovered that there are really very few options that work well with screen readers. The only ones that seemed at all viable were Electron and JavaFX. .NET MAUI also seems very promising, and I like that they're actively blogging about it[1], but it hasn't been officially released yet. Anyway, it seemed to me that basically all the others either aren't accessible at all, or are only accessible on one or two of the target platforms, or have long-standing accessibility bugs that seem like they would render the UI unusable. [1]: https://devblogs.microsoft.com/xamarin/the-journey-to-accessible-apps-screen-readers/ https://devblogs.microsoft.com/xamarin/the-journey-to-access...
- nicoburns 5y agoDoes QT not work with screen readers?
- deleted 5y ago[deleted]
- mumblemumble 5y agoAccording to the information I was able to gather, it seemed that the answer to that question depends on whether you ask Qt, or a visually impaired user of Qt applications. I decided the latter opinion was the one I cared more about. I'm admittedly trying to play it very safe. I have zero proficiency with screen readers, so I'm not really able to independently verify any of this. All I know is that the GUI toolkit is one of the most expensive things to have to change later, so I want to be as close as I can possibly be to 100% sure that I won't end up in a situation where my projects have accessibility issues that I can't fix without changing the GUI toolkit.
- mwcampbell 5y agoThank you very much for taking the time to research toolkit accessibility and being willing to make it a deciding factor. Which toolkit did you go with? From what I've read, JavaFX apparently has its own accessibility problems; for instance, I vaguely remember reading that if you used Alt+Tab to switch to or from a JavaFX window, JavaFX would automatically activate the menu bar. I've never used a real JavaFX-based app though. As much as some of us might dislike it, I think the safest choice is Electron, or just making it a web app if that's an option.
- tombert 5y ago> I've never used a real JavaFX-based app though. Neither have I; from what I can tell, the only place that JavaFX seems to have a foothold still is "intro to software engineering" classes in colleges.
- mwcampbell 5y ago> "intro to software engineering" classes in colleges That's not nothing. Blind students need to be able to participate in those classes.
- tombert 5y agoOh, to be clear I don't disagree at all. I'm all for making this stuff more approachable.
- lukastyrychtr 5y agoThe basics work, however for example screen readers do not anounce context menus under Windows, treeviews are not providing all the information they could see (https://bugreports.qt.io/browse/QTBUG-81874?jql=text%20~%20%22IExpandCollapseProvider%22 https://bugreports.qt.io/browse/QTBUG-81874?jql=text%20~%20%...), etc. But in the end, if you need somewhat more advanced widgets (tables etc.) and you do not want to implement the gui on each platform or use Electron or similar, you have no choice.
- Cthulhu_ 5y agoHonestly the amount of work people have put in over the years to NOT just build an app with the native tooling is staggering. It really is not that expensive to duplicate some code across multiple target platforms, compared to the compatibility, UX and accessibility headaches. Facebook and Twitter both spend dozens if not hundreds of man-years trying to make HTML lists (tweets, posts) scroll as fast as native. Google is spending IDK how much hours painstakingly redrawing all the native components for both iOS and Android into Flutter, having to catch up every time they make a change. Just use the platform like it was intended to be used. You're not special. You're not smarter. You're forgetting most of what the authors have already solved. And, if you're at the scale of the Facebooks and co, you have the engineers to build it. You have the engineers to rebuild your whole app from scratch a dozen times over. And if you don't, it'll be trivial to find and hire them at the rates you're paying.
- lwb 5y agoThe real problem with Facebook at least is build times -- using the native stack incurs something insane like several hundred hour build times IIRC. So the native stack is just a non-starter once you get to a certain (ludicrous) codebase size.
- 72deluxe 5y agoAre you saying that the client includes all of the Facebook logic or something?? Surely displaying forms (essentially what a post is) and ability to scroll through a list and click on a button or view/upload a photo is the essence of the app? Where's the magical bit that means they can't use a native UI toolkit?
- swiley 5y agoIt's always absolutely fascinating how complicated people can make scrolling and displaying forms. This stuff was solved in the early 90s and everyone's bored now.
- 5y ago
- tombert 5y agoI agree completely. I'm not visually impaired outside of garden-variety nearsightedness, but I sort of have a strong appreciation for "boring" websites that have very utilitarian "Header, subheader, body of text, etc...". They work well with text-only browsers, but also are trivial to make work with various text-to-speech things which I find occasionally useful; sometimes it's just easier for me to understand something if it's being read along to me while reading it, particularly if the font is small.
- 72deluxe 5y agoThey also typically load faster because they don't need megabytes of javascript to "display" the content or offer pointless fading in/out of text and lazy/load of images. All of which means less CPU, fewer network requests and less power used which means a longer-lasting planet.
- tombert 5y agoAt some level I understand that it's kind of a form of artistic expression, and I understand and appreciate that. If people like making pretty and super-interactive websites because it's a way to make themselves happy, by all means they should do it. It's not radically different that someone getting into painting or sculpting in my mind. I think I mostly get annoyed with stuff like news websites of personal blogs having all this extra crap added to it. At the end of the day, I view these things as somewhat utilitarian; I don't go onto a blog to be wowed by a million JavaScript effects, I go there to read text, and maybe some pictures to help elaborate on stuff.
- visarga 5y ago> sometimes it's just easier for me to understand something if it's being read along to me while reading it Doing exactly this right now. I use a bookmarklet to make anything I click start speaking, on any website. It even shows the progress by fading away read words. I've been doing this for at least 7 years, always using Alex from MacOS, at 1.3x. I used to have it work on PDF's as well, but that went away when Chrome's PDF viewer was changed from PDF.js
- econnors 5y agoThere are some folks doing great work here, although I agree on the overall sentiment. Ryan Florence is one name that comes to mind: https://reach.tech https://reach.tech
- brudgers 5y agoApple and Google have done all that work because of accessibility laws at the US Federal and state (particularly California) levels. They have done it because accessibility laws are Civil Rights laws. They have done all that work to avoid problems in the lucrative market that is the US. Microsoft has done similar work for the same reasons. Business reasons. Bottom line reasons.
- dagmx 5y agoWhile that is true, many of the devs also do care greatly about accessibility. As someone who has worked on some a11y stuff, I do it because I think it's the right thing to do, not because of the regulations. The regulations just set a baseline. People often forget there are humans on the other end developing things, not just faceless corporations.
- brudgers 5y agoThe developers are paid to work on those things for the stated reasons. The alignment of interest is fortunate. But the motivations are orthogonal. People often forget that companies are not humans.
- dagmx 5y agocompanies don't make decisions just out of thin air. A lot of the accessibility features on display aren't just meeting the baseline, they go above and beyond. That's done because people legitimately care about this stuff, in addition to it being beneficial to the company. The point is it's not all mutually exclusive.
- brudgers 5y agoI don’t see anything above or beyond. Just an effort to comply with civil rights law. I mean Steve Jobs was infamous for parking his Benz in handicap parking spaces just for convenience. The companies are just as committed on principle as a real estate developer who puts in curb ramps to stay out of court. That doesn’t mean the designer who drew the plans and the building inspector who approved them don’t care about the plight of the disabled. But the ramps are there because of the law not goodwill.
- raarts 5y agoQuestion. Would Flutter fall into this category? Because that would be a dealbreaker for my projects.
- pax_americana 5y agoIt has a pretty good accessibility story for it's built-in widget set (Material and Cupertino). However, if you want to create a new Widget that does not depend on the built-ins but still provide a11y, you can wrap it using the Semantics[1][2] widget. [1] https://api.flutter.dev/flutter/widgets/Semantics-class.html https://api.flutter.dev/flutter/widgets/Semantics-class.html [2] https://youtu.be/NvtMt_DtFrQ https://youtu.be/NvtMt_DtFrQ