this issue will fix the accessibility issues from #1952394: Add configuration translation user interface module in core
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.
Comments
Comment #1
Schnitzel CreditAttribution: Schnitzel commentedthe attached patch fixes all these issues:
Comment #3
Schnitzel CreditAttribution: Schnitzel commentedreroll
Comment #4
Schnitzel CreditAttribution: Schnitzel commentedComment #6
Schnitzel CreditAttribution: Schnitzel commented#3: 1999156-config-tranlation_accessibility-3.patch queued for re-testing.
Comment #8
Schnitzel CreditAttribution: Schnitzel commented(facepalm), overwrote $key, interesting that the whole thing actually still worked! :D
Comment #9
Schnitzel CreditAttribution: Schnitzel commentedthis patch depends on #2004194: Add getLanguageWithFallback() to ConfigGroupMapper so it will fail till it's not yet landed
Comment #11
Schnitzel CreditAttribution: Schnitzel commented#9: 1999156-config-tranlation_accessibility-depends-2004194-9.patch queued for re-testing.
Comment #13
Schnitzel CreditAttribution: Schnitzel commented#9: 1999156-config-tranlation_accessibility-depends-2004194-9.patch queued for re-testing.
Comment #15
Schnitzel CreditAttribution: Schnitzel commented#9: 1999156-config-tranlation_accessibility-depends-2004194-9.patch queued for re-testing.
Comment #17
Schnitzel CreditAttribution: Schnitzel commented#9: 1999156-config-tranlation_accessibility-depends-2004194-9.patch queued for re-testing.
Comment #18
Gábor HojtsyI think title should come first before the label definition, eg. "Page Display" vs. "Display Page".
Also, it would be great to look for a 'label' key as well. So what I would do is
Comment #19
Schnitzel CreditAttribution: Schnitzel commentedupdate of the patch, now searching for direct title or label elements before searching for elements which contain these words
Comment #20
Gábor HojtsyI committed this at http://drupalcode.org/project/config_translation.git/commit/8ed56dcc385e... thanks! Only slightly edited.