Accessibility button in the Welcome screen still needs its own string

The Bug:

This is a clone of MC-261119.

The Accessibility settings button on the Welcome screen uses the same string as the Accessibility settings button in the Options menu (options.accessibility), which causes issues in some languages where the text doesn't fit due to the icon.

To make it extra clear (considering the misunderstanding in MC-261119):
The button shown in Welcome screen.png and the button shown in Options menu.png both use the string options.accessibility. The request is to make these two buttons have separate strings, for example one strings options.accessibility and the another onboarding.accessibility.

Observed Behavior:

The current string used for the Accessibility settings button on the Welcome screen is the same as for the Accessibility settings button in the Options menu.

Expected Behavior:

To ensure the Accessibility settings button on the new Welcome screen fits properly in all languages, a separate string should be added. This would align with the approach taken for other settings, where separate strings are used for different elements (for example options.sounds and options.sounds.title).

Note:

The attached examples illustrate this need for a separate string. The current behavior can make it difficult for users with accessibility needs to read and access the button. Therefore, creating a separate string is important to ensure that the feature is accessibility-friendly.