Hi, I'm Laurent's side here.
Ensuring our tool works properly even without javascript is a premium. It's very easy to forget these days with full JS apps that we need to have a proper HTML fallback that meets real use cases (text browser, slow connection/clients, accessibility…). Keeping the separation explicit forces developers to think about it. Of course accessibility is now doable with JS only but it's an awful lot of work when a simple HTML fallback does the job. The selenium tests would be awesome but it's a lot of work ;) About accessibility (blatant thread hijacking): I don't know if we made a formal announcement but we attended a presentation with Charles Benke from Jean-Philippe Mengual at the latest RMLL about Dolibarr usability for blind people. ( https://2014.rmll.info/conference223) It was a very constructive and moving talk from which I drafted the most obvious points he made at http://wiki.dolibarr.org/index.php/Accessibility. I don't know how to promote these good habits to Dolibarr developers but it's something we need to keep in mind. Cheers, -- *Raphaël Doursenaud* Directeur technique (CTO) Expert certifié en déploiement Google Apps <https://gpcsolutions.fr/raphael-doursenaud-google-apps-certified-deployment-specialist> +33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10 -- <http://gpcsolutions.fr> http://gpcsolutions.fr Technopole Hélioparc 2 avenue du Président Pierre Angot 64053 PAU CEDEX 9 SARL GPC.solutions au capital de 7 500 € - R.C.S. PAU 528 995 921 <http://wiki.dolibarr.org/index.php/Dolibarr_suppliers_France#GPC.solutions>
_______________________________________________ Dolibarr-dev mailing list Dolibarr-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
