Google Translate

[anormand]

Expert reviewer's comment

The controls for switching to another language were accessible, but after switching, I couldn't find the translated content on the updated page. All that I could read was the Google menu with the options for selecting either the translated or original content and for performing another translation. furthermore, the radio button to choose the original content (i.e., to return to the English page) didn't show up in the tab order of the page for some reason. There was an iframe shown but I couldn't access the content (I'm assuming it's supposed to contain translated text).

Problem

Google Translate opens in a framset which is not accessible. In addition the framset can't be closed.

The Google Translate API has been officially deprecated as of May 26, 2011. The API will be shut off completely on December 1, 2011.

Remedy

I think we should look at moving back to the Google Translate Element. At least that allows users to close the tab.

[anormand]

Paul and Anthony set up a test page using the old API and it was send to our expert reviewer.

Expert reviewer's comments

I tried it, with results that were indistinguishable from the earlier version.

In particular, I couldn't even find, let alone read, the translated material, although the user interface controls were accessible. You might have to use an API for the translation service and pull the content directly into your own page instead of using Google's UI.

Selecting the "internal frames" didn't help, and none of the structural navigation commands showed that the translated content was even present. At least I was able to select the language, not that it helped.

Comments

The suggestion of looking for an alternative API is a good one.

There are several other versions available.

Microsoft Translate (aka Bing Translator) performs a similar function to Google Translate, but it isn't accessible either.

There is also a JQuery version of the Google Translate API whcih might be worth looking at: http://www.superawesomejquery.com/plugins/2_jquery-google-translate-plugin/

[anormand]

I undertook a comparison of both the current translate function and the previous translate function using Jaws 10 on Windows XP.

The results were as follows:

Old Translate Function

Internet Explorer 7.0.5730.13 x Can't tab out of language combo-box x Language combo-box auto submits x Content isn't translated x Cannot select another language x Incorrent voice used, e.g. Spanish spoken with English accent o Back button works o Translate bar can be closed

Firefox 5.0 x Can't tab out of language combo-box x Incorrent voice used, e.g. Spanish spoken with English accent x Back button doesn't work o Can tab through trawnslated content o Translate bar can be closed

Current Translate Function v.0.9.5

Internet Explorer 7.0.5730.13 o Can tab out of language combo-box o Can tab through translated content o Back button works x Can't close translate bar

Firefox 5.0 o Can tab out of language combo-box o Can tab through translated content o Back button works x Can't close translate bar

Conclusions

The current translate function, despite several limitations, is clearly better than the previous translate function.

In particular, the form for selecting a language is accessibile and does not auto translate. The translation is also read out using the correct accent.

The use of a translation toolbar introduces an accessibility paradox. On the one hand, providing content in multiple languages increases the number of people who can access the content. On the other hand, Google's translate toolbar contains a number of form elements that are inaccessible to screen reader users.

The translate function is aimed principally at users who have english as a second language. It is not designed for regular staff and student use.

At this stage I believe that UoM has done all that it can at it's end to resolve this problem. I will follow up the outstanding accessibility problems with Google.

In my opinion, the templates are now ready to go live, in terms of accessibility.

Naturally the impact of the translate function on users will have to be reassessed over time and if we receive complaints from users we will have to reopen this issue.