I18N: Mark screen reader strings as such with translator comments.

This aims to provide better context for translators and make it easier to determine that some strings contain hidden accessibility text and are not displayed in the UI.

Props kebbet, mercime, pavelevap, ocean90, swissspidy, Chouby, jipmoors, afercia, desrosj, costdev, audrasjb, SergeyBiryukov.
Fixes #29748.

git-svn-id: https://develop.svn.wordpress.org/trunk@55276 602fd350-edb4-49c9-b593-d223f7449a82
This commit is contained in:
Sergey Biryukov
2023-02-07 17:08:26 +00:00
parent 86dc3ffe0b
commit 6d7430cfe1
132 changed files with 1558 additions and 328 deletions
+9 -1
View File
@@ -182,7 +182,15 @@ function display_setup_form( $error = null ) {
<th scope="row"><?php has_action( 'blog_privacy_selector' ) ? _e( 'Site visibility' ) : _e( 'Search engine visibility' ); ?></th>
<td>
<fieldset>
<legend class="screen-reader-text"><span><?php has_action( 'blog_privacy_selector' ) ? _e( 'Site visibility' ) : _e( 'Search engine visibility' ); ?> </span></legend>
<legend class="screen-reader-text"><span>
<?php
has_action( 'blog_privacy_selector' )
/* translators: Hidden accessibility text. */
? _e( 'Site visibility' )
/* translators: Hidden accessibility text. */
: _e( 'Search engine visibility' );
?>
</span></legend>
<?php
if ( has_action( 'blog_privacy_selector' ) ) {
?>