]]>
]]>
Passe en niveau de gris un site pour en apprécier les contrastes
Lately we’ve been tinkering with deploying Android beyond the phone (using Google’s open-source Android to connect devices to each other and the web), so we thought we’d see if we could leverage the efficiency of Android on a BeagleBoard, the accessibility of wireless webcams, and the ease of a Flickr feed to a custom Google Gadget to track the ups and downs of our metered utilities. Why webcams? While there may be a few compelling (low-cost, low-impact) products out there to monitor your electric meter, there are no comparable products for reading gas or water meters. So until the really smart grid arrives, here’s a way to chart your whole utility spend on your own Google homepage.
]]>
]]>
Last but not least, we have also improved some of our accessibility features. The Overlay widget now prevents focus from going to other elements when set to "modal", InfoPanel has better ARIA support and the Slider widget has more intuitive keyboard access for screenreader users.
TAW3 with a click allows to verify, with just a click, the accessibility of the Web sites that you are visiting, by means of the TAW3 online service (www.tawdis.net) and making use of the W3C Web Content Accessibility Guidelines (WCAG 1.0 and WCAG 2.0).
]]>
]]>
]]>
"Techniques for WCAG 2.0" provides information to Web content developers who wish to satisfy the success criteria of Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20]. Techniques are specific authoring practices that may be used in support of the WCAG 2.0 success criteria. This document provides "General Techniques" that describe basic practices that are applicable to any technology, and technology-specific techniques that provide information applicable to specific technologies. The World Wide Web Consortium only documents techniques for non-proprietary technologies; the WCAG Working Group hopes vendors of other technologies will provide similar techniques to describe how to conform to WCAG 2.0 using those technologies. Use of the techniques provided in this document makes it easier for Web content to demonstrate conformance to WCAG 2.0 success criteria than if these techniques are not used.
]]>
Making styling easy as cake with accessibility and performance baked-in.
]]>
]]>
Cargo is a web publishing (CMS) and community-building platform currently in development.
Cargo evolved out of the system that runs the SpaceCollective community. We found it remarkably successful and efficient in creating visual content on the web, placing a strong emphasis on design, layout, image quality and typography. Our goal is to dramatically increase the accessibility and exposure of creative individuals on the Internet, while aspiring to build a networked context that will contribute to the culture as a whole.
Web Accessibility Initiative’s Accessible Rich Internet Applications.
Description des outils * CoLT : une extension pour copier/coller des URLs. Elle peut-être facilement paramétrée pour générer le raccourcis typo SPIP d’un lien. Voir la contrib : COLT : Extension de Firefox utile pour SPIP * Firefox Accessibility Extension : donne des outils pour vérifier l’accessibilité d’un site. * HeadingsMap : très pratique pour voir les titres utilisés sur une page et vérifier leur cohérence hiérarchique [2]. * Resizeable Textarea : un champ de texte trop petit pour la saisie ? Il suffit de le redimensionner ! * ColorZilla : une pipette pour récupérer une couleur dans une page web [3] * Html Validator : pour vérifier immédiatement la validité de votre page. À régler en mode SGML !
The Email Standards Project works with email client developers and the design community to improve web standards support and accessibility in email.
]]>
]]>