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.'
Thread beginning with comment 485615
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: HTML 5 == Pointless Bloat
by Brendan on Wed 17th Aug 2011 21:32 UTC in reply to "RE[5]: HTML 5 == Pointless Bloat"
Brendan
Member since:
2005-11-16

Hi,

This toolkit doesn't magically solve the problem for me but it gives me the ability to build something which does ... much like the Aural Stylesheets.


And that is probably where the problem starts. It doesn't magically solve the problem, but does lure web developers into thinking "semantics" is "good enough".

Providing facilities to allow blind people to use a web site isn't really an option. Typically there's legal obligations (various equal rights laws in different countries). Most web developers just couldn't be bothered doing extra work for a relatively small amount of potential users. Instead they create "visual user only" web sites then fail to provide a stylesheet for aural users; and pretend that using semantic markup is "enough".

Basically, "semantic markup" is used as a scapegoat, so web developers can continue doing nothing for blind users despite legal obligations.

Note: Before when I said I hadn't heard of Aural Stylesheets, what I really meant was that I've done several web development modules (all of them that were offered) as part of a CS degree, and hadn't heard of Aural Stylesheets. The university completely skipped over the entire issue. I'm hoping galvanash will reply to this too - he's been doing web development since 1996 or so, and I'd be willing to bet that in those 15 years he's never created an aural stylesheet or tested any of his web sites with a screen reader.

Now consider what would happen if there was an Aural Markup Language (AUML?); and if web developers couldn't rely on the "semantics" scapegoat. Web developers would be forced (by legal obligations) to actually design sites for blind users; and if that happened a lot of people (not just blind people) would use it (it'd be perfect for things like smartphones - imagine browsing OSNews via. headphones while you're out jogging).

- Brendan

Reply Parent Score: 2

fran Member since:
2010-08-06

I think CSS is a shining pearl.
Not only in structure. (bring a sort object orientated approach like inheritance) but also semantically it is very quick to grasp, write and read.
It also is preferred use in many best practice due to performance advantages to HTML styling tags.
Tables is one example where the CSS styled ones load faster than the HTML tags.
I hope that they can just forgo the majority of HTML styling tags in favour of CSS.

Reply Parent Score: 2

galvanash Member since:
2006-01-25

I'm hoping galvanash will reply to this too - he's been doing web development since 1996 or so, and I'd be willing to bet that in those 15 years he's never created an aural stylesheet or tested any of his web sites with a screen reader.


Aural stylesheets - no. I have read about them but I have never done a website using them. I have, however, tested quite a few sites I have done using JAWS. I will admit, however, that the effort was simply to ensure basic compatibility with a screen reader - I wanted it to work, but we did not go out of our way to optimize for it. That said, if you just want basic screen reader support and you use semantic tags properly it is pretty much automatic ;)

Reply Parent Score: 2

lucas_maximus Member since:
2009-08-18

Well in any discipline you will have those that will do "just enough" and those that will make their best efforts to great stuff.

Blaming the semantic markup and CSS however for lazy devs is still crazy.

Reply Parent Score: 2