3 ms·

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

by brd529 8y ago

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.

cmroanirgo 8y ago
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)...
- toyg 8y ago
  > 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).
- austincheney 8y ago
  Accessibility is not a modern fashion. The concerned standard is WCAG 2.0.
  - cmroanirgo 8y ago
    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_Guidelines https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guid...
    - austincheney 8y ago
      https://www.w3.org/TR/WCAG20/ 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.

by brd529 8y ago

cmroanirgo 8y ago

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)...

toyg 8y ago
> 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).
austincheney 8y ago
Accessibility is not a modern fashion. The concerned standard is WCAG 2.0.
- cmroanirgo 8y ago
  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_Guidelines https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guid...
  - austincheney 8y ago
    https://www.w3.org/TR/WCAG20/ 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.