Alt atribute

Well this is not possible. This alt attribute is by defintion the "alternate representation" of that image, in out case it is the original image location (not the preset one). As we dont have "one image one node" relateion in the 6--1-0 branch, we are not able to save any meta-data at any other places then inline in the html img tag. In that case, we reuse that alt value to place at the original image. Later, when you edit that image, this "original2 image will be used to generate the new preset you might have added (so the preset is always generated using the original image). that is the case, because there is no relyable way to reverse-map a preset image path to its original.

These kind of meta-information, even more, will be possible in the 6--2-0 branche where every image will become a node.

Wrong state

Why i really se a valid point in your approach g.idema, i dont think we should introduce this in the 6--1-0 branch. We are limited in the number of meta fields here + this branch should stay very very simple.

Please wait for the 6--2-0 to apear which will also include alt and other meta informations which you will be able to use

While this is another very elegant solution to allow images to be added to posts - similar Image Browser in some respects, certainly in how it stores things like image locations, but perhaps this is even nicer! However this is very difficult for me to use. I work mainly with charities and organisation that work with charities and disabled people. For reasons of accessibility, this module fails.

I speak for the many people who use assistive technologies to access websites. The Web Content Accessibility Guidelines 1.0, available at http://www.w3.org/TR/WCAG10-TECHS/#tech-text-equivalent make it very clear:

Guideline 1 - Checkpoint 1.1

Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images...

And this is a priority 1 requirement:

[Priority 1]

A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.

In many countries it is now illegal to provide web content that discriminates against particular groups of users. For the example, in the UK, the Disability Discrimination Act says that:

5.23 (p71): “For people with visual impairments, the range of auxiliary aids or services which it might be reasonable to provide to ensure that services are accessible might include ... accessible websites.”

Alt text for images is the 1st checkpoint of the first guideline in the WCAG (link above) and has the highest priority. I applaud the module - it makes adding images a breeze, I just wish that such a basic thing was given higher priority.

All your arguments are valid. So i guess you have to wait for the 2.x version, where this will be fixed properly.

That's good to hear. Thanks for your response!

This is actually fixed in the current 6.2.0 release. You now can set alt to whatever you like, currently the title is used ( you can change that overloading the theming method.

stable 6.2 is out :)