Linked by snydeq on Tue 16th Aug 2011 16:46 UTC
Web 2.0 InfoWorld's Peter Wayner discusses the 11 hard truths Web developers must accept in making the most of HTML5 -- especially those who are looking to leverage HTML5 in hopes of unseating native apps. 'The truth is, despite its powerful capabilities, HTML5 isn't the solution for every problem. Its additional features are compelling and will help make Web apps formidable competitors for native apps, but security issues, limitations of local data storage, synchonization challenges, and politics should have us all scaling back our expectations for the spec.'
Permalink for comment 485486
To read all comments associated with this story, please click here.
RE[4]: HTML 5 == Pointless Bloat
by Brendan on Wed 17th Aug 2011 10:17 UTC in reply to "RE[3]: HTML 5 == Pointless Bloat"
Brendan
Member since:
2005-11-16

Hi,

"Of course for blind people, you really don't want HTML at all - you want something designed for complete control over audio (both sound and speech synthesis), including timing, volume, position, etc; and you want web developers to design sites specifically for audio (including site navigation, etc) instead of trying to make something intended for visual content delivery (and primarily used for visual content delivery) work in a "half-assed, almost better than nothing" way.


Somebody hasn't heard of Aural Stylesheets.
"

You're right - I hadn't heard of Aural Stylesheets (and I wouldn't be surprised if most people haven't).

Do they magically restructure an entire web site? For example, with an Aural Stylesheet would the OSNews main page automatically be split up into many smaller (easier to navigate) pages with no more than about 8 articles/news items per page; with the headlines as a single list at the beginning (and all the extra clutter like the search, login, and the "legalese" at the bottom shifted to a separate page)? Or was I right from the start - it's a barely adequate compromise that fails to come close to being usable on it's own (unless web developers deliberately design a radically different "intended for audio" version of their site, that shares nothing in common with the "intended for video" version other than the database backend)?

Forgive me for suspecting the latter..

- Brendan

Edited 2011-08-17 10:18 UTC

Reply Parent Score: 2