sul forum di joomla.org ho trovato solo questo al momento poca roba:
http://forum.joomla.org/index.php/topic,103863.msg520006.html#msg520006....
1. Introduction
Accessibility in Joomla! and Mambo has always been a much debated topic. It an area that covers lots of different issues and as a result it means different things to different people. The major issues that are discussed frequently on the forums are :
* hardcoded tables in Joomla! code
* unflexible SEF (search engine friendly URLs) solution
* different issues with metadata (keywords, description and site titles)
* compliance to different accessibility standards (508, WCAG, ....)
These issues have been adressed in the design and accessibilty workgroup and most, if not all, of these issues can be solved within the new 1.5 framework. In this paragraph we will shortly describe the features that have been built into the 1.5 framework.
2. Accessibility in 1.5
Accessibility is a topic that much depends on the client's demands, the goals of the website designer, the audience of the site etc... It seems there is no one solution-fits-all. This awareness made us shift strategy from 'putting it all in the core' to 'making sure designers can do it themselves'. This approach is exactly what we did when we developed the framework; for Joomla! 1.5 we have done the following :
1. All html output has been moved into extension templates. These templates can be overridden in your own site template, allowing a designer to completely change the generated html markup to his liking. He can change css classes, remove tables, make the template compliant to accessibility standards etc...
2. A designer can define his own module wrappers in his site template. In 1.0 there were only 3 hardcoded options, in 1.5 a designer can define his own option to wrap his modules.
3. The menu module in 1.5 now renders as unordered lists by default, the old menutypes are still supported for backwards compatability reasons.
4. The pagination output can be overriden in the site template by a designer.
5. The whole SEF system has been revamped. The core SEF support has been improved and can easily be extended by plugins. No core hacking is needed.
What does this all mean? In 1.5, a designer can change every little bit of html the system generates, the standard output however is still the same as in 1.0 to retain backwards compatibility with 1.0 site templates. This allows the creation of accessible, standard compliant, tableless, whatever-the-designer-thinks-is-important, websites.
We are currently trying to create a semantic site template that will act as a proof of concept to demonstrate how people can use the new features in 1.5. The goal is also to make this template an offical package. Template designers can then use it as the basis for their own accessible and standard compliant templates. The template will be fine-tuned based on feedback gathered from the community and the idea is to move it into the core for 2.0.
....
In short the features can be described as follows:
* Integration of patTemplate for the site templates;
+ Adding incredible flexibility in building form, pages etc. etc.
* Complete separation of logic and output;
+ This option enables new features like a PDA alike output without adjusting functional logic.
* Accessibility improvements
+ See section B.
* Template parameters;
+ Offering full control to templete developers (and of course) users to overide any part of the web-page.
qua il riferimento
