Change the confusing "Screen Options" button text

[cryptex_vinci]

From a new users perspective the label "Screen Options" doesn't make any sense. Seems technical, it doesn't express anything meaningful. From a general perspective by reading a buttons text it should be clear to users what it does. Besides that the text Screen Options is not that common either.

In my opinion, It would be easier and meaningful if it uses one of these :

1. see more
2. more information
3. display more

Google Books Ngram Viewer
how many times these terms has been used (from year 1800 to 2000)

Google Trends

Reference:

1. Design Words With Data ​https://medium.com/dropbox-design/design-words-with-data-fe3c525994e7#.hv4ce0o2q
2. How To Design Words ​https://medium.com/@jsaito/how-to-design-words-63d6965051e9#.tfmbqs2ux

[cryptex_vinci]

Google Ngram Viewer

[cryptex_vinci]

Default Screen options Button

[afercia]

@cryptex_vinci thanks for your report and welcome to Trac! I'm going to remove the accessibility since it's not strictly related to an accessibility issue.

[SergeyBiryukov]

Related: #21583

[lukecavanagh]

@cryptex_vinci

Display More, would make more sense than Screen Options.

[melchoyce]

I'd be up for improving this label, but I think the proposed solutions don't necessarily clarify any better what is in Screen Options.

"See more," "More information," and "Display more" all neglect to tell you what you're seeing more of. See more what? More information about what? Display more what? Whatever label we use should answer that.

Honestly, not sure this is any different from #21583, which is the root problem — Screen Options just aren't very discoverable.

[cryptex_vinci]

It's definitely tricky. Context of "What" a user is seeing depends on the area he/she is browsing. Although Display more info about post/ pages doesn't seem right too. In terms of clarity "Display more info", "Show more info" or any other proposed solution would be better in my opinion than just Screen Options.

[Travel_girl]

What about "Display more setting options" maybe a bit long, but I found it quite clear.

Or should we continue this disscussion in #21583

This pull request updates the terminology across the WordPress admin codebase, replacing "Screen Options" with "Display Options" for consistency and clarity in both user-facing text and internal documentation. The changes affect JavaScript, PHP, and CSS files, as well as help text, comments, accessibility announcements, and privacy policy documentation.

User-facing text and accessibility updates:

• All references to "Screen Options" in UI strings, help text, and accessibility announcements have been changed to "Display Options" throughout the admin dashboard, post/page editors, and related screens. [diffhunk://#diff-b9e9194f24d2a3548ae0b16b6bde5e0c7756a2b7668bed4d1040093e00550bf6L431-R431 [1]] [diffhunk://#diff-e46ecfbb842ed565f82a5773316b8c5420c2bd08ac6199ceb9212be762115feaL474-R474 [2]] [diffhunk://#diff-40c1cf7194f39543c4b383a20737941505065dd4bef4b5b02981a604bd3a1abaL38-R38 [3]] [diffhunk://#diff-3c1da94f2001db1493a153468f64e88c0b7a92e3b748bbefae0d4e62e889139dL63-R63 [4]] [diffhunk://#diff-ad14d4a1e0e27d08d8eba47d7afca5f5d05a0bc3057c09c9bf223584c2a32b5cL275-R275 [5]] [diffhunk://#diff-ad14d4a1e0e27d08d8eba47d7afca5f5d05a0bc3057c09c9bf223584c2a32b5cL290-R290 [6]] [diffhunk://#diff-360dda58d91673fdf7705609269a9de163a827aa3a3b43e2d560cad57bacede2L69-R69 [7]] [diffhunk://#diff-e16824dc0b95c8da5a7b198cac7bf89280d06180cefaf6da296ccf211671af77L294-R294 [8]] [diffhunk://#diff-039bdc6683a2811a98f11ac7d8f235b8e6c5c0d0b6d45f708a8720d5d9bf3748L264-R266 [9]]

Documentation and code comments:

• Inline comments, function descriptions, and documentation blocks referencing "Screen Options" have been updated to "Display Options" in both JavaScript and PHP files, including class properties and method descriptions. [diffhunk://#diff-b9e9194f24d2a3548ae0b16b6bde5e0c7756a2b7668bed4d1040093e00550bf6L389-R389 [1]] [diffhunk://#diff-b9e9194f24d2a3548ae0b16b6bde5e0c7756a2b7668bed4d1040093e00550bf6L476-R476 [2]] [diffhunk://#diff-b9e9194f24d2a3548ae0b16b6bde5e0c7756a2b7668bed4d1040093e00550bf6L568-R568 [3]] [diffhunk://#diff-e46ecfbb842ed565f82a5773316b8c5420c2bd08ac6199ceb9212be762115feaL295-R295 [4]] [diffhunk://#diff-acd1e34adc28310cb1063141ffecc6e91172e4de2e4667ec48e2bf636aef45a4L797-R797 [5]] [diffhunk://#diff-cb27cb72b5160a4ed56d62d3a7d3a03c7f1dfd6ac7a6554e8eca5d1bd3007851L159-R159 [6]] [diffhunk://#diff-cb27cb72b5160a4ed56d62d3a7d3a03c7f1dfd6ac7a6554e8eca5d1bd3007851L184-R184 [7]] [diffhunk://#diff-cb27cb72b5160a4ed56d62d3a7d3a03c7f1dfd6ac7a6554e8eca5d1bd3007851L498-R498 [8]] [diffhunk://#diff-cb27cb72b5160a4ed56d62d3a7d3a03c7f1dfd6ac7a6554e8eca5d1bd3007851L705-R705 [9]] [diffhunk://#diff-cb27cb72b5160a4ed56d62d3a7d3a03c7f1dfd6ac7a6554e8eca5d1bd3007851L958-R958 [10]]

CSS class and section comments:

• CSS comments and section headers have been updated to reflect the new terminology, ensuring style definitions and documentation are consistent with the new wording. [diffhunk://#diff-9cd7cfe9f840fdcd45dcbe3503da77ac7490c7574209a4c7cf01a885e6ae0f00L1776-R1776 [1]] [diffhunk://#diff-9cd7cfe9f840fdcd45dcbe3503da77ac7490c7574209a4c7cf01a885e6ae0f00L1796-R1796 [2]] [diffhunk://#diff-9cd7cfe9f840fdcd45dcbe3503da77ac7490c7574209a4c7cf01a885e6ae0f00L1868-R1868 [3]] [diffhunk://#diff-aaa32ce64546abbfab8a6c15e365e9d989d500e08f2c06cdab2a60b63ff6246dL240-R240 [4]] [diffhunk://#diff-fd27ee048c40fddec930c410d341428d36aa6546c1a7014d2ff0feffeb98002fL1991-R1991 [5]] [diffhunk://#diff-fd27ee048c40fddec930c410d341428d36aa6546c1a7014d2ff0feffeb98002fL2242-R2242 [6]]

Privacy policy and cookies:

• The privacy policy text now refers to "display options cookies" instead of "screen options cookies" to match the new terminology.

These changes ensure a unified experience and reduce confusion for users and developers by standardizing the term "Display Options" throughout the WordPress admin interface and codebase.

Trac ticket: https://core.trac.wordpress.org/ticket/39852