Issue № 319
Web apps, WAI-ARIA, JavaScript, and accessibility.
by Derek Featherstone ∙ 12 Comments
For seven years, progressive enhancement has been how we build sustainable, interoperable, and accessible web solutions. Now that the release of ARIA is approaching, let's see how ARIA fits within progressive enhancement strategy. Can we use ARIA in a way that respects progressive enhancement? Can we use ARIA in ways that ensure we have a working solution at every level?
by Detlev Fischer ∙ 11 Comments
Web developers interested in accessibility issues often look to WAI-ARIA to bridge the accessibility gap created by ubiquitous scripting and make web applications more accessible to blind and visually impaired users. But can we recommend WAI-ARIA without reservation? Are there times when appropriate semantic HTML elements are preferable to custom widgets?
In any given day I can find myself reading up on a new W3C proposal, fixing an issue with our tax return, coding an add-on for our product, writing a conference presentation, building a server, creating a video tutorial, and doing front end development for one of our sites. Without clients dictating my workload I’m in the enviable position of being able to choose where to focus my efforts. However, I can’t physically do everything.
“We’re at the cusp of understanding the ultimate value of web publishing platforms, particularly ones that work cross-domain.”–Matt Mullenweg of WordPress.
MapBox's new vector-based map tiles are more stable, more scalable, and customizable to an amazing degree.
