User tests: Successful: Unsuccessful:
Updated language for How to Create Articles guided tour.
Pull Request for Issue # .
Updated the step descriptions for How to Create Articles to provide more information for new users.
Using a Joomla 4.3.x instance, click Take a Tour > How to Create Articles?
Step 1: How to create articles?
Step 2:Select the 'New' Button
Step 3: Add a title for the article
Step 13: Select 'Save and Close'
Step 1: How to create articles?
Step 3: Add a title for the article
Step 4: Generate or Add Article Alias
Step 7: Select Article Category
Step 9: Set Article Access Level
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
Category | ⇒ | Administration Language & Strings |
Status | New | ⇒ | Pending |
Thanks for your feedback Brian. This is not intended for 4.3.2 but for 5.0. Will review with Olivier and update.
This is not intended for 4.3.2 but for 5.0.
then you should make the PR against the correct branch and add [5.0] to the title to make it clearer and help reviewers
Title |
|
Labels |
Added:
Language Change
PR-5.0-dev
|
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-05-15 21:41:20 |
Closed_By | ⇒ | sdwjoomla | |
Labels |
Added:
PR-4.3-dev
|
Sorry but all of the markup being used here fails basic accessibility and usability.
Whenever you have used a class of fw-bold or fst-italic you have done so to emphasise the text. Because this has been done with a VISUAL class the emphasis is completely ignored by a screen reader and other assistive technology.
That is why we have semantic markup and you must use
<em>
and<strong>
as they convey the additional emphasis to assistive technology and visually.Secondly for accessibility purposes some of the language changes are not good. Any time that you refer to a previous step this causes cognitive issues so please make sure that the text for each step makes complete sense without having to remember what was in a previous step. see COM_GUIDEDTOURS_TOUR_ARTICLES_STEP_VERSIONNOTE_DESCRIPTION as an example
When updating this pr to use semantic markup you will also see multiple grammar errors so could you please fix those as well.
Finally I am not sure that this can go in a patch release. Please see the policy on changing strings