Change link text on Maintenance mode form to 'user login page'

Done. The MR now targets main and the branch is rebased, same two line change as before.

On comment #4, fair point about the interface text standard, so here is some background on why I went this way. I'm blind, and I found this while setting up maintenance mode on my own site with VoiceOver. The checkbox description gets announced with "user loginpage" mashed into one word, because when the accessible description is computed, the link text and the text right after it get joined with no separator. Moving "page" inside the link fixes that, and as a bonus the link text now says where the link actually goes, the user login page, instead of half a phrase.

The quoted style from the standard, 'user login' page, would most likely fix the mashed together announcement too, since the closing quote separates the words. So if the maintainers would rather stay consistent with the standard, I'm completely fine changing the MR to that. I mainly care that screen reader users stop hearing "loginpage". Whichever direction you pick, I'm glad to update the MR, and if the no-quotes version is preferred I can help with a follow up for the standards page. Note for anyone clicking the live preview: it fails because the Tugboat recipe sets COMPOSER_ROOT_VERSION to main-dev, which composer rejects as an invalid version string, so it looks like the preview tooling has not caught up with MRs that target main. Also, if I'm not wrong, this issue might be a Regression. I can’t really recall which version of Drupal I was running but never saw this type of issue before on Drupal.

Update: I retested on three setups against a Drupal 11.4.5 site:

macOS VoiceOver, Safari and Chrome: the description reads correctly, "user login page", three words.

Desktop Chromium's computed accessible description, read straight from the accessibility tree: the space is present, "user login page."

iOS VoiceOver, Safari and Chrome: still announces "user loginpage" as one word at the end of the checkbox description.

So I need to narrow what I wrote earlier: the run-together is not in the desktop browsers' computed description, it is specific to how iOS VoiceOver reads the aria-describedby text across the link boundary. iOS VoiceOver is the most used mobile screen reader, so the announcement problem is real for a lot of people administering sites from a phone, but it is narrower than I first described, and I plan to report the iOS side to Apple separately.

The link purpose half of this issue is unchanged by any of that: the link text says "user login" while the destination is the user login page, and that markup is identical on every supported branch. Moving "page" inside the link addresses the link text, and as a side effect gives iOS VoiceOver a single text run with nothing to join wrongly. If the maintainers prefer the quoted style from the interface text standard instead, that would most likely also fix the iOS announcement, since the closing quote separates the runs either way.

Some real device data that should hopefully help regarding Comment #4.

I run a Drupal 11.4.5 production site, so I applied both candidate wordings to my own maintenance form and tested each with VoiceOver on an actual iPhone.
The MR's wording, with "user login page" fully inside the anchor: the checkbox description reads cleanly, "via the user login page", no run together.
The Interface Text Standards style from #4, "via the 'user login' page" with quotes around the link and "page" outside it: this also reads cleanly on the iPhone. The closing quote sits at the link boundary instead of a space, so nothing gets swallowed. That confirms with a device what I guessed in Comment #7, either wording fixes the announcement problem.
So the announcement is no longer the deciding factor. What remains is exactly the link purpose point oily made in Comment #11, and there the two wordings are not equal. Moving through the page by links alone, the standards style announces the link as just "user login", while the MR wording announces "user login page". Only the second tells you where the link goes when the link text is all you hear, which is how many screen reader users navigate. It reads more complete for sighted users in context too.
On the standard itself, my reading is that the single quote rule is for referring to pages by their title, as in the 'Search settings' example, where 'Search settings' is the page's actual name. "User login page" is a descriptive phrase, not a title, the login page's title is "Log in". So I do not think putting the full phrase inside the anchor conflicts with the standard's intent. I've also been thinking, looking at the standard page, one option is adding an accessibility note to it: when the page reference is itself a link, the whole phrase belongs inside the link. And if consistency wins and the quoted style is preferred here, I can live with that, it fixes the announcement, though it leaves the link purpose half unaddressed.