Problem/Motivation

As an inclusive community, we are committed to making sure that Drupal is an accessible tool for building websites that can also be accessed by people with disabilities.
-- https://www.drupal.org/about/features/accessibility

The Webform module needs to build and provide accessible forms. Accessibility should become part of the Webform modules ongoing iterative process.

Proposed resolution

Document and setup the tools needed to make it easy to review the Webform module's accessibility.

Notes

  • Creating a dedicated Webform Examples Accessibility module will hopefully raise more awareness about webform accessibility and make it easier to remediate issues.
  • Immediate focus is to address accessibility issue related to the published webforms and management tools.

Remaining tasks

Questions

  • How should we track elements with accessibility issues? via the examples, documentation and/or tickets

Comments

jrockowitz created an issue. See original summary.

mgifford’s picture

Do you have an existing demo? Just having a space where people can look at some of the common patterns and evaluate it would be quite useful.

Often it is easy to just look at a public demo and run some basic tests with automated tools like the WAVE Toolbar to find problems. With WAVE & keyboard only testing you can usually find the low hanging fruit. It's not perfect, but you can get color contrast, semantic forms, and basic navigation set up with that.

Other issues might be more complicated, but it would be useful to see the functionality to know.

jrockowitz’s picture

The webform examples accessibility module provides demo forms with tools to enable/disable certain accessiblity features, including toggle client-side validation, inline form errors, required validation, etc...

This module with its examples will become part of the core webform module after my presentation at Design4Drupal.

  • jrockowitz committed 6718e18 on 8.x-5.x
    Issue #2979628 by jrockowitz: [meta] Improve Webform Accessibility....
jrockowitz’s picture

Status: Active » Fixed

It is time to close this ticket.

@see #2989232: Release 8.x-5.0-rc17

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.