Accessible Helper Module Documentation

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

Use Cases: How is the Accessible Helper module useful or intended to be useful?

These lists should translate to feature requests in the issue queue if they are not already part of the functionality

Accessible Help module

Accessible Fix module

Accessible API module

Developer Questions

Is there a procedure I can use to find modules that I can try to fix?

Not formally, but try these approaches:

Is the goal for individual fixes to eventually get them committed to the module itself?

Yes. The goal is to get the modules themselves fixed. In other words, ideally the "fix" functionality of this module would not be needed at all.

On the other hand, the architecture of this module is such that core and contributed modules are treated the same. For example, this module’s fixes to the Block module are alongside its fixes to various contributed modules. These fixes are more likely to appear in the next version of Drupal.

What is the development cycle for the accessible_fix component of this module?

When a project is in its alpha or beta stage, it’s best to submit a patch to the project itself. By following that approach, you will accomplish much more.

But when a project has reached the release candidate or release phase, this module provides a feasible alternative to having to wait until the next development cycle begins before making the benefits of your patch available.

What is the development cycle for the accessible_api component of this module?

This module follows the standard cycle: alpha, beta, release candidate, release.