Loading...
Flash Player 9 (or above) is needed to view slideshows. We have detected that you do not have it on your computer.To install it, go here
SlideShare is now available on LinkedIn. Add it to your LinkedIn profile.
ItalianSkin: an improvement in the accessibility of the Plone interface in order to be compliant with Italian laws and screen readers for blind people
The Italian government has made a law specifying the accessibility requirements (the most famous is the usage of the Strict XHTML) for public administration websites. To enable Plone front- and back-end to be compliant with these specifications the ItalianSkin project was initiated, but its development has gone beyond the simple implementation of the law and has continued with the objectives of making Plone wholly functional with screen readers for blind people and providing developers with automatic tools to improve the accessibility of their own sites. We would recommend this talk to anyone developing websites and in particular to those who are responsible for accessibility.
847 views | 0 comments | 0 favorites | 30 downloads | embeds (Stats)
Slideshow Transcript
- Slide 1: ItalianSkin ItalianSkin, an improvement in the accessibility of the Plone interface in order to be compliant with Italian laws and screen readers for blind people.
- Slide 2: Relators Davide Moro (Redomino) Franco Carinato (Zope Italia) Massimo Azzolini (Redturtle) Nunziante Esposito (Unione Italiana Ciechi)
- Slide 3: How was born based on an idea of Vincenzo Barone developed by Davide Moro (it was my thesis project at the Polytechnic of Turin)
- Slide 4: What is ItalianSkin? ... and why this name? requirements for Italian Public Administrations websites the most famous is XHTML Strict other accessibility requirements all pages should be validated Plone uses the Transitional doctype instead
- Slide 5: Why XHTML Strict? XHTML Strict no accessibility motivations ... but forward compatibility Transitional doctype is transitional next versions will be similar to the strict one more cleaner than Transitional free of presentation clutter
- Slide 6: What we have done (1) Skins XHTML Strict skin (both front and backend) default tableless Editors FCKEditor patch offers some instructions how to use alternative text display an alert if you don't apply a title/alt to links or images Kupu vs TinyMCE Editor vs RestructuredText Franco Carinato will talk about this issue
- Slide 7: What we have done (2) Portal transforms simple XHTML transform stripped out attributes/elements not allowed it could be turned off we will use the configurable Plone3 HTML Filter now
- Slide 8: What we have done (3) Validation tools what happens introducing bad code? provided a validation tool it will be reimplemented with Zope/Plone 3 technologies
- Slide 9: What we have done (4) Automatic validation automatic validation of all content types special thanks to RedTurtle code in a separated branch Massimo Azzolini will talk about this talk
- Slide 10: Validation action
- Slide 11: Validation results
- Slide 12: ItalianSkin tool view
- Slide 13: Target development version preview of the new version of ItalianSkin for Plone 3.0.1 https://labs.redomino.com/ItalianSkin/bundles/3.0.1/ only for development (experimental release) working in progress...
- Slide 14: What we have to do (1)... Improvements to Plone skins provide an high contrast skin (for low vision) or better, provide more that one skins (resting view, ecc...) same default graphical structure implements a skin switcher improve the actual default skin more color contrast (green font on green background) increase vertical distance from links list of links separated from printable characters
- Slide 15: What we have to do (2) Improvements to Plone let's the user to customize the graphical template background color font color ecc... page template's code XHTML Strict check correct labelling controls text equivalent for every nontext element
- Slide 16: What we have to do (3) Improvements to Plone javascript some components don't work without JS resize font reference popup widget forms screen readers'bugs in edit mode Jaws doesn't read formHelp elements can we do something? Franco Carinato will talk about these problems
- Slide 17: Credits Main authors Davide Moro (Redomino) Fabrizio Reale (Redomino) Vincenzo Barone (Abstract)
- Slide 18: Special thanks Franco Carinato (Zope Italia), for intensive testing with screen readers and content editors Nunziante Esposito (Unione Italiana Ciechi), for his tests and suggestions Massimiliano Martinez (Unione Italiana Ciechi), for his consulting about low vision Massimo Azzolini (RedTurtle), for building the validating tool
- Slide 19: Any questions? if we are late, at the end of the other talks
