usability

Hi Everyone,

I've just created this accessibility bug on the oEmbed filter for Drupal (D6 and D7),
http://drupal.org/node/1024470

I would welcome any comments and suggestion for improvements.

Many thanks,

Nick

Has anyone considered implementing Distcha ?

Distcha is an accessible Captcha shown here :

http://accessibiliteweb.com/stuff/captcha-slider.html

It is a very promising new way of providing an accessible captcha.

I would like to expand my knowledgebase within storm module with some additional topics. I am not finding an easy way to do this within the module. I am a total noob to this sort of project tracking system so I apologize if this is a simple question.

Thanks in advance for your help!

What I have:
A primary menu (one level depth) at the top of the page.
Some secondary menus to the right, that changes depending on primary links (controlled via Visibility).

What I need:
Primary links to stay active when secondary links activated.

You can see the project I'm working on at nexos

I'm a graphic designer, trying to evolve to serious web design with Drupal, and think I accomplished the theme task very well, but this challenge of active trails...

As part of a bigger usability testing, we recently usability tested Drupal 6 comment form.

I wrote a pretty detailed blog post on my blog.

Some of our findings generated the following issues:
http://drupal.org/node/796236
http://drupal.org/node/632380#comment-2962104

Interested in hearing your opinions.

Thanks,

Fabio Varesano

Not much to say here, but perhaps this would be a good place to hash out what we know and need to know about doing accessibility tests on ARIA-based interfaces. It's a real challenge.

A good place for background information is Jared Smith's presentation at the November 2009 Accessing Higher Ground Conference, Accessibility of Rich Internet Applications.

I was overwhelmed by the amazing support that accessibility is receiving from the Drupal community, we really do rock! We had an excellent presentation at Drupalcon last week by Kate Lynch, and a couple of very productive BoF sessions. In the second session we started to put together some ideas for how we can move forward to ensure that Drupal 8 is a completely accessible CMS, including communicating an accessibility statement, and making sure as many Drupal modules and themes as possible are accessible.

After discussing the d7ux overlay accessibility issue with several at Drupalcon, and mentioning the issue in my lightning talk at the Core Developer Summit I noticed that an Allow users to opt-out of the overlay issue had been opened in the bug tracker. Overlay is a contentious topic for some in our community, and I will not rehash all of the pros and cons for Overlay's inclusion in core. I will however attempt to concisely present an argument for Overlay being disabled in all Drupal 7 core installation profiles.

Before developing a new module, does someone know if there's a module able to parse the body text, analyse it, find every h2, h3, h4, etc. and generate a "quick links" section (in form of an ordered list, or a select list) above the text (like wikipedia pages)?

We need to come up with a good name for a CSS class, but I don't want this discussion to clutter up the issue queue. (Let's reserve the queue for presenting and discussing patches that fix functional or programmatic problems.) So I'm posting this item to see if we can develop an idea that is better than the ones we've already come up with.