transifex / transifex-old-core

Translation workflow & crowdsourcing for agile teams. Older, open-source codebase of Transifex.com
https://www.transifex.com/
GNU General Public License v2.0
5 stars 5 forks source link

The website is not very accessible for translators using Assistive Technologies. #232

Open rhdunn opened 11 years ago

rhdunn commented 11 years ago

The "click for translation" buttons (and other buttons that execute JavaScript code) are not usable through screen readers and other Assistive Technologies such as Jaws. This makes it impossible for blind users to help contribute translations to a project.

nsallembien commented 11 years ago

Hi Reece,

Sorry our editor wasn't built in a very accessible manner. We would love to try and help, but quite frankly we do not know how to make this work for you. Would you be able to give us some pointers, or advice?

Thanks Nico

rhdunn commented 11 years ago

Hi,

I am not the one using the site through assistive technologies -- some people on the eyes-free mailing list are (see https://groups.google.com/forum/#!forum/eyes-free). You could get in contact with the people there -- I'm sure they will be willing to help you test the site to improve its accessibility. They were how I found out about this issue (see the https://groups.google.com/forum/#!topic/eyes-free/Q-TI6QAifBs thread).

As for making the site accessible, there is the WAI-ARIA web standard for annotating parts of the page (especially if it uses non-standard markup for links and other things).

http://www.w3.org/WAI/intro/aria is the main W3C page on ARIA.

http://www.w3.org/TR/wai-aria/ is the WAI-ARIA specification document and http://www.w3.org/TR/wai-aria-primer/ a primer/introduction.

http://www.w3.org/TR/wai-aria-practices/ has some tips on annotating HTML with WAI-ARIA markup.

http://dev.opera.com/articles/view/introduction-to-wai-aria/ is another introductory article on ARIA and serves as a good overview of the problem faced by Rich Internet Applications in supporting accessibility.

http://blog.paciellogroup.com/2010/10/jaws-support-for-aria/ has information on how the JAWS screen reader handles WAI-ARIA content.

There is also the http://www.marcozehe.de/articles/how-to-use-nvda-and-firefox-to-test-your-web-pages-for-accessibility/ blog post. The NVDA screen reader is a Free Open Source screen reader, so makes it easy to test website accessibility.

That website (http://www.marcozehe.de/) also has other tips and tricks on using WAI-ARIA, including http://www.marcozehe.de/2013/04/24/easy-aria-tip-6-making-clickables-accessible/.

pvagner commented 11 years ago

Hello, I think Reece has provided impresive studying resources. I just would like to add into this that I am one of those potential visually disabled users. I would like to start translating. I have registered, logged in, applied for a position in the team. And received a notification stating I am now part of a team. This worked all verry well except of one little issue which can be easilly worked around on my part. While trying to join a team there is a link join team. This is fully accessible. However after activating the link the javascript code updates the page by appending a form to the end and it then positions that form so it looks correct. However nothing happens what would indicate the change to the assistive technologies. So in order to access the form that has been inserted I have to scrol down to the verry bottom of the page and activating the join button which is again verry accessible. It would be reasonable to move the focus to one of the controls inside that form as it pops up.

However when all this is done I can browse the languages, see some of the details however I am unable to figure out how I can get the file for translation. Can you please describe step by step how and where the controls for downloading a file or translating it are so I can try to come up with a workaround until the issue can be fixed? Ideally we need to have a focusable control which can be operated using keyboard only.

Greetings

Peter