This is not good for accessibility.
The similar OOUI search widget just keeps the text widget outline:
which also works in monobook/apex
Esanders | |
Oct 4 2017, 2:29 PM |
F11958706: Screen Shot 2017-12-20 at 1.11.24 PM.png | |
Dec 20 2017, 9:13 PM |
F11958702: Screen Shot 2017-12-20 at 1.12.22 PM.png | |
Dec 20 2017, 9:13 PM |
F10465819: Screen Shot 2017-10-27 at 4.59.52 PM.png | |
Oct 27 2017, 11:51 AM |
F10015083: Screen Shot 2017-10-05 at 12.37.57.png | |
Oct 5 2017, 10:40 AM |
F10014346: Screen Shot 2017-10-05 at 11.58.12.png | |
Oct 5 2017, 10:40 AM |
F10014868: cx-new-dialog-search-initial copy.png | |
Oct 5 2017, 10:40 AM |
F9999699: image.png | |
Oct 4 2017, 2:33 PM |
F9999715: image.png | |
Oct 4 2017, 2:33 PM |
This is not good for accessibility.
The similar OOUI search widget just keeps the text widget outline:
which also works in monobook/apex
The search bar is presented as a compound input element with some controls inside (in addition to the icon it has a language selector). In this case I think it makse sense to have the blue outline around the whole border as it happens in wikipedia.org or with the Flow input area:
So in the case of Content Translation it should look closer to this:
Regarding the red error outine I think it should not be shown, I created a separate ticket about it (T177470).
Change 381246 had a related patch set uploaded (by Petar.petkovic; owner: Petar.petkovic):
[mediawiki/extensions/ContentTranslation@master] Embed New translation search results
Change 381246 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] Embed New translation search results
Since the above patch there is now a 1px inset, although that should be 2px (and transitioned). Also if I tab out of the input I still see the inner outline of the input widget.
From a technical perspective, I think it will be much easier to increase the padding on the TextInputWidget, and absolutely position the language selector over it, as currently we are trying to override then recreate a lot of upstream styles. This is basically how the www.wikipedia.org portal version works. All the border states will then work automatically, as will the apex/monobook version.
Change 383540 had a related patch set uploaded (by Esanders; owner: Esanders):
[mediawiki/extensions/ContentTranslation@master] Use input padding and absolute positioning on page selector
Change 383540 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] Move language filter and close buttons to input's 'label' area