Steps to reproduce the issue

Audit finding

The Filter Options button expands a set of filter controls elsewhere on the page.

The button does not indicate that it expands content. Its expanded or collapsed state is not conveyed programmatically.

The only indication that the filters are open is the presence of the filter options elsewhere on the page.

The report notes that this is particularly problematic for people using zoom, who may believe nothing happened after activating the button. Screen-reader users may also have difficulty finding the filter controls because they are not near the button.

The report recommends adding aria-expanded to the button, showing the options directly after it, and communicating the expanded state visually, for example by changing its icon.

User impact

Keyboard and screen-reader users may activate Filter Options without knowing whether it opened anything.

Because focus does not move to the filter controls, users may need to search the page to find them. At high zoom, the controls may be outside the visible area entirely.

Screen-reader users may not understand that the button controls a disclosure, and may not know how to return to it after using the filters.

This makes filtering articles slower and can make the feature appear broken.

Remediation plan

Make the filter disclosure state and focus movement predictable

• Add aria-expanded to the Filter Options button and keep it synchronised with the filter area's visibility
• Associate the button with the filter area it controls where appropriate
• Move keyboard focus to the first filter control when the filters open, or otherwise provide a predictable and announced way to reach them
• Return focus to the Filter Options button when the filters are closed
• Show the filter controls directly after the button where the layout allows
• Communicate the expanded state visually as well as programmatically, for example with a changed icon or clear open/closed treatment
• Preserve a visible focus indicator on the button and filter controls
• Ensure the filter controls remain keyboard operable
• Ensure the behaviour is consistent across list views that use the shared filter component
• Do not rely on the mere presence of filter controls elsewhere on the page to communicate the state

Preconditions

• Use Joomla 6.2 with the Atum administrator template
• Sign in with an account permitted to view the Articles list
• Use a test installation with articles and filter options available
• Record the exact Joomla build, browser name and version, operating system, viewport dimensions, and browser zoom
• Record the screen reader and browser combination if testing announcements
• Start at 100% browser zoom
• Record the active appearance and any template overrides or custom CSS
• Do not change production filters during verification

Steps to reproduce

1. Open the Joomla administrator interface at the site's base URL followed by /administrator/
2. Open Content → Articles
   • Alternatively, navigate to /administrator/index.php?option=com_content&view=articles on the same installation
3. Locate the Filter Options button
4. Inspect the button using Developer Tools
5. Record its element type, accessible name, aria-expanded value, and aria-controls value if present
6. Move keyboard focus to the button
7. Activate it with Enter or Space
8. Record whether the filter controls become visible
9. Record whether aria-expanded changes
10. Record where keyboard focus moves after activation
11. Check whether focus reaches the filter controls
12. Scroll or zoom to 200% and repeat the activation
13. Record whether the filter controls are visible or discoverable after activation
14. Close the filters
15. Record whether aria-expanded changes and where focus moves
16. Capture the closed state, expanded state, focus position, and relevant DOM attributes

Screen-reader verification

1. Use a screen reader with the browser combination being tested
2. Navigate to the Filter Options button
3. Record its announced name, role, and expanded state
4. Activate the button
5. Record whether the screen reader announces the state change
6. Record whether focus moves to the filter controls
7. Navigate through the filter controls and record their order
8. Close the filters and record the announced state and focus location
9. Repeat with at least one additional screen reader if available
10. Record the screen-reader name, version, browser, and operating system

Verification after remediation

1. Open Content → Articles
2. Confirm that Filter Options exposes aria-expanded="false" when closed
3. Activate it and confirm that aria-expanded="true"
4. Confirm that focus moves predictably to the filter controls
5. Confirm that the visual state clearly indicates that the filters are open
6. Close the filters and confirm that focus returns to the button
7. Repeat at 200% browser zoom
8. Confirm that the filter controls remain keyboard operable and visibly focused
9. Record the final attributes, focus behaviour, and visual state

Version

6.2

Expected result

The Filter Options button programmatically conveys whether the filter area is expanded or collapsed.

When the filters open, keyboard focus moves predictably to the filter controls, or another accessible and predictable mechanism guides users to them.

When the filters close, focus returns predictably to the Filter Options button.

The expanded state is also communicated visually.

Actual result

The Filter Options button does not indicate that it expands content and does not convey its expanded or collapsed state.

The filter controls do not receive keyboard focus when they open.

The only indication that the filters are open is their presence elsewhere on the page.

The current Joomla 6.2 build needs to be checked to establish whether the issue persists.

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?

VoiceOver, JAWS, NVDA

Additional Comments

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

Development is the responsibility tag in the original report.

The report's suggestion to place the filter controls directly after the button is one approach. Moving focus to the controls is another. The chosen approach must provide a predictable way for keyboard and screen-reader users to reach the filters.

This issue concerns the filter disclosure and focus behaviour. It does not require changing which filters are available or how filtering results are calculated.

MS2b is proposed for the shared list-filter disclosure component, with MS3b covering the documented Articles-list integration.