Thanks @Schnark! Darn it vendor properties…

Do I understand the state correctly, that this should be applied for example to the first checkbox here?

Fixed in I52874694758ebf961117fa85c792f6875e0082ee.

Do we agree that we should treat non-Arabic numeral ordered lists equal to Arabic numeral (all Latin scripts to my knowledge) ones?
If we don't set decimal as default, ordered lists fall back to decimal. Which we should override with better treatment for serving our communities (we do this in other skins already).

Form looks great, works on mobile.

@alexhollender Assigning to you for visibility and sign-off.

The most critical point here from my perspective is to make sure overlay height decrease (if we gonna go for a 48px based header) to normal branded header is well addressed.

From a conversation with @PDrouin-WMF off-Phab:

An ellipsis is a (as in one) typographic character with three dots, … vs ... – depending on the font the three dots might look widely stretched, in any case they are always typographically wrong.

Update 2019-03-19:

Also let's bear in mind that currently there doesn't seem to be any use of 'unTrash' right now… https://codesearch.wmflabs.org/search/?q=%27unTrash%27&i=nope&files=&repos=

Compared to a striked through trash can still an improvement IMO. The use case for this icon is meant to be only actions that follow an icon signified by 'trash', not other functionalities like page restore for example…
The example from the task description on the other hand has too many details: https://www.freeiconspng.com/img/12269

Restore seems like the best possible option here. We've got opposite pairs outside of “Un-” as in “UnTrash” like “collapse” + “expand”.

Latest mock with stop sign inspired icon, added sizing information and error box alternative without strike-through bar.

'notices' https://codesearch.wmflabs.org/search/?q=notices%3A&i=nope&files=&repos= appears to be used in

• ve.init.mw.ArticleTarget.js 1x and
• ve.init.mw.DesktopArticleTarget.test.js 1x (neglible).

Nowhere else…

Contrast/WCAG conformance:

• When boldened and at higher font-size (18+ px) we would conform to level AA.

I do like to have the error set apart from the warning, and notice stronger, but if majority agrees with readability and identification being fine with black on red, then I'm fine too.

• The icon is ok to be set to Yellow50 as long as the text is fulfilling contrast factor. It's not optimal, but acceptable in this combination. If you've got better ideas, pls share.

@Jdforrester-WMF shared on IRC:

Updated with overhaul based on work by @Hanna_Petruschat_WMDE with comments and feedback integrated.

@JoeWalsh Thanks for those insights. What is your preferred way forward (I personally wouldn't rely on that value being unchanged for all future)?

Do you have an URL to share to look at the same output?

Not the biggest fan of centering text in general, but in this case with infoboxes where centered images come directly underneath, it seems acceptable to me to have them centered.

Exciting progress here from @Jdrewniak
A few notes:

• The anchor gets role=button assigned, why not making it a button out of box? That would make it simpler for assistive technology
  • Even if disabled, the code is

<a id="" href="" class="mw-ui-icon mw-ui-icon-element mw-ui-icon-minerva-language-switcher language-selector disabled" role="button" title="Read in another language">Read in another language</a>
which the disabled class alone doesn't provide any useful addition to screen readers. It should carry an aria-disabled or if changed to a button a disabled attribute!

+1 If in doubt, see reasoning on parent tasks. The only remaining concern letting people stop from using the same terminology on mobile like on desktop from my memory was, that “Publish” takes up more space.
Compare German “Speichern” (“Save”) vs “Publizieren” {“Publish”)

There are several that are either in-depth or well-balanced resources, depending on their main audience (designers, developers, PMs & general audience), let's take for example Tooltip page on Material Design:

• Usage
• Placement
• Behavior
• Theming
• Spec
• Implementation

Excellent, thanks @Lucas_Werkmeister_WMDE!

@iamjessklein Here's some feedback on each of them:

@Lydia_Pintscher Due to the path dependency someone still needs to review and merge WikibaseLexeme patch provided at https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/WikibaseLexeme/+/485991/

T215644: Add a frameless design for OOUI's IndexLayout (TabLayout), suitable for use on large, unframed contexts (not dialogs) provides another use case.

Related to T203859: Evaluate IndexLayout (TabLayout) appearance on mobile

Just coming from A11yCampBay, this is a nice resource, basically repeating combobox being the more appropriate role https://gerardkcohen.github.io/periodic-table-of-semantics.html

Patch provided at https://github.com/wikimedia/WikimediaUI-Style-Guide/pull/191

In this specific case I thought putting the whole question in next line seems appropriate. The effort needed to tackle this generally (JS involved, performance cost) doesn't allow a general solution.

@Jdlrobson So how do we address non-Arabic numeral issue then in T217616?