ARIA and accessibility improvements in entity (content) translation settings page

Created on 30 November 2012, almost 12 years ago
Updated 11 July 2023, over 1 year ago

Follow up for #1810386: Create workflow to setup multilingual for entity types, bundles and fields

Problem/Motivation

#1810386-71: Create workflow to setup multilingual for entity types, bundles and fields Started an accessibility review.
#1810386-124: Create workflow to setup multilingual for entity types, bundles and fields Addressed request for label for=
This is a follow-up for ARIA and other accessibility focused investigation and careful review. This issue is for remaining accessibility work on the translation settings page. Note that some of the other usability follow-ups to that issue might also improve general accessibility and those general improvements dont need to be addressed here.

Proposed resolution

#1810386-114: Create workflow to setup multilingual for entity types, bundles and fields

Remaining tasks

  • Read ARIA docs carefully.
  • Add comments listing specific changes to make
  • Implement some, create patches
  • Get more reviews
  • Rinse. Repeat.

Find other things todo

  • Get more types of accessibility reviews, screen reader, having someone just try using the page without a mouse.
  • Get the point of view of some of the experienced accessibility reviewers in the community
  • http://drupal.org/node/1853532 doc page: Contributor task: Manually do Accessibility testing of a patch for a Drupal issue could be helpful for people wanting to jump in

User interface changes

(new or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text)

API changes

No api changes expected.

📌 Task
Status

Closed: outdated

Version

9.5

Component
Content translation 

Last updated 3 days ago

No maintainer
Created by

🇺🇸United States yesct

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

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Accessibility

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

  • Needs manual testing

    The change/bugfix cannot be fully demonstrated by automated testing, and thus requires manual testing in a variety of environments.

  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

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.

Production build 0.71.5 2024