Hello, with all of the accessibility enhancements that have gone into Drupal core, I am asking for module maintainers to sign up for the #D7AX pledge. We are asking for module maintainers to pledge to make their modules as accessible as it can be. We're not asking that you guarantee that your module is 100% accessible, however this pledge will assure folks that maintainers are aware of the importance of accessibility and if individuals submit an accessibility issue it will be taken seriously.

To ask more about accessibility within the Drupal context, please feel free to join http://groups.drupal.org/accessibility and post your questions or concerns. Modules which have signed up can be found automatically, but are also available here. By simply adding #D7AX to your description page of your module we can keep track of your support for this initiative.

Comments

Bèr Kessels’s picture

Status: Active » Postponed (maintainer needs more info)

Please add actual, atomic actions that we can perform to make the module more accessible. AFAIK there are no issues with AX to be solved, but you seem better informed, so open up feature requests about how we can fix the AX.

mgifford’s picture

The single atomic action is to put #D7AX on your description page to state that your module will work on accessibility issues when they are brought up. It's a pledge like #D7CX, but without the fixed time frame.

I don't know of any accessibility issues, but running your pages through a validator like http://wave.webaim.org can go a long way to resolving problems that there might be.

Bèr Kessels’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

"Won't fixing". Not that I won't work on UX, on contrary. But without actual patches or proposals there is nothing to pledge for. Will decide on a per-issue base.

mgifford’s picture

Well, you can make it as specific as you want. You could well pledge to ensure that Tagadelic is WCAG 2.0 AA compliant. It's very tangible. Lots of nice ways to evaluate that. Fits in nicely with goals for D7. Really, it's just an extension of basic xHTML validation, which is pretty much assumed.

I'm not sure what issues there are with this module. i haven't tested it. However, simply agreeing to run it through an auto tester to evaluate easily understood problems is another approach. It's usually pretty painless too. The WebAim Toolbar even allows you to review the admin side easily with Firefox.

Waiting for proposals & patches is fine. I know how much of an effort it takes to maintain modules at the best of times. The pledge is just a way to see that our community and the sites that they build becomes more inclusive.