...e gli ruba il pesce.
Andrea Dessì // Andrea, Man, about 20, (x)html operator, web lover.
I'm a Entando Developer!
Yesterday I added a new plugin to the forge.
It's called MooContentAssist.
What does it do? It provides a content/code assist functionality for your webpage.
You define a closed vocabulary and the user will get help to write code or words.
Using control+space or alt+space will be shown the list of keywords or object/function for the current namespace.
I'm waiting for feedbacks...
More Info
Directions web service arrives at Google I/O
Wednesday, May 19, 2010
Google I/O is always a fantastic opportunity for the Maps API team to meet face to face with some of the many Maps API developers worldwide. We believe our developer community is one of the biggest strengths of the Google Maps API, and with over 350,000 web sites actively using the Maps API, there is no shortage of skilled and helpful expertise to tap into.
However Google I/O is not the only way in which we engage with developers. The Google Maps API Google Groups are thriving communities and many of us on the Maps API team enjoy listening and engaging in discussions held on these Groups. In addition we also have the Google Maps API Issue Tracker, a tool with which any Maps API developer can report problems with the API, suggest new features that they would benefit from, or star existing issues or features.
The Google Maps API team takes the problems and ideas featured on the Issue Tracker very seriously, and although we can not always address every issue that is raised, we do consider any that attract a lot of stars. Recently one feature request in particular has been head and shoulders above the rest in terms of the number of stars it has attracted. It therefore only seems appropriate today, as we sit down with our developer community for a Fireside Chat, that we respond to that request by launching a Directions Web Service.
The Directions Web Service is a companion to the existing Geocoding and Elevation Web Services, and allows applications to obtain Driving, Bicycling, and Walking directions through an XML/JSON REST interface. All of the features of the Map API v3 Directions service are supported, including “avoid highways”, “avoid tolls”, and waypoint optimization (travelling salesman solver). For more information, check out the Directions Web Services documentation.
If you have a great idea for a new Maps API feature, please don’t hesitate to submit it to the Issue Tracker. If your idea proves to be popular, we’ll do our best to make it a reality.
Posted by Thor Mitchell, Maps API Product Manager
great! I've starred that issue http://code.google.com/p/gmaps-api-issues/issues/detail?id=235 for the enhancement.
huuh :D
Highlights
WCAG 2.0 in Italian: Authorized Translation Published
Linee guida per l'accessibilità dei contenuti Web (WCAG) 2.0, the Italian Authorized Translation of Web Content Accessibility Guidelines (WCAG) 2.0, is now available, following completion of the W3C Authorized Translations process. WAI encourages translating WAI documents in all languages. See:
- WCAG 2.0 Translations for a list of other completed and planned translations,
- WCAG 2.0 Italian Authorized Translation Published e-mail.
(2009-Dec-21)
(versión en castellano abajo)
I’ve took the classic paint The Maids of Honour (Las Meninas) and made this CSS pseudo-3D/parallax effect. It is pure CSS, so no javascript or flash involved: only CSS and HTML code.
It has been tested and it is working on Internet Explorer 8, Firefox 3, Opera 9, Safari 3, Chrome 4 and Konqueror 3.5, and it validates.
UPDATE: 3D Meninas Explained
Castellano
He tomado el cuadro Las Meninas y he creado este efecto pseudo-3D con CSS. Es CSS puro, sin javascript ni flash; sólo código CSS y HTML.
Para la realización he usado tres imágenes: dos se corresponden al fondo (paredes) y otra de sprites (3 sprites: uno con el lienzo, niño y perro, otro con las meninas, y el último con la monja y acompañante). El posicionamiento de los sprites se realiza mediante hover en un total de 80 anchors. El lateral derecho de la habitación se ensancha y contrae para mejorar el efecto 3D.
Hay algunos truquitos para que el hover funcione correctamente, podéis verlos en el código fuente. Para que no interfieran las imáges en el hover, he usado distintos z-indexs y nbsps con tamaño de fuente de 455 píxeles: el mismo alto que el experimento en sí.
Funciona en las últimas versiones de los navegadores más usados y valida.
UPDATE: Explicación del efecto
brillant tecnique.
but... very messy! :D
A number of popular Javascript UI Libraries are in the process of adding WAI-ARIA support to their widgets and components. What is the current status and future plans for WAI-ARIA implementation in these libraries?
BBC Glow Widgets
Some of the Glow widgets have ARIA support:
The BBC Glow Library does not provide any documentation as to its conformance WCAG Guidelines.
Dojo (Dijit)
All Dojo 1.0 core widgets (Dijit) are claimed to be accessible via keyboard, ARIA, as well as in High Contrast mode.
- Dojo (Dijit) Widget explorer
- Dojo: an accessible JavaScript toolkit
- Dijit Accessibility (a11y)
- Dojo Toolkit Accessibility Final Report from the ATRC, University of Toronto
DOJO provides an Accessibility Statement which states:
“While Dojo does not make an explicit claim of compliance to W3C WCAG 2.0 Level A or to US Section 508, every attempt has been made to meet those guidelines and to make the 1.0 and future versions of the core widget set, dijit, accessible to keyboard, low vision and assistive technology users. “
EXTJS
(Extjs) - It has been reported that there are “Accessibility improvements - Section 508 and ARIA support” in Ext JS version 3.0, but no details are provided. No documentation could be found on what ARIA is implemented and what aspects of Section 508 or the WCAG Guidelines Extjs conforms to.
There is an ARIA Enabled Tree example provided for the Ext JS version 3.0, but no other samples appear to have ARIA support.
The Ext GWT 2.0 Explorer contains some ARIA mark up, but it is unclear at this time which widgets have ARIA support added.
Fluid Infusion
Fluid Infusion includes ready-to-use components as well as a framework to build your own. Infusion combines JavaScript, CSS, HTML and user-centered design, rolling them all into a single package that sits on top of the popular jQuery toolkit.
Fluid Infusion components using ARIA:
Fluid infusion does not provide any documentation as to its conformance to Section 508 or WCAG Guidelines, but it does state that “assistive technology like screen readers are tested extensively with our codebase”
Google Web Toolkit
GWT 1.5 Widgets have ‘baked in’ ARIA roles and states, and methods to add ARIA role and properties. It is unclear what the extent of the ARIA implementation is, a quick review of the GWT Feature Showcase indicates ARIA use in many Widgets:
GWT Widgets that do not currently make use ARIA, on which users would benefit from its use include the Stack Panel, Basic pop up, Dialog box and Split Panels. GWT does not provide any documentation as to its conformance to Section 508 or WCAG Guidelines.
GWT ARIA Resources
- Built-in Accessibility in GWT 1.5 Applications
- Adding Accessibility Support to GWT Widgets: A Guide for Widget Developers
JQuery UI
Use of ARIA is being actively worked on. JQuery have a UI accessibility sub-team, and a JQuery Accessibility email group. Limited ARIA support was introduced in version1.7.
ARIA enabled JQuery UI widgets:
Full ARIA implementation planned for JQuery UI version 2.0 (2009?). JQuery UI does not provide any documentation as to its conformance to Section 508 or WCAG Guidelines.
Yahoo! User Interface Library (YUI)
There are ARIA plugins for a number of YUI widgets. The following YUI widgets currently have an ARIA plugin (as of October 2008):
Yahoo! UI does not provide any documentation as to its conformance to Section 508 or WCAG Guidelines, though it has been suggested that “most of the widgets would stand a rigorous Section 508 testing”. Victor Tsaran, an accessibility engineer at Yahoo!, stated recently that further ARIA support will be implemented in the upcoming version of YUI (3.0).
Libraries with no implemented ARIA support
- ASP.NET AJAX Control Toolkit - The ASP.NET AJAX Roadmap includes WAI-ARIA support in quarter 2 2009.
- Icefaces is the successor to Sun’s opens source library Woodstock. In the Icefaces introduction, Iceface accessibility is discussed, but there is no mention of WAI-ARIA implementaion. It states “Current accessibility standards have not yet caught up will modern Ajax techniques”, which suggests that ARIA has not been considered as yet. There is an ICEfaces Accessibility Spreadsheet available which details level of conformance of Icefaces JSF components in respect to WCAG 1.0. There are no indications in the Icefaces Road Map that WAI-ARIA implementation is being planned.
- Moo Tools - No information can be found on WAI -ARIA support or intention to support.
- Telerik ASP.NET AJAX Components - Claim conformance to WCAG 1.0 guidelines. No information can be found on WAI -ARIA support or intention to support.
- ZK Direct RIA - Documentation refers to planned WAI-ARIA support, but has noot been updated since 2007. A check of the ZK widgets indicates no ARIA implementation. Information about ZK’s Section 508 Compliance.
I was scrolling back my google reader and i've found this article.
Browsers and js frameworks are moving on and implementing new feature for the accessibility issue.
So the question is: What about MooTools and WAI-ARIA ?
I use MooTools and I'd like to know if they will implement something.. I know the team is smart enough for this task!
Posterous and GoogleWave Wavelet
So let's try. :)Here in Google wave you cannot determine what could happen :)In order to help the community provide accessible multimedia, W3C made public it's internal Multimedia Accessibility FAQ. The FAQ provides some practical advice on: What do I need to do to make audio and video accessible? How do I get a transcript for my media? How do I do captions? Where can I get more information? W3C's formal guidance on accessible multimedia is provided in Web Content Accessibility Guidelines (WCAG) 2.0. (2009-10-08)
via (Web Accessibility Initiative (WAI))
L'elenco delle faq comprende:
Eccellente guida sul supporto dei CSS nei client di posta. Da tenere sotto mano quando si realizzano email servizi web.
Guide to CSS support in email clients
Designing an HTML email that renders consistently across the major email clients can be very time consuming. Support for even simple CSS varies considerably between clients, and even different versions of the same client.
We’ve put together this guide to save you the time and frustration of figuring it out for yourself. With 23 different email clients tested, we cover all the popular applications across desktop, web and mobile email.
As the number of email clients continues to grow, we’ve decided to simplify the web-based version of the guide to focus on the 10 most popular email clients on the market. For the complete report on all 24 email clients across the desktop, web and mobile email world, download the complete guide in PDF format.
via http://www.campaignmonitor.com
Read the full article at http://www.campaignmonitor.com/css/
