Steps to reproduce the issue

Audit finding

The document titles do not distinguish the specific tasks in two audited workflows.

In frontend module editing, the page title is “Module Settings” regardless of which module is being edited. It identifies the general activity but not the selected module.

In the Joomla installation wizard, the same title is used across the installation steps. The title does not identify the current step, such as database configuration.

This finding concerns the document title displayed by the browser, not only the visible heading within the page.

User impact

A screen reader user checking the page title cannot identify which module-editing form is open. If several editing pages are open, identical titles make it harder to select the correct browser tab and confirm the editing context.

During installation, an unchanged title does not help the user recognize that they have moved to a different step. They must inspect the page content again to determine which task is now active.

These generic titles can also make orientation harder for people who rely on clear task names to keep track of a multi-step process.

Remediation plan

Generate document titles that identify the specific module-editing task or current installation step

• For frontend module editing, include the selected module's title together with the editing task
  • For example, use “Main Menu — Module Settings” when editing a module titled “Main Menu”
  • Derive the module name from the module being edited rather than a fixed example
• For installation, include the current step's descriptive name and the installation context
  • For example, use “Database Configuration — Install Joomla” for the corresponding step
  • Reuse the current step's heading or fieldset legend where appropriate so that the title and visible task remain consistent
• Update the document title when the active installation step changes, including transitions that do not load a new document
• Preserve appropriate site-name branding without replacing or obscuring the task-specific information
• Use translatable title strings and handle module titles safely through the existing title-generation APIs
• Verify the resulting document title, not just the visible page heading
• Test screen reader behaviour separately if automatic announcement of an in-page step change is also required
  • Do not assume that changing the document title alone guarantees an announcement in every screen reader

Preconditions — frontend module editing

• Use Joomla 6.2 with the Cassiopeia frontend template
• Sign in with an account permitted to edit frontend modules
• Ensure that frontend module editing is enabled and available for the test account
• Make at least two modules with different titles available for frontend editing
• Record the module titles, their frontend page URLs, and the editing actions used
• Record the browser name and version and the operating system
• Record the exact build or commit and whether it includes an existing title-related fix
• Do not save unintended changes to the modules

Steps to reproduce — frontend module-editing titles

1. Open a frontend page containing the first test module
2. Sign in with the permitted account if necessary
3. Activate that module's frontend editing action
4. Confirm which module is being edited
   • Record its title from the module settings or other identifying information
5. Read the browser tab or window title
   • If the title is truncated in the browser interface, inspect the document's <title> element using Developer Tools
6. Record the complete document title
7. Check whether it identifies the selected module as well as the editing task
8. Close the editing form without saving changes
9. Open a frontend page containing the second test module
10. Activate its frontend editing action
11. Record the second module's title and the complete document title
12. Compare the two document titles
    • Check whether both use only “Module Settings” or another generic title despite referring to different modules
    • If a site name is included, check whether the task-specific part still distinguishes the modules
13. Close the form without saving changes

Preconditions — installation wizard

• Use a separate disposable Joomla 6.2 installation environment
• Do not run this test against an existing production installation
• Have the test database details and other required setup information available
• Record the exact installation build, browser, and operating system
• Use test credentials and avoid including passwords or database secrets in screenshots

Steps to reproduce — installation-step titles

1. Open the installation wizard for the disposable Joomla installation
2. Record the visible heading or fieldset legend identifying the first step
3. Read and record the complete document title
   • Inspect the <title> element if the browser tab truncates it
4. Enter the required test information and use the wizard's continuation control to advance
5. Wait for the next step to become active
6. Record its visible heading or fieldset legend
7. Record the complete document title again
8. Repeat for the remaining available installation steps
   • Include the database-configuration step if present in the tested flow
   • Do not assume that the number or order of steps matches a different Joomla build
9. Compare each title with the active step's purpose
10. Record whether the same generic title remains across distinct steps
11. If a step changes without a full-page load, check whether the document title updates after that transition
12. Stop when sufficient evidence has been collected
    • Complete the disposable installation only if needed for the test

Supplementary screen reader test

1. Enable a screen reader and record the screen reader and browser combination
2. Open a frontend module-editing form
3. Use the screen reader's command for reading the current window or page title
4. Check whether the title identifies the module being edited
5. Repeat for another module
6. In the disposable installation environment, repeat the title check at successive installation steps
7. Record title accuracy separately from whether a step transition is announced automatically

Version

6.2

Expected result

A frontend module-editing page title identifies the selected module and the editing task.

Each installation-step title identifies the current task within the Joomla installation process.

The document title remains consistent with the active page or step, including after transitions that occur without a full-page load.

Actual result

The audit reports that frontend module-editing pages use “Module Settings” regardless of the selected module.

It also reports that the installation steps share the same title instead of identifying the current step.

The titles therefore do not distinguish the module-specific editing context or the individual installation tasks.

What device were you using? (eg, phone, laptop)

Desktop web

What web browser were you using? (eg, Chrome, Safari)

Chrome, Firefox, Edge, Safari

Assistive Technology?

No response

Additional Comments

The browser entries above are carried forward from the original issue and do not represent a new verification of every browser against Joomla 6.2.

The original issue does not identify an assistive-technology test configuration. The supplementary screen reader steps are proposed verification, not a claim that those tests were already performed.

The original report contains no screenshot for this finding.

The issue links PR #48505, titled “[6.3] fix module unclear titles”, which is marked as merged, and PR #48489, which is marked as closed. Record whether the tested build contains either change rather than assuming that a merged fix is present in Joomla 6.2 or resolves both reported workflows.

MS3a is proposed for the frontend module-editing integration. The supplied milestone summaries do not explicitly allocate installation-wizard title changes, so that assignment requires confirmation.

This issue targets the two documented workflows rather than requiring every Joomla page to have a globally unique title.