Skip to content

bug: Buttons do not announce state changes for screen reader users #395

@optimatrix0

Description

@optimatrix0

Bug description

On the app’s home screen, there is a new search button. As a screen reader user who frequently visits this repository, I initially assumed it would open the keyboard when activated. However, tapping the button multiple times did not trigger the keyboard.

After navigating further through the interface, I realized that this button actually toggles the visibility of the search bar instead of directly focusing it. Because this behavior is not announced by the screen reader, it creates confusion and makes the feature difficult to understand.

This appears to be a missing accessibility implementation: the button does not expose its state (expanded/collapsed or visible/hidden) through proper accessibility attributes (e.g., state description or similar).

A similar issue occurs in another component: the version selection toggle (for example, when selecting different versions in a list like YouTube variants). When navigating with a screen reader, there is no feedback indicating which option is currently selected. This makes it hard to know the current state after interacting with the control.

Version of Morphe (Manager) and the app you are patching

1.14.0dev.4

Morphe logs

N/a

Acknowledgements

  • I have checked all open and closed bug reports and this is not a duplicate.
  • I have chosen an appropriate title.
  • All requested information has been provided properly.
  • The bug only affects using Morphe (Manager)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions