Contrib.social

Section 508 Issue - Textarea field missing label

Open on Drupal.org →
Created on 13 February 2024, 9 months ago
Updated 14 February 2024, 9 months ago

Problem/Motivation

We have a gallery that loads images and the page fails the accessibility test. The accessibility tool finds element containing no label element. The textarea element is being inject dynamically and then later removed by Juicebox JS. This JS file is loaded dynamically which we do not have control over it. We need a solution to turn off using this textarea or add label to this element to avoid Section 508 issue.

Steps to reproduce

Run the accessibility tool to scan for Section 508 issues on the page containing image gallery using juicebox.

Note: We are using siteimprove to test for accessibility

Proposed resolution

Add a label element to textarea field.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Postponed

Component

Code

Created by

🇺🇸United States JaswinderSingh

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @JaswinderSingh
  • Status changed to Postponed 9 months ago
  • Comment 9 months ago →
    🇺🇸United States fkelly

    4.0.x-dev is the current version of Juicebox. We are trying to get a stable version going forward from that for Drupal 10. I have code working on the latest Drupal 10 which, as of today is 10.2.3. The current Drupal core version is constantly changing, of course. I doubt we will be doing anything with Juicebox 8.x-3.0-alpha2. I certainly won't.

    I went to the siteimprove web site and took the chance to install its extension in my Chrome browser, then looked at my Drupal 10 web site Juicebox Gallery. No real surprise, siteimprove shows accessibility issues. It would almost be a surprise if it didn't because the Javascript code generating the gallery is more than 5 years old. And we (Drupal) have no direct access to the Javascript code.

    I am reducing the priority to Normal and the status to postponed. If there is someone out there who wants to work on this, most probably for a release focused on Drupal 10 and forward, post here. Granting the importance of accessibility, unless someone knows how we can address this it is not likely to be dealt with. Sorry.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024