Hi All,
I am trying to come up with a listing of Drupal 7 tasks by end users than we can test for accessibility. I have included some tasks below to get the ball rolling, feel free to add your tasks. I'm not sure if this was done already, but the plan is to come up with some tasks, and then test them against actual users with disabilities and see what improvements can be made.
The tasks are:
- Creating a user account
- Requesting a new password
- Changing your password
- Posting a comment
- Editing an existing page/article (editing the main title and description and important options such as Published)
- Creating a new page/article (maybe a simple story to start with and then we can expand to include the common cck fields)
- Creating a menu link
- Ordering/re-ordering a menu link
- Rearranging blocks
- Navigating the administrative interface in the Overlay
- Creating a role and setting permissions
- Assigning an additional role to a user account
- Tagging a node with the autocomplete UI component
- [add your common tasks here]
Note: This type of process has already been set up a few times by Usability folks. I don't see why this should be any different for people with physical & cognitive/learning disabilities. I added this to the usability folks as well.
** Response: We may wish to test specific UIs with users of specific types of assistive technology to see if the UIs cause a greater barrier for these users than for a user who does not rely on assistive technology.
Test Environment:
- Drupal 7 core using the default install profile. Some core modules would be enabled, while many others would not.
- The theme would be Bartik and Seven as the admin theme.
- Overlay would start on by default.
- Drupal 7 would already be installed. (Later we could test the installation process; that is 2nd priority).
Comments
Test plan
Have a look at http://drupal.org/node/949424, there's an attachment with a testing plan there which we've used in lab tests before. Doing those same tasks will give us comparable results. Thanks!
Approach for accessibility testing
@yoroy, thanks for the info. While I think we want as much consistency between the usability tests and these accessibility tests, there are a few differences that I would suggest:
First, I think we should start with Drupal already installed. In the Usability Beginner Test Script, the first test was installing Drupal. But for accessibility testing, I think we should jump right to the most important and most frequent tasks. It is important that the Drupal installation process be universally accessible, but I would suggest that adding comments or creating a node are much more important.
Second, I suggest that we give more "training" than the usability tests provided. For example, the usability tests directed the test subjects to . But for accessibility testing, I suggest we tell users about the concept of blocks and ask them to create or edit a block.
We already know that the words "block" and "node" can be confusing and meaningless. This is a problem for all Drupal newcomers regardless of any disability. What we want our tests to focus on is whether Drupal is accessible. That is my 2 cents. I would appreciate others' input and expertise as we all try to craft a plan for the most effective accessibility testing.
www.pixotech.com
groups.drupal.org Accessibility: Drupal 7 Usability Tasks to tes
Hello everyone,
This is Hadi Rangin from the University of Illinois.
Some of you might know me from working on other accessibility related projects but for those of you who don't know me here's a brief introduction.
I am working for the University of Illinois as Web Design & IT Accessibility Specialist. My primary responsibility is to work with on-campus developers and product development teams from vendors we buy products from to ensure that they incorporate accessibility in their design process. I also help them to find the best technique to implement the accessibility support in their application and test their applications during the development phase to ensure that we are on the same page.
Some of the external products I worked on are WebCT, Blackboard, Ebsco Publishing, Scopus, Ex Libris, Elluminate, and Qualtrics.
We had a meeting with some of our Drupal lovers/developers in our campus/area such as John Barclay and Brandon a couple of months ago and I was asked to work with the Drupal Accessibility Group. I also talked with Everett a while ago about and created an account at the Drupal site and I thought I was subscribed to the your list but after talking with Brandon, I realized that having an account on the Drupal site does not necessarily mean that I am subscribed to any group.
Anyway, I am now subscribed and trying to follow your discussion but at this time I don't know enough about Drupal to provide any good feedback. I think I need to bug John Barclay and Brandon to help me to learn enough about the Drupal (hopefully) in the next days.
Looking forward to working with you all,
Thanks,\
Hadi
Welcome!
Hija Hadi, welcome to the party! Very nice to have you here.
Welcome Hadi
Welcome, Hadi! Here is another thread where we're talking about ideas for promoting Drupal accessibility at the DrupalCon Chicago 2011 conference in Spring 2011: http://groups.drupal.org/node/104089
I'm excited to get your ideas.
www.pixotech.com
Hello everyone, I think you
Hello everyone,
I think you all pretty covered all the good ideas for an effective accessibility presentation.
By reading the thread I have realized that your potential audience are core/module developers and to my experience once they have their aha moments then with a little help you will have them on board.
I think the best way to get their attention is if you use one of their own module and tries to interact with it just with the keyboard and/or screen reader program but please with the monitor turned on. It is very confusing and distracting for a typical developer to follow the screen reader program with the monitor turned off and it could give a wrong message as if they would need too lengthy and comprehensive description for each element.
Here's what I would suggest:
1. A brief introduction into different types of disabilities and how people with disabilities approach and interact with the web.
2. Demonstrating one of the modules developed by one the developers present in the session and illustrating and highlighting accessibility issues with it.
3. Show how the problem could be resolved if they would have used one of the accessible techniques.
Note that accessibility is an abstract issue for most developers and they might not switch to the accessible techniques over night. They need time and help to feel comfortable with the new techniques and one should encourage them to post their questions publically or privately.
I was wondering if there is a Drupal coding best practices that developers can read, learn, and follow and lead them to more accessible module out of box.
How about if a developer has an accessibility related question? Does he/she know where to ask about it?
I believe the answers to my questions are yes but I just wanted to know.
Thanks,
Hadi