A11y: Send the status message via drupal.announce

Created on 26 January 2022, about 3 years ago
Updated 24 January 2025, 11 days ago

Problem/Motivation

A screenreader user does not know what happens when the link/flag is clicked.

Steps to reproduce

Create a flag with ajax link and ask a screenreader user what the screenspeacker does after clicking the flag.

Proposed resolution

* Send the message via Drupal.announce. See https://www.drupal.org/docs/drupal-apis/javascript-api/accessibility-too... β†’

Found by https://www.drupal.org/u/westphaldenn β†’

πŸ› Bug report
Status

Needs review

Version

4.0

Component

Flag core

Created by

πŸ‡©πŸ‡ͺGermany tobiasb Berlin

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • @tobiasb opened merge request.
  • πŸ‡©πŸ‡ͺGermany tobiasb Berlin
  • πŸ‡ΊπŸ‡ΈUnited States tr Cascadia

    Is there a difference between the MR and the patch? I don't know what to review here. Patches should be hidden IMO because they can't be tested.

    I'm in favor of doing this, but there really needs to be a test for this feature. There are lots of FunctionalJavascript tests in this module that you can use as an example.

  • πŸ‡©πŸ‡ͺGermany tobiasb Berlin
  • πŸ‡ΊπŸ‡ΈUnited States tr Cascadia

    You can still use the patch that way if it's hidden. And hiding it will make it clear what needs to be reviewed and committed. The patch in this case seems to be just secondary and only so that a specific set of changes can be loaded by composer in another project.

    Regardless, I don't see anything wrong with the MR. It works, but it still needs tests.

Production build 0.71.5 2024