4

How about using screen readers or text only browsers with Dapps? Has someone ever tried existing Dapps with this tools? Thanks.

  • Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. – niksmac Apr 19 '16 at 11:35
  • I don't really see opinions in this. Just say if you tried a dapp using accessibility tools and report if it worked. Only facts. If you think that saying if a dapp is accessible or not relates to opinions you're wrong. There's accessibility guidelines and checklist for web apps since a long long time ago. – Nicolas Massart Apr 19 '16 at 11:44
  • @NMassart the problematic part here is where you ask if people have tried existing Dapps with these tools. Maybe you could try to improve your question by giving a specific Dapp as example and what your specific concerns are? Javascript itself might not have to be a problem anymore for the last couple years due to recommendations like ARIA – Joris Bontje Apr 19 '16 at 12:11
  • 1
    OK, I see your point. I will try myself Dapps using these tools and see how it works and then ask. But the point is that I don't have these tools. I just feel concerned by accessibility but as someone without disabilities. That's why I expected some feedback ideally from people with vision problems. But you're right I'll try myself and come back. – Nicolas Massart Apr 19 '16 at 13:38
4

This is the same as any other web application which uses JavaScript. If your front end is HTML / JavaScript you will use the same techniques to comply with your AAA standard chosen.

For example the WAI-ARIA (Accessible Rich Internet Applications (WAI-ARIA) 1.0), as mentioned in the comments. More info: https://www.w3.org/TR/wai-aria/

Just to note, the front end does not need to be Html / JavaScript, it can be in any language which can interact with the client (.Net, Java, Ruby...), and it will follow the usual design rules for accessibility.

  • Except that most web site, it they're well designed and if accessibility is taken in account, could work in a degraded mode without JS and dynamic ui design. Using xhr can be replaced by full pages loading. Here we need the web3 Api and it's not for cosmetics. – Nicolas Massart Apr 19 '16 at 11:47
  • 1
    Yes but these are rich web applications, not web sites, web sites are for content. How will it work soundcloud, trello, etc.. A dependency on JavaScript is not an issue. – Juan Blanco Apr 19 '16 at 16:28
  • You mean that as it's already not accessible so that's not an issue if it's still not accessible ? Or am I misreading you... – Nicolas Massart Apr 19 '16 at 16:41
  • 1
    No what I meant, is that any application (regardless of front end technology) when designed correctly complies with accessibility standards. – Juan Blanco Apr 21 '16 at 5:05
  • 1
    If your frontend is in javascript/html you could follow this standard: w3.org/TR/wai-aria This is an interesting article also: parhamdoustdar.com/2016/04/03/tools-of-blind-programmer – Gerbrand Apr 21 '16 at 8:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.