this issue will fix the accessibility issues from
First off, it is hard to distinguish the "source" information from the form field where to type its translation. This issue could be solved by adding the language to the label of the information that you are translating.
So, for instance, to translate the site name you could have something like:
Site name (Source language): site_name
Site name (Language_that_you_are_translating_the_information_into): form field to translate it
If this additional information should not be shown to sighted users, it can be wrapped in a span/div element which the "element-invisible" class can be assigned to, so that the information is available for screen reader users, but not for sighted ones.
When you try to translate the displays of a view, you get lots of buttons labelled "display settings". You can understand what display a button refers to only after clicking it. This is not good for accessibility and (maybe( for usability too. And I was also wondering: does it make sense, from a usability point of view, to have the display settings in collapsible details elements?
And finally, I think that the Source text that you are translating into another language should be wrapped in a div/span element, which "lang" attribute should be set to the appropriate value according to the source language. It could be also appropriate to set the "lang" attribute of the form element to translate an element (e.g. the site name) to the appropriate value according to the language that the text is going to be translated into.
|PASSED: [[SimpleTest]]: [MySQL] 238 pass(es).|
|PASSED: [[SimpleTest]]: [MySQL] 240 pass(es).|
|PASSED: [[SimpleTest]]: [MySQL] 242 pass(es).|
|FAILED: [[SimpleTest]]: [MySQL] 234 pass(es), 16 fail(s), and 3 exception(s).|
|FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1999156-config-tranlation_accessibility-1.patch. Unable to apply patch. See the log in the details link for more information.|