Disscussion about: Joomla! aims towards Accessibility and Standards Compliance

[stingrey]

Discussion area for the announcement that:

Joomla! aims towards Accessibility and Standards Compliance
http://forum.joomla.org/index.php/topic,8821.0.html

[interfaSys]

While work had been done to improve the generated output, such as including the ability to provide an alternate text attribute for the image tag, or associating form labels with their controls, full compliance has yet to come.

I just hope this means dropping support for the silly mosimage bot. Just let wysiwyg editors do their job. The best ones provide an image manager with support for alternate text. The special image tab in the frontend editing just brings usability issues and cannot be easily disabled.

[ChuckTrukk]

I agree the WYSIWYG editors can do much more than the mosimage bot.

Chuck

[HarryB]

No need to drop the bot, just don't use it!  Need to retain it anyway to mantain backward compatibility for production sites using it.

[TheSaint]

Perhaps provide support for previous versions of the mosbot, but in the future steer users towards more compliance related standards? Props to the development team for trying to keep output clean!

[rjs]

Fantastic. This is a huge move forward just bringing accessability standards to the forefront. Many have asked for quite some time for major improvements in this area. Glad to see it's being taken seriously.

[vavroom]

@ Olivier, We are currently not looking at getting rid of that bot.  Our goal is to have Joomla! able to provide compliant sites, and the bot provides an important function in that.  It does make placing images with alternate attribute easier for many people (while I realise it may confuse others).  We can't depend on a 3rd party application such as WYSIWYG editor to assist us in providing compliance tools.

So, at this point, no plan to drop the bot.  This doesn't mean we won't be discussing ways to improve/replace this particular function for something more "usable".

@ TheSaint, while one could say the bot outputs "clumsy" code, it *is* compliant.

@ rjs, you're right, many have been asking for a while.  Good things are on the horizon

[allmagica]

Hi,

cant call myself an expert on mambo, but I ve been using it for a couple of months. Now this might have another solution I am not aware of, but if not then I d like to post this question.

I ve used editors like spaw (which seemed to be the only editor friendly to the greek language) and noticed that they altered the code I insert (producing a very weird, unnecessary and even disfunctional code). There might be a way which I have not found out, to insert just html as an item or in a section/category (without it being altered). But if not, it would be great if we had this kind of control over the code.



Hope its not nonsense what I posted .

[vavroom]

Most of the editors allow you to switch between source view and wysiwyg view.  If you click to source view, you should be able to type in your actual html as you want it.

Editors are a big issue for me, most of them don't produce compliant code.  But, until (and unless, which is very low priority at this point) the core team produces their own editor, we won't have any control over that aspect.

[allmagica]

Yes.. insert the code in code view, click on wysisyg view (because otherwise the item will not saved by clicking save) and the editor alters automatically the code to what it suits it . It even alters the url of the images (if one wants to link to another image folder, outside the mambo directory).

But I understand this could be just an individual problem, or even a spaw problem.

If the core team makes their own editor... that would be great. In the meantime (and we can wait and hope ), at least there are some ways to trick the editors...

[focalguy]

This is great news to hear! I honestly just started learning about accessibility, standards, CSS and the important role it all plays in the past few months. I happened to be browsing anAccessifyForums thread the other day and the demand looks to be quite high for this type of OS CMS.

Glad to hear it's on the way! And J!1.2 (hopefully  ) can't be that far off!

Oh, and I say let the developers work on the core and let the WYSIWYG developers work on their product. Go Joomla!

[bluesaze]

I happened to be browsing anAccessifyForums thread the other day and the demand looks to be quite high for this type of OS CMS.

Intresting Once Joomla becomes accessible. They might take it more seriously.