As additional information, text-shadow: 0 1px rgba( 0, 0, 0, 0.1 ) is also still featured on primary buttons in mediawiki.UI (for example on the login screen).

no text shadow. i think we can remove the primary button text-shadow too.. it was leftovers from the 3d button era.

No shadow.

I want to add one small note, we could have a significant higher contrast with relatively little visual impact with the alternate options (I just added another one to the CodePen).

I think no shadow is fine, particularly since color contrast is not a requirement for disabled elements, per WCAG (my emphasis below):

Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.

I agree on keeping it simple and avoid the shadows (and introducing potential inconsistency with the shadow-less icons that can appear next to them). We can reconsider if we find issues while testing with users.

no shadow.

We have a clear majority on the disabled buttons case.

I have to open this up one more time as text-shadows are currently also used on disabled input elements like the “TextInputWidget (disabled)”‎ in OOjs UI demos, which are a different beast. Their color contrast is not level AA compliant (3.82:1) and gains from use of white text-shadow.

For same reasons as previously, I think we can simplify to no text-shadows here as well.

In T148000#2731158, @RHo wrote:

For same reasons as previously, I think we can simplify to no text-shadows here as well.

Tagging Codex Steering Committee as Codex Steering Committee superseded Design-System-Team in 07/2025 and as this open lingering Design-System-Team task has no other active codebase- or team-type project tags and otherwise would not show up on any active workboards otherwise