News for hackers. Stuff that matters.
Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @09:14AM (#19582161)
This is an impressive feat of engineering. But unfortunately, the resulting UI is completely inaccessible to blind users with screen readers, and probably users with some other disabilities as well.

This will not be easy to fix. AFAIK, if you're using Canvas or WebGL, the only way to make the application accessible is to construct a parallel accessible HTML tree that's completely covered by the canvas via CSS. Note: Don't use "display: none" to hide the accessible HTML tree, because then screen readers will ignore it.

I'm reluctant to rain on your parade, because as I said, this is an impressive piece of engineering. But for the best accessibility and performance, I believe it's better to accept that the Web platform won, and target it directly with a UI that's native to that platform.

Re:Show HN: 300k lines of Java UI code running native in bro... by fsloth on Friday April 05, 2019 @10:20AM (#19582752)
Um, you can't make paintings accessible to blind people nor can you make downhill skiing accessible for four-limb paraplegigs.

There is a public domain within which most disabilities should be catered for but you can't expect that every non-private thing is made public so it's usable by all.

Just because something is 'in the web' doesn't mean it's a public service, access to which is a basic right.

It's good to be reminded to take into account disabilities, of course, since those are not obvious to people who do not have disabled people nearby.

Re:Show HN: 300k lines of Java UI code running native in bro... by brd529 on Friday April 05, 2019 @12:25PM (#19584104)
This is not art or sport, it is a technical demonstration of an interesting way to build web applications by compiling java to javascript. Calling out that this method has accessibility issues seems very on-point for a show hn post. The TeaVM people may not have thought of this, but should consider it as it will eventually become a barrier to adoption of their tech. For example, anyone who sells software to enterprise companies that has customer facing UIs (and potentially employee facing UIs) knows that the interfaces must meet certain web accessibility standards because the risk to the enterprise of facing ADA lawsuits is high.
Re:Show HN: 300k lines of Java UI code running native in bro... by cmroanirgo on Friday April 05, 2019 @03:58PM (#19586412)
Thanks for your comment! I had been wondering where this 'sudden' push toward web accessibility came from: good 'ol US litigiousness!

Of course it's a good thing to be mindful of from a humanist perspective, but if fear of lawsuit is driving the change, it's not a very "love thy neighbour" kind of thing, but more of a fascist dictation, no? Especially if you are not in the US.

I'll be doubling down on my efforts to ensure better compliance nevertheless.

I presume the web standards you mention are part of some US legislation, yes? :S The web is becoming a crazy place, it seems that every country is writing laws that affects the whole web... and we as developers are assumed to know them all, from UI requirements (US) to security implications (Australia), to privacy concerns (GRPR)...

Re:Show HN: 300k lines of Java UI code running native in bro... by austincheney on Friday April 05, 2019 @10:14PM (#19588739)
Accessibility is not a modern fashion. The concerned standard is WCAG 2.0.
Re:Show HN: 300k lines of Java UI code running native in bro... by cmroanirgo on Saturday April 06, 2019 @04:16AM (#19589831)
Thanks for that. I simply hadn't ever encountered it, and stand highly corrected on my ignorance! It's actually been around forever [0]:

> The WCAG 1.0 was published and became a W3C recommendation on 5 May 1999. They have since been superseded by WCAG 2.0.

That said, the current is 2.1:

> WCAG 2.1 became a W3C Recommendation on 5 June 2018

[0] https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guid...

Re:Show HN: 300k lines of Java UI code running native in bro... by austincheney on Saturday April 06, 2019 @07:29AM (#19590275)
https://www.w3.org/TR/WCAG20/

3 November 2008, though it had been available long before in as draft going back to 25 January 2001.

Re:Show HN: 300k lines of Java UI code running native in bro... by toyg on Friday April 05, 2019 @07:34PM (#19588058)
> I presume the web standards you mention are part of some US legislation, yes?

Lots of European companies have similar requirements if they want to sell to the public sector (which is probably even bigger as a market over here, I would expect).

Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @10:32AM (#19582884)
A person with a disability shouldn't be denied any given job because an application is inaccessible even though the job function itself ought to be accessible (e.g., for a blind person, isn't inherently visual). It follows that every line of business application that can be accessible must be accessible. This is why I call this out whenever I learn about an inaccessible UI toolkit. I'm afraid that an inaccessible app will lead to someone being unable to get a job they want, or losing the one they have.
Re:Show HN: 300k lines of Java UI code running native in bro... by monkeynotes on Friday April 05, 2019 @11:42AM (#19583633)
How can a blind person ever be a report designer? The nature of the task is inherently visual. No matter how much accessibility you add to PowerPoint a blind user isn't going to be able to chose the perfect font or position a chart in a meaningful way.
Re:Show HN: 300k lines of Java UI code running native in bro... by miki123211 on Friday April 05, 2019 @03:09PM (#19585962)
I don't have a problem with companies explicitly choosing not to make the apps accessible, unless I'm forced to use them, or they were accessible and it's hard to switch now. I have a problem with UI toolkit developers dismissing accessibility entirely and then companies using those "cool things" to build apps. If you build an inaccessible web app and you want to add a11y later on, you reasonably can. It might be hard, but it's usually doable. If you use a toolkit like this though, you're completely, hopelessly screwed. You can't do anything without rewriting half of the toolkit to support an alternative DOM representation, which will probably affect your performance. I've never seen that done. Either the companies just give up or moan about the shitload of money they've wasted and rebuild the app using normal web components, or build an alternative. Sometimes the law just forces them to, and the toolkit forces them not to. Imagine the sums of money you can waste on this.
Re:Show HN: 300k lines of Java UI code running native in bro... by humblebee on Friday April 05, 2019 @11:53AM (#19583740)
PowerPoint is a pretty poor example. A blind person may not be able to build a PowerPoint template, but I think they should be able to build a PowerPoint presentation using a supplied template.
Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @12:11PM (#19583936)
Exactly. Furthermore, my primary concern is not the app, but the toolkit, since that's what the Show HN i really about IMO.
Re:Show HN: 300k lines of Java UI code running native in bro... by RickTM on Friday April 05, 2019 @12:14PM (#19583971)
Some Powerpoints make me wish I was blind.
Re:Show HN: 300k lines of Java UI code running native in bro... by mattnewton on Friday April 05, 2019 @11:47AM (#19583688)
But this is replacing something with good a11y guidelines, with poorer support. That’s worth warning about, and nothing at all like trying to make downhill skiing for paraplegics.

Imagine using this for a new B2B app and then losing sales because prospective customers have ADA requirements or blind employees who use other web apps just fine. It’s extra engineering work sure, but it’s hardly a crazy ask, and it’s the right thing to do for large to medium size companies who can afford it IMO.

Re:Show HN: 300k lines of Java UI code running native in bro... by tracker1 on Friday April 05, 2019 @01:32PM (#19585007)
Working on an application now with deep a11y requirements. The main function of the application can't be done without sight (validating scanned documents). It's just a little frustrating.
Re:Show HN: 300k lines of Java UI code running native in bro... by mattnewton on Friday April 05, 2019 @05:24PM (#19587182)
There are also sighted keyboard/switch users, a11y is a lot more than just blind users. https://a11yproject.com/posts/myth-accessibility-is-blind-pe...

Implementing good a11y apis allows the variety of vendors to make assistive technology that can navigate your page for all sorts of user categories.

Re:Show HN: 300k lines of Java UI code running native in bro... by tracker1 on Friday April 05, 2019 @07:13PM (#19587916)
I completely understand that... it's simply that some of the hard requirements only make sense for those without sight, but you cannot effectively use the app without at least some sight. (there's decent zoom and contrast support)
Re:Show HN: 300k lines of Java UI code running native in bro... by bzbarsky on Friday April 05, 2019 @11:30AM (#19583492)
"can't" is a pretty strong term. Up until recently, people would have said that you can't make Olympic sprinting accessible to someone with no feet, but it turns out in fact you can, with sufficient application of technology.

So the real question is always whether the technology to make something accessible exists and whether it can be deployed reasonably in the particular instance involved.

Re:Show HN: 300k lines of Java UI code running native in bro... by atomicUpdate on Friday April 05, 2019 @03:02PM (#19585908)
They didn't change the race though, they changed the person running it by giving them pseudo-feet. To continue your analogy, in order for a bling person to use this we just need to give them pseudo-eyes.
Re:Show HN: 300k lines of Java UI code running native in bro... by bzbarsky on Friday April 05, 2019 @03:33PM (#19586174)
That's a worthwhile goal in itself, sure. But I think you're reading too much into what I said. I never claimed the two situations were identical or analogous, just that "can't" is something that needs to be periodically re-evaluated.

But if you do want to press on with sprinting events, note that they have been using start signals with both an audible and a visible component for a while, to accommodate people who may not be able to perceive one or the other. Back until we had electronically-triggered lights, you "couldn't" have a deaf competitor compete, modulo smoke from the starting gun. Now you can.

Re:Show HN: 300k lines of Java UI code running native in bro... by tomcam on Friday April 05, 2019 @08:24PM (#19588328)
> with sufficient application of technology.

Plus years of stupendously painful physical therapy and Herculean will.

Re:Show HN: 300k lines of Java UI code running native in bro... by bzbarsky on Friday April 05, 2019 @11:38PM (#19589043)
Yes, that too. I did not mean to downplay that part at all!
Re:Show HN: 300k lines of Java UI code running native in bro... by haglin on Friday April 05, 2019 @03:54PM (#19586375)
If you want to sell software or services to the government you need to be 508 compliant

https://www.section508.gov/sell

Re:Show HN: 300k lines of Java UI code running native in bro... by phry on Friday April 05, 2019 @04:35PM (#19586759)
> nor can you make downhill skiing accessible for four-limb paraplegics

BS, we can and already have. here's a paraplegic person dropping in on one of the steepest in-bounds runs in the US.

https://youtu.be/MAF08-ko3aw

quit being so dismissive.

Re:Show HN: 300k lines of Java UI code running native in bro... by fsloth on Saturday April 06, 2019 @07:02AM (#19590205)
Cool! My intent was not to be dismissive.

I was not implying people with disabilities should stop doing things, rather, that it shouldn't stop a non-disabled person to do a thing just because a disabled person can't do the same thing.

Re:Show HN: 300k lines of Java UI code running native in bro... by usepgp on Friday April 05, 2019 @06:02PM (#19587457)
He has use of his arms
Re:Show HN: 300k lines of Java UI code running native in bro... by sterlind on Saturday April 06, 2019 @01:18AM (#19589388)
Nitpicking here, but many quadriplegics still have some use of their arms. Depending on the level of SCI and completeness they might not be able to use their pinkies or wrists but still use their arms for transfers or picking things up.

There are actually accomplished quadriplegic pool players. They use a bridge and learn a grip that works. Disabled people are extremely adaptable out of necessity.

Re:Show HN: 300k lines of Java UI code running native in bro... by bytematic on Friday April 05, 2019 @12:53PM (#19584483)
Your not wrong factually but the beauty of web is the fact that it can work for a blind person on the other side of the world or a modern person right next to you.
Re:Show HN: 300k lines of Java UI code running native in bro... by austincheney on Friday April 05, 2019 @10:11PM (#19588725)
> Just because something is 'in the web' doesn't mean it's a public service, access to which is a basic right.

This is not correct and may result in very costly class action lawsuits.

Re:Show HN: 300k lines of Java UI code running native in bro... by omega3 on Friday April 05, 2019 @09:28AM (#19582257)
This is a page layout and report designer, I doubt that the blind users are the target audience.
Re:Show HN: 300k lines of Java UI code running native in bro... by geofft on Friday April 05, 2019 @02:17PM (#19585473)
The title of this submission is "Show HN: 300k lines of Java UI code running native in browser at desktop speed," not "Show HN: page layout and report designer." The criticism is that this particular method of making Java UI code run in the browser, which is being shown to HN because it's presumably interesting to other people with large amounts of Java code as part of different applications, is inaccessible - not that the page layout and report designer is inaccessible.
Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @09:40AM (#19582354)
That's true if the application is entirely about visual layout, e.g. positioning and font sizes. But a blind user should still have an accessible way of controlling the content and structure of a report. And you might be surprised at how much information about layout and formatting is accessible in word processors.

Furthermore, now that this toolkit is available, companies will use it for applications that are required for job functions that ought to be perfectly accessible to blind people. An inaccessible application can lead to a blind person losing their job.

Also, I mentioned other disabilities. A person that can see but has a severe mobility impairment should still be able to use this app.

Re:Show HN: 300k lines of Java UI code running native in bro... by jimbokun on Friday April 05, 2019 @11:05AM (#19583238)
"That's true if the application is entirely about visual layout, e.g. positioning and font sizes."

That's almost exactly what this tool is for.

Re:Show HN: 300k lines of Java UI code running native in bro... by cglace on Friday April 05, 2019 @11:01AM (#19583195)
Should estwing consider consider people without arms while designing their hammers?

I'm not being dismissive I'm just wondering how far your beliefs go.

Re:Show HN: 300k lines of Java UI code running native in bro... by ndarilek on Friday April 05, 2019 @11:51AM (#19583724)
As a blind software developer, I'm kind of sad to see how much Matt is getting pissed on in this thread.

It really didn't seem like he was all that inflamatory, either. He just pointed out the accessibility challenges that I myself face every single day because, what, blindness isn't all that common? Great, so either kill me off[1] or give me enough UBI to not need a job, because there's really no other path for me and my uncommon condition other than, it seems, to constantly assert my existence. Should we make hammers accessible to the disarmed? Ugh, should I have to waste any more of my time because someone on the internet put up yet another straw man for me to knock down?

Look, I'd get it if his initial message was like mine, and I fully expect and don't care that I'll get downvoted for this. And to be clear, this comment is more about the intolerance and dismissiveness I've seen in the replies of what appeared to be a fairly constructive piece of criticism of someone who does accessibility work professionally and gave out free advice. Hell, how often does a Show HN get pissed on because the design looks outdated, and that's just taken as par for the course? People criticized the Thoughter design a few days ago (I don't recall how it was spelled and don't want to look it up) and no one said "Damn, the guy made a product and all you can do is complain about how it looks?" Yet someone voices accessibility concerns and look what happens. I myself have held off on posting some Show HNs because I can't make a website look good. But someone makes a constructive comment about a thing not being accessible along with tips on what might fix it and it's like "OMG get teh blinds outa here!" And now we know why I don't even seek out tech work anymore. Queue up the "maybe you'd have better luck if you behaved better" comments. :)

And to be more constructive, I am a bit worried about the "render everything to a canvas and call it progress" trends I've seen with Web Assembly lately. It isn't just this, but the projects to compile QT and other native GUIs to wasm. Do that and you lose access to the native OS accessibility layers these tools use. I've wondered if there might be a way to create parallel HTML versions of these same widgets so your GTK button might compile to a <button/> with GTK-like styling. But I don't know anyone working in that direction, and I'm not smart enough to pull it off myself. I'm just worried that one day we'll have a pile of thin clients all running in their own canvases. My girlfriend's law firm uses timekeeping software written in the 90s with a web interface. I imagine it's a GUI app running on some basement server with a VNC client in front of it. That's an outlyer, but wasm makes it likely that it won't be, and Matt's concerns as an accessibility professional are completely on-point.

1. To be clear, not a cry for help or anything, but it sort of blows my mind that on one hand people dismiss disabilities because they're not that common. On the other, a large subset of society expects us to try harder to compensate for that apathy. So you either do, and become exceptional, or you just give up to some degree or other and accept that you'll likely never have the nice salary and such. On the gripping hand, most of you are likely to have one of these "uncommon" disabilities when you age. Hope you enjoy whatever you do while you can do it. It's going to be fun learning how to keep coding in your 70s when half the tools you took for granted aren't accessible to the screen reader you use because your glasses no longer cut it. :) I don't expect folks to bow and scrape when a thing isn't accessible, but to shit on someone for politely pointing that out is quite an unfortunate reaction.

Re:Show HN: 300k lines of Java UI code running native in bro... by bartread on Friday April 05, 2019 @01:02PM (#19584591)
Not to minimise accessibility concerns, but I think Matt's getting pissed on because rather than focus on the (impressive) achievement here he's diverted attention away from that and has (I think perhaps inadvertently) created a discussion that's beginning to resemble a social media pile-on. Accessibilty matters but this isn't an edifying spectacle and focussing on it in the way this discussion does is taking something away from what is otherwise quite a cool tech demo. I.e., it is raining on the parade.
Re:Show HN: 300k lines of Java UI code running native in bro... by ndarilek on Friday April 05, 2019 @01:14PM (#19584762)
And again I ask, when someone else produces some technically great achievement and people pile on about the design looking bad, why is that treated any differently? Why isn't that raining on the parade?

In a parallel universe, someone might have said "You're right, it isn't accessible. That wasn't my goal, and if this ever does take off then I might have to investigate other options."

But that isn't what happened, it's a bit of a double standard, and that double standard has real consequences for some of us. The bulk of the pile-on doesn't seem to be coming from my friend, but rather from a bunch of folks criticizing him for daring to politely suggest that there's another perspective worth considering.

If your response is "because more people care about the visual design of a technically sound concept than whether it is accessible because looks matter," then I'd agree with that, and we can just leave it there without casually dismissing an entire group of real people who matter. But again, that isn't what happened here.

I wish I could post web apps I've made here without contending with the half dozen "your design sucks" comments I'd likely get. But if I got them then I'd expect them, and that frustrates me to no end.

FWIW, I'm not actually all that upset. I'm kind of used to this, actually. And I know you're just trying to explain why things are what they are, which is exactly what I'm doing. :)

Re:Show HN: 300k lines of Java UI code running native in bro... by jerf on Friday April 05, 2019 @03:09PM (#19585960)
"And again I ask, when someone else produces some technically great achievement and people pile on about the design looking bad, why is that treated any differently? Why isn't that raining on the parade?"

It is. HN rains on a lot of parades. It's a bit notorious for it. There are people who have posted that they have things they want to Show HN but don't particularly want... well, exactly this.

Re:Show HN: 300k lines of Java UI code running native in bro... by ndarilek on Friday April 05, 2019 @04:16PM (#19586589)
Fair point. On one hand it makes me a little sad to see parades rained on. On the other, I assume folks want some degree of criticism if their ideas have some sort of flaw. On the gripping hand (such a useful metaphor, that) if we're going to tolerate some amount of politely-phrased negative feedback, then we probably shouldn't sweep some of it under the rug because it isn't the "acceptable" kind of feedback. Not that you are doing that, mind you. But it seems like some of that may have happened here.

Full disclosure: I know Matt and think he's a good guy, and he reached out to me wondering if he'd done something wrong. And I can actually kind of see both sides of this situation. But unlike him, I know I'm kind of a hard-ass about access issues not because I want to be, but because today's cool idea might be tomorrow's "no job for you, Nolan," and not because anyone wants that, but well, what do you tell someone who wants to work for a company but can't because most of the tools they use aren't accessible, so you literally can't do the job they need? And yes, this has happened to me before. And we can sit around and talk about privilege or who is at fault all day, which may certainly be a worthwhile discussion to have, but at the end of the day, the discussion I most want to have is "are you going to change your company's workflow to account for the fact that I'm qualified to do this job but can't as things stand?" and the answer is usually "nah, easier to find someone else, sorry."

So that's where Matt and I are coming from, and I wish folks hadn't piled onto him for trying to express that. And while I'd like to be nice and polite about that, well, what do I get when I am? A cookie? I'll try to pay the rent and do fun stuff with that cookie, thanks. :P

Enough novels from me. Got stuff to do. :)

Re:Show HN: 300k lines of Java UI code running native in bro... by DoreenMichele on Friday April 05, 2019 @03:19PM (#19586052)
This is not limited to HN. In any group setting, arguing against a thing is frequently counterproductive.

Social settings are "attention economies." Piling on to the argument adds attention to the thing you nominally want less of, yet are fueling. I generally try to not add to such situations.

I used to say "Fighting against the fighting is still fighting." If I am going to wade in, ideally, I should do so without being combative about it.

I have been debating whether or not to send the comment about how this is not accessible for the blind to a group I co-own called Blind Dev Works. Not sure if it is relevant to the interests of others there. I'm visually impaired and generally interested in accessibility, but I'm not blind, nor really a developer (though I actually want to learn to code and I'm trying to do something about that).

I don't know if it would just be seen as salt in an open wound or an interesting discussion.

Re:Show HN: 300k lines of Java UI code running native in bro... by ndarilek on Friday April 05, 2019 @04:01PM (#19586443)
I don't think it'd be salt in a wound--or at least I wouldn't see it as such. I do wish someone smarter than I am could come up with an accessibility backend to map GUIs to accessible HTML interfaces. So just as QT apps push accessibility objects to Linux/Windows-native accessibility APIs, something could push either ARIA-enhanced <div>s to the browser, or could just output fully-accessible HTML. So instead of QT rendering to a canvas, it could render to another target that just happens to be HTML elements. Substitute any other GUI toolkit with an accessible object representation for QT in my previous paragraph to get a sense for the scope of the problem.

I've just never dived into how those particular APIs work mainly because, well, there are so many problems needing solutions, and I happen to be focusing on others. Surely I'm not the only one to have thought of this, though, and on the off-chance that I am, the best thing I can do is keep mentioning it until someone else decides it's worth trying. :)

Re:Show HN: 300k lines of Java UI code running native in bro... by DoreenMichele on Friday April 05, 2019 @04:06PM (#19586496)
Thanks. I've sent some links and excerpts from the discussion (to Blind Dev Works).

(Anyone on HN interested in joining Blind Dev Works is welcome to shoot me an email. I"m happy to send an invitation. It's a small, low traffic group.)

Re:Show HN: 300k lines of Java UI code running native in bro... by miki123211 on Friday April 05, 2019 @02:55PM (#19585847)
When reading this, I just wish HN had a superupvote button. As a blind person, it echoes back my thoughts exactly.
Re:Show HN: 300k lines of Java UI code running native in bro... by ralusek on Friday April 05, 2019 @11:58AM (#19583792)
Make hammers inaccessible to the disarmed? A hammer is a tool for a function. It's not the materialization of privilege for the armed.
Re:Show HN: 300k lines of Java UI code running native in bro... by ndarilek on Friday April 05, 2019 @12:25PM (#19584107)
Sure, but in the context of building a visual layout tool, for someone to say that it shouldn't or doesn't need to be accessible to a blind person because OMG, visual! completely misses the point that it can be, and that other tools before it are. To say "I didn't have time to focus on accessibility because I was struggling with the challenges of making a Java codebase run under wasm" is one thing, and a thing I myself can relate to, having banged my head on wasm's challenges myself. To say "there's just no way to make a visual layout tool accessible to folks who can't see, so I'll just throw up my hands and give up" is another entirely. And I don't think that's what OP is doing, but I do think it's what some in this comment thread are advocating, and that's what bugs me.
Re:Show HN: 300k lines of Java UI code running native in bro... by ndarilek on Friday April 05, 2019 @12:34PM (#19584230)
Also, on a note directly applicable to this example, if you think hammers are unusable by folks without arms, might I suggest the documentary Right Footed? I can't say whether or not she uses a hammer without arms, but she flies a plane and drives with her feet, so I can't imagine her not using a hammer if she didn't want to.

It feels a bit inspiration-porny at times, and my girlfriend and I both cringed quite a bit while watching it, but I think it makes the point I'm trying to much better than I am. Please don't dismiss a challenge out of hand because you can't imagine in 15 seconds of thought how it might be overcome.

"you" being a generic term applicable to anyone reading this, BTW.

Re:Show HN: 300k lines of Java UI code running native in bro... by ralusek on Friday April 05, 2019 @12:46PM (#19584394)
> a challenge _out of hand_

-_-

Re:Show HN: 300k lines of Java UI code running native in bro... by ralusek on Friday April 05, 2019 @12:44PM (#19584387)
Making something accessible for a group of people is an opportunity cost at every step in the process. For some reason you've determined that "making the Java codebase run under wasm" is an acceptable diversion from making it accessible, but what makes other decisions less so? For example, I haven't bothered supporting IE for many years, regardless of the fact that there are potential users that will be unable to use services because of it. Same thing with internationalization, there's an opportunity cost that has to be made. That doesn't mean don't make the decision to expand support, I'm just saying that it IS a decision and it DOES have a cost.

If you don't perceive it that way, you have to accept that there is a near infinite number of accessibility measures to contend with. Maybe I add support for red green color blindness, and then discover there are other types. The package bundle is too large for users in countries with poor internet access, so you need to have a fallback that removes features, and dedicate some resources to minimizing the initial load time. Oh, the input configuration doesn't make sense for users who are unable to use keyboard and mouse, but use an alternative input mechanism, you have to change it to support that. Oh no, adding support to assist those users has made able users switch to the assisted input configuration, and given them a competitive advantage in your game.

Every company cannot service every need. Those that service a need open potential to acquire the market. That may or may not be worth it or possible at any given point, and that's okay.

Re:Show HN: 300k lines of Java UI code running native in bro... by ndarilek on Friday April 05, 2019 @01:24PM (#19584888)
Can we just agree that Matt was pointing out a gap and leave it at that?

I know more than most people that there is a cost to making things accessible. Do you not think that I get the dumbed-down, PR/support-filtered version of that response every single time I reach out to a company and tell them that a thing my company is using is unusable by me? :)

But I think we, by which I mean everyone in this thread, can acknowledge that without implying that our needs aren't worth considering because there aren't many of us, or that they aren't worth considering because no one immediately knows how. If that isn't what folks have done here then I'll own my misunderstanding, but folks could have just acknowledged the comment rather than criticizing him for having the audacity to suggest that I too might want to appreciate the technical achievement for myself..

And FWIW, I kind of resent having my disability, which no amount of learning or software upgrades will fix, lumped into the same category of English proficiency or IE 6. That does feel a bit condescending. Saying "well, some people can't upgrade their browsers" is in an entirely different league than a visual disability that no amount of upgrades or night classes can fix. I'm not saying that switching browsers or learning a new language are possible for everyone, but short of gene editing, there is no way for me to eliminate my blindness. I'm not upset about the examples you chose, but would like to politely suggest that you reframe how you think about these issues. :) Thanks, and not in a snarky way. :)

Re:Show HN: 300k lines of Java UI code running native in bro... by ralusek on Friday April 05, 2019 @03:33PM (#19586171)
I was worried that me bringing up other accessibility consideration might come off as making the case that a browser upgrade was an equivalent inconvenience as blindness, and that wasn't my point at all.
Re:Show HN: 300k lines of Java UI code running native in bro... by ndarilek on Friday April 05, 2019 @04:20PM (#19586615)
That's fair. I accept that isn't what you meant. Thanks for confirming it, and apologies for the implication.
Re:Show HN: 300k lines of Java UI code running native in bro... by squeaky-clean on Friday April 05, 2019 @01:09PM (#19584700)
> or some reason you've determined that "making the Java codebase run under wasm" is an acceptable diversion from making it accessible,

They didn't say that. They said "I didn't have time to focus on accessibility because I was struggling with the challenges of [...]" You're focusing on the [...] which could be anything, it doesn't matter. The point is they're acknowledging it's a legitimate issue that they just didn't have the time or ability to fix. As opposed to saying it's a non-issue or something they refuse to fix.

For example, "My personal website isn't accessible because I wrote the code from scratch to learn myself and it's not perfect" is fine. "My personal website isn't accessible because I don't have any blind friends so it doesn't need to be" is less so.

Re:Show HN: 300k lines of Java UI code running native in bro... by ndarilek on Friday April 05, 2019 @01:27PM (#19584932)
Thanks, a thousand times this. :) Even though this particular codebase doesn't bother me at all, my perception of the responses in this thread does bug me, and I appreciate that someone less emotionally attached than I am has both gotten it and taken the time to try explaining it.
Re:Show HN: 300k lines of Java UI code running native in bro... by orf on Friday April 05, 2019 @01:12PM (#19584740)
> you have to accept that there is a near infinite number of accessibility measures to contend with

This is why we have accessibility standards and guidelines that are not an infinite number of pages long.

Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @09:36AM (#19582323)
That last paragraph wasn't entirely constructive. I'm sorry about that. I realize there are lots of existing applications that can't be rewritten to directly target the Web platform. But I still believe that new ones should.
Re:Show HN: 300k lines of Java UI code running native in bro... by stefan_ on Friday April 05, 2019 @04:17PM (#19586602)
Targeting the "web platform" does not by itself magically make an application accessible. It is vastly easier to make a native iOS or Android app accessible given the well defined rich widgets and the absence of 20 years of HTML and CSS evolution.
Re:Show HN: 300k lines of Java UI code running native in bro... by dyarosla on Friday April 05, 2019 @01:04PM (#19584626)
> I believe it's better to accept that the Web platform won

The "Web platform" is not a single thing. It is a bunch of things that are constantly evolving, that are also implemented differently by different browser vendors that have their own issues.

Just because the web purports to have a (sometimes) working UI that is accessible to some percentage of users on some percentage of devices doesn't mean that we should stop there and not experiment anymore in other directions (even if those new directions could, initially, not support all a11y functionality that 'the Web' already provides, for screen readers or what else have you).

There is no "the Web won, accept it"- many things are terribly broken, before even taking a11y into account. Just note how many dysfunctional UI paradigms exist that don't support what we call 'responsive web design', often from the biggest companies in the world!

A11y isn't anywhere close to a solved problem on the Web any more than responsive layout is -> it should not be the target specification to work towards just because.

As a final thought experiment: what if we are going about a11y all wrong? What if screen readers and tree hierarchies of components aren't the right way to approach building these things and instead the better solution is to completely do away with that approach and instead make new screen "readers" that use AI to better visually determine elements on screens after the fact. AI is definitely at a point where it can classify buttons from text and images, as well as read out text in several kinds of fonts. If this becomes the future, it'll render all of our current web 'standards' to look like an unnecessary hassle of working with the more disingenuous and restricted (in the sense of, you can only use such and such component in such and such way) methods of today.

What I'm saying is, encourage people to experiment with new UIs that don't yet conform to standards. By all means, mention that you wonder about a11y and ask what the plan might be going forward. But don't dismiss these experiments too early cause they're not built in the "right way".

Re:Show HN: 300k lines of Java UI code running native in bro... by HeWhoLurksLate on Friday April 05, 2019 @02:44PM (#19585739)
> > I believe it's better to accept that the Web platform won

> The "Web platform" is not a single thing. It is a bunch of things that are constantly evolving, that are also implemented differently by different browser vendors that have their own issues.

Maybe The Web, as a platform won?

EDIT: Formatting

Re:Show HN: 300k lines of Java UI code running native in bro... by jeffreportmill1 on Friday April 05, 2019 @09:26AM (#19582250)
You're right - it would require a bit of work, however, it wouldn't be that bad for a shared UI framework. I also think this kind of thing will be more common as WebAssembly allows other languages to move to the browser.
Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @09:45AM (#19582395)
Did you consider an SWT-like approach, where the toolkit uses each platform's native widgets? Porting SWT to the Web platform might even be feasible.
Re:Show HN: 300k lines of Java UI code running native in bro... by jeffreportmill1 on Friday April 05, 2019 @10:03AM (#19582571)
I have gone down this road before - but I think this is why many people saw Java as "Write Once, Debug Everywhere". It's just hard to write an abstraction that fronts for so much different native code on different platforms. Something is always going to break. Whereas if you run the same code everywhere, it might actually run everywhere.
Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @10:17AM (#19582714)
So, I guess you have to either take on the extra work of debugging multiple UI implementations, or take on the extra work of making your own toolkit accessible. Personally, I would have chosen the former.
Re:Show HN: 300k lines of Java UI code running native in bro... by LoSboccacc on Friday April 05, 2019 @12:42PM (#19584363)
https://www.eclipse.org/rap/ (and others)

doesn't work that well because the event model between web and desktop is radically different. if you don't have complex interactions or expectation about your widgets it kinda works.

Re:Show HN: 300k lines of Java UI code running native in bro... by vijaybritto on Friday April 05, 2019 @05:04PM (#19587034)
Honestly the replies here are the most meta discussions I have ever seen. So toxic and rude!
Re:Show HN: 300k lines of Java UI code running native in bro... by anoncake on Friday April 05, 2019 @09:27AM (#19582256)
> Note: Don't use "display: none" to hide the accessible HTML tree, because then screen readers will ignore it.

That sounds like a use case for @media queries

Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @09:42AM (#19582373)
That opens a whole other can of worms. Some blind people don't want a website or web application to be able to detect that they're running a screen reader, and by extension, that they're blind. [1] I'm not sure where I stand on that issue.

[1]: https://news.ycombinator.com/item?id=19547239

Re:Show HN: 300k lines of Java UI code running native in bro... by mastazi on Friday April 05, 2019 @10:42AM (#19582995)
Media queries are instructions that the client can use, unlike other methods like user-agent there is no info being sent over to the site. Of course a malicious page could implement js code to try and understand what bersion of the page the client is actually rendering, but it would be quite easy for the client to circumvent that.
Re:Show HN: 300k lines of Java UI code running native in bro... by ago on Friday April 05, 2019 @11:59AM (#19583803)
Media queries can leak info to the server easily without JavaScript: https://matt.traudt.xyz/p/YF4ciVY6.html
Re:Show HN: 300k lines of Java UI code running native in bro... by mastazi on Friday April 05, 2019 @07:19PM (#19587964)
For a client that did not want to send info, this would be even easier to prevent than the JS scenario discussed above...
Re:Show HN: 300k lines of Java UI code running native in bro... by anoncake on Saturday April 06, 2019 @08:53AM (#19590472)
Especially for a screen reader: It can fetch all images intended for seeing people anyway while ignoring images intended for screen readers.
Re:Show HN: 300k lines of Java UI code running native in bro... by anoncake on Friday April 05, 2019 @12:01PM (#19583823)
I bet there already is a way to detect that.
Re:Show HN: 300k lines of Java UI code running native in bro... by Wowfunhappy on Friday April 05, 2019 @03:42PM (#19586263)
Would a traditional desktop java application have been more accessible?
Re:Show HN: 300k lines of Java UI code running native in bro... by Arnavion on Friday April 05, 2019 @04:30PM (#19586718)
Google suggests that users can enable a "Java Access Bridge" (ships with JRE but disabled by default) that enables the Windows Accessibility API to work with Swing applications.
Re:Show HN: 300k lines of Java UI code running native in bro... by dosy on Friday April 05, 2019 @10:25AM (#19582809)
It's also inaccessible to non-English speakers.

A11Y is not the bottom line to judge everything by. That dilutes it's importance as a niche. Judging by a11y is a power that should be used responsibly, not as a last resort to just find something critical to say.

It's inaccessible to non English speakers and that's not a problem because it just doesn't matter enough. Same thing with disability. There's just not enough disabled people to justify critiquing everything that's not usable with screen readers.

The world is not accessible to every group within it, and that's okay, that doesn't mean everything that isn't able to be used by some group is somehow bad or deficient. To discriminate against apps that don't have certain abilities is just the same bias as discriminating against people with different abilities. Be more tolerant of apps that are serving their special niches and nothing more.

Re:Show HN: 300k lines of Java UI code running native in bro... by kalleboo on Friday April 05, 2019 @02:15PM (#19585453)
You can't even type in Japanese. Typical cross-platform "well we got it to run everywhere!" solution.

So now we have a framework running on a VM running on a VM running inside a sandbox running in microcode (did I miss a level?). Can't wait for the next abstraction!

Re:Show HN: 300k lines of Java UI code running native in bro... by HeWhoLurksLate on Friday April 05, 2019 @02:27PM (#19585577)
CPU architecture?
Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @10:47AM (#19583037)
I'm not calling this out just to be critical. I call this out because I don't want people to be blocked from doing their jobs productively, or at all, due to an accessibility problem that could have been prevented.
Re:Show HN: 300k lines of Java UI code running native in bro... by dosy on Saturday April 06, 2019 @02:57AM (#19589643)
This is not a software problem. Software doesn't need to absorb every requirement. You can prevent this problem in ways that don't involve pretending that somehow it's the responsibility of every software developer to use a11y in every product. So judging as if that's in scope is incorrect, is a wasteful use of judgement and, if people are convinced, a wasteful use of software resources.

Doing that is just harming a11y efforts, by insisting software must be the fix, when there are plenty of other solutions that don't involve rewriting / redesigning a piece of software, likely to deliver solutions faster or better than changes to software.

At this point, I really don't know why you keep advocating this path as your goal can be achieved through other means. Get off the idea that a11y critiques are the ultimate trump card. They are not.

Re:Show HN: 300k lines of Java UI code running native in bro... by giornogiovanna on Friday April 05, 2019 @11:23AM (#19583423)
Still, by your logic, every app must be translated into every language. It's okay to exclude people, especially when you're small and don't have the resources to cater for the needs of every single person.
Re:Show HN: 300k lines of Java UI code running native in bro... by Piskvorrr on Friday April 05, 2019 @12:48PM (#19584422)
Nope. The point is "the underlying toolkit should enable this." I18n and l10n are somewhat better supported in this regard than a11y.
Re:Show HN: 300k lines of Java UI code running native in bro... by geofft on Friday April 05, 2019 @02:16PM (#19585463)
Apps should be translatable, even if they're not translated. If you're small, you're not obligated to translate an app to every possible language, but it is bad engineering to make your UI dependent on your primary language in a way which would make it hard to ever add support for a new one.
Re:Show HN: 300k lines of Java UI code running native in bro... by anoncake on Friday April 05, 2019 @11:55AM (#19583758)
People can learn foreign languages. Disabled people cant stop being disabled.
Re:Show HN: 300k lines of Java UI code running native in bro... by HeWhoLurksLate on Friday April 05, 2019 @02:32PM (#19585638)
The impossible just takes longer.

And money.

https://www.mayo.edu/research/departments-divisions/departme...

Re:Show HN: 300k lines of Java UI code running native in bro... by austincheney on Friday April 05, 2019 @10:21PM (#19588763)
Translatable not translated. Failing to see the difference is likely an accessibility violation.
Re:Show HN: 300k lines of Java UI code running native in bro... by maimeowmeow on Friday April 05, 2019 @04:36PM (#19586764)
Why does it matter, blind people cant see.
Re:Show HN: 300k lines of Java UI code running native in bro... by bufferoverflow on Friday April 05, 2019 @09:58AM (#19582520)
Not everything has to be accessible. 100% blindness isn't that common. And even if it was, there's nothing wrong with making apps for people with good vision.
Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @10:02AM (#19582561)
A blind person can lose their job because an application that's required for the job is inaccessible, even though the job function ought to be perfectly accessible (i.e. isn't inherently visual). That happened to an acquaintance of mine. May it never happen again.
Re:Show HN: 300k lines of Java UI code running native in bro... by fastball on Friday April 05, 2019 @10:08AM (#19582619)
How is that the application creator's fault?

That's a problem with the employer, not the application. Applications do not need to cater to every edge case of humanity.

Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @10:11AM (#19582649)
Yes, the employer is at fault in that case. But the application creator is as well, because they erected the barrier of an inaccessible app.
Re:Show HN: 300k lines of Java UI code running native in bro... by fastball on Friday April 05, 2019 @12:21PM (#19584046)
They "erected" nothing.

Accessibility is not something that exists until a developer nerfs it. Accessibility takes time and effort to implement.

Take two examples:

* I release an app without much accessibility support on April 5th. Immediately, 90-95% of my prospective customer base can use the app. 5-10% cannot. Over the next few months, I improve my app's accessibility and release the new version on July 5th. Now, 99% of potential customers can use it. In the interim period of three whole months though, the vast majority of potentials were able to use my product.

* I think an app is not worth releasing until it has comprehensive accessibility support. It takes me a couple extra months than it would've without it, but eventually I release my product on July 5th. Yay. 99% of my potential customers can use it at the time of first release.

You really think the second example is better?

Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Friday April 05, 2019 @12:38PM (#19584291)
I actually do think the second scenario is better. Some people will lack a convenience in the intervening three months (and remember that's a very optimistic case; it could be4 much longer). But at least a person with a disability won't lose their job because it now requires an app that they can't use.
Re:Show HN: 300k lines of Java UI code running native in bro... by jhayward on Friday April 05, 2019 @05:56PM (#19587416)
Ok, now give your reply when the 'app' is critical to saving lives. Each hour it isn't available costs, let's say, 1 infant their life who could otherwise have been saved, per 1000 app users.

The point of the exercise being that you seem to be dismissing the fact that there are actual bad consequences to the 'must be 100% accessible upon first release' principle, simply because a person for whom accommodation is required now has a job.

What I don't see in your argument is some sort of equitable discussion of who bears what costs, and how that equity is fairly determined.

Re:Show HN: 300k lines of Java UI code running native in bro... by yjftsjthsd-h on Friday April 05, 2019 @11:10PM (#19588954)
> Some people will lack a convenience in the intervening three months

> lose their job because it now requires an app that they can't use.

So is it a convenience or essential for the job? If it is a convenience, then it isn't essential. If it is essential, you're denying it to the larger group in the interim.

Re:Show HN: 300k lines of Java UI code running native in bro... by sbov on Friday April 05, 2019 @11:36PM (#19589027)
I think the idea is: the new app is a convenience to a job that existed before the app. The company that uses it then decides to make it essential to that job.
Re:Show HN: 300k lines of Java UI code running native in bro... by mwcampbell on Sunday April 07, 2019 @10:35AM (#19596994)
Yes, you got it.
Re:Show HN: 300k lines of Java UI code running native in bro... by fastball on Friday April 05, 2019 @05:41PM (#19587330)
So you think it's better for everyone to have less convenience so that it is literally impossible to discriminate, instead of just telling employers "don't discriminate"?

Maybe we should just go ahead and gouge everyone's eyes out to really level the playing field...

Re:Show HN: 300k lines of Java UI code running native in bro... by HeWhoLurksLate on Friday April 05, 2019 @03:00PM (#19585890)
If you've taken calculus, you'll understand the idea of area under the curve- the number of people using your app will likely go up over time, and it takes time to accrue customers (the area under the curve of the rate of customers). One thing that you should think about is that it takes time for products to gain momentum, and as a product gains momentum, it generates revenue. As such, it might make sense to ship your code without much accessibility support and add it in the ensuing months. If you can be available to even 50% of potential customers three months before the first scenario, by only releasing for people using the OS you develop on, and then you go cross-platform in three, (making your population ~90%) and then add accessibility in the sixth month, it would still make sense from a business point of view to do so.

Keep in mind that things take time to develop a userbase, and that large companies really like things to have an established userbase and support before they get on board. For instance, one of the major reasons that the Raspberry Pi Foundation has seen so much success, even though they aren't the fastest or the cheapest, is because they have a large community support network and support their stuff well.

As such, as long as I (and / or management) are committed to implementing solely-accessibility related features in the near future, I would take the first option, and release as soon as I could.

Re:Show HN: 300k lines of Java UI code running native in bro... by vinceguidry on Friday April 05, 2019 @11:23AM (#19583425)
I share your sentiments. Anybody building a tool that could conceivably be used for work purposes has a moral impetus to treat accessibility as a first-class citizen. The standards are there, the profit motive should be there and thus the resources should be there.

The only reason not to is greed.

Re:Show HN: 300k lines of Java UI code running native in bro... by yjftsjthsd-h on Friday April 05, 2019 @11:12PM (#19588963)
> the profit motive should be there

> The only reason not to is greed.

This seems contradictory? If there's a profit to be had, then greed would demand that it be taken.

Re:Show HN: 300k lines of Java UI code running native in bro... by LoSboccacc on Friday April 05, 2019 @12:37PM (#19584289)
> The only reason not to is greed

while accessibility is important this extremisation is a little rich under a post of a literally free tool.

Re:Show HN: 300k lines of Java UI code running native in bro... by vinceguidry on Friday April 05, 2019 @12:43PM (#19584372)
You're ignoring the preceding qualifiers. A tool that can be used for work, and a profit motive.
Re:Show HN: 300k lines of Java UI code running native in bro... by LoSboccacc on Friday April 05, 2019 @01:08PM (#19584675)
that's a non sequitur. a free tool doesn't have a profit motive and a company using the tool for profit doesn't attach a profit motive to the tool itself.
Re:Show HN: 300k lines of Java UI code running native in bro... by HeWhoLurksLate on Friday April 05, 2019 @03:06PM (#19585939)
But they have an interest in their "free" tools being around the next day, don't they? Otherwise they have to either do it the "old way" or find a replacement, both of which cost time. At $100,000 a year per 40-hour-work-week developer, a team of 5 developers costs $240 an hour. That's a lot to lose because your tools disappeared. Analogous to physical work, consider what getting a new tool that's slightly different does to your muscle memory- there's an inherent value in having long-lasting tools, even if they're free.