Usability

Hello All,

Over the last few weeks, we have come up with a list of important tasks that we deemed important for the module redesign. However, we would like to test those with our users. So, we are going to conduct interviews and understand how they use the module page.
Following is the guide we intend to use to do the interviews:

Research module page

Goals

I'm considering using a service such as http://www.usertesting.com/ for usability testing on behalf of a client who doesn't necessarily have the time or budget for using a proper usability lab, but would probably benefit from some basic form of usability testing.

Has anyone tried a service such as this? If so, what pros/cons exist?

The first problem we need to solve is how users get around Drupal's interface on devices with small screens and touch screens. See the D8MUX road map.

Let's do some brainstorming and prototyping over how we get this good on mobile.

What do we need?

• Simple
• Consistent
• Finger friendly
• Complementary - The navigation can't upstage the main purpose of the page or task.

Current pain points

One page many purposes

As we found out in London, Drupal's mobile admin interface faces some big obstacles to overcome. If we want to to be able to tackle some of these problems in the next release cycle we need focus, the idea being we don't move on to the next item in till we have the previous one licked. I've whipped up proposal for our road map. This is by no means complete, there is plenty of detail to fill in.

I'm hoping we can work on it together.

Words to live by

Don't let the current interface hold us back

During the accessibility BoF at Drupalcon London several people showed interest in resuming the monthly conference calls that we have had in the past.

I would be happy to participate in these calls, and think we should get started. There are several initiatives that require some attention, primarily:

1. html5 accessibility (including WAI-ARIA in Core)
2. WYSIWYG in Core
3. Further triage and patches for open accessibility issues
4. ...

I'm hoping that someone will volunteer to organize these calls so that we can:

In order to be more efficient in our approach in identifying issues, we have created a simple google spreadsheet. The intent is for everyone in the community to be able to log issues easily. Over the period of time we will be able to prioritize and solve these usability issues.

I hear you guys, this is a very 1.0 way of doing it, but at least it is a start! right?

So when you get annoyed with something, make a difference, log the issue.

Here is the google spreadsheet: https://docs.google.com/a/acquia.com/spreadsheet/ccc?key=0Ai6zQDgsPhvldH...