It is the true teacher who leaves the class knowing they have learned the most.
Tucson, AZ
Joined September 2006
- Tweets 64,757
- Following 13,801
- Followers 26,057
- Likes 36,165
@sarahebourne I'm talking about a software problem, Sarah. Not good document semantics. Different issue, same heart.
1
Pragmatics define the technique, and we are working through that now. It isn't pretty. We do our best we make mistakes, we learn. ThxMols
1
But HTML itself should NEVER have had any function attached to an element by default IMO. EVER. This was a software problem we inherited.
3
1
1
ACCESSIBILITY features should be in the OS and/or browser. Real world example? ZOOM in Opera (solves page resizing). This is our failing (5)
3
1
1
Adaptive features began appearing on the document layer, with few exception. This began a NIGHTMARE of problems for all of us because (4)
1
Due to a lack of interest and participation in the making of specs by co's like Freedom Scientific and other Adaptive Technologies (3)
1
1
To address accessibility well, as computer scientists, we should be doing this at the software and/or OS layer NOT in HTML. (2)
2
3
Alright, you want to get into it, let's get into it. The Web grew fast, and we hacked around, which messed up inherent accessibility (1)
1
@bjornjohansen That you still have to do that proves the point explicitly!
No, that would be the canvas, @phidip. But not the <canvas>. And don't forget, there's the chrome, too. But not The Chrome.
@200ok I pointed out earlier (and Twitter being Twitter, people missed) that IMO the article needed better editorial development.
2
@200ok Always. A world without semantics would leave me bereft.
Yes! @richquick. But you forgot the most important, shame on you: To use as a container with position: relative; and no offsets. ;)
1
"This is an between-elites argument" - @firasd I just tweeted the very same conclusion. GMTA :)
I love how we (me!) talk about semantics and HTML5 and CSS3 as our daily fare. Most people publishing to the Web aren't devs at all.
2
1
1
I'd love to see some real stats on how many people publishing web sites even know what a <div> means, much less <section> or <article>. ha!
4
2
1
Bottom line is that I appreciate @divya's point in our changing times, and encourage people to articulate their arguments. This is Open Web.
3
Challenging our status quo might be uncomfortable, but it's necessary. Out of these discussions can come innovation and clarity. Or chaos.
2
@richquick @StuRobson I can top you both. I'm saying look beyond that one statement into the rest of @divya's message.