I haven't done any testing at all on this, but in your first sentence in the project description you make an accessibility claim without backing it up "Magic tabs is an implementation of tabs that are loaded using ajax, but are fully accessible and degrade beatifully if Javascript is not available."

What kind of testing has been done? How is it better than other tab options?

Comments

yhager’s picture

It means that if you have JS disabled, the tabs will look the same, and will work the same (i.e. all the content will be accessible from a JS crippled browser). It will work with full page load, and will probably be slower, but it will work the same.

mgifford’s picture

Most assistive technology works just fine with javascript as it operates on the DOM. It's great that it works without JS. Certainly there are people and conditions where JS isn't enabled. However, that's not the same as evaluating the output to ensure that it works with assistive technology (or without a mouse).

yhager’s picture

I don't have experience with assistive technology - Can you help?
I assume that if there are links to be clicked, and content to be shown, then any browser-like technology will be able to use those. There is no need for a mouse.

mgifford’s picture

There are some good resources here - http://drupal.org/about/accessibility

If you use Windows, there's a great tool called NVDA that you can use. Anyone with a Mac can use VoiceOver as an assistive technology platform.

There are also links above to help explain how to do keyboard only navigation.

I don't have time to do the testing. If you've got specific questions I can help. However, just because a link can be clicked on doesn't mean it's accessible.

There's also GDO to ask good questions http://groups.drupal.org/accessibility

yhager’s picture

Priority: Normal » Minor

Thanks for the links much appreciated. My time is pretty limited too, so let's hope someone else chips in on this.