PUBLIC MARKS with search hope

we present here some possible changes and improvements to WCAG 2.0, and items that we hope might help you better understand and implement optimal accessibility

That’s the thing about delightful details: they’re not just another thing you can add on top. Unless you sweat the details all the way through the user experience, the ones that delight quickly get drowned out by the ones that constantly annoy. I hope someone at Amazon will take that to heart.

Let me explain why and how this happened. Years ago an Italian writer wrote a book (not a great book), a story about teenagers, love and death. A scene in this book described two lovers who hooked a lock at Ponte Milvio, in Rome, in the name of their love. Since the book began very famous in Italy among teenagers, all lovers (all teenagers) began to hook their lockets on every bridge, everywhere in Italy: in Florence they began on Ponte Vecchio as well, wasting the beauty of the Art. It’s very difficult remove them, in fact. I hope this stupid behaviour will stop soon, but as I can see it’s common also in France now. It’s epidemic.

HI, THIS IS THE OMMWRITER USER’S PLAYROOM. A PLACE TO CREATE AND INSPIRE.

WE HOPE YOU ENJOY IT AND JOIN US.

We can't send 100 or 101 responses because the caching layer on the front of Heroku eats them. We hope you won't miss them too much.

Despite it's frighteningly boring name, the Windows Phone 7 operating system is in the vanguard of what I fondly hope is an anti-chrome revolution:

Whether or not the HTML spec in the WHATWG is called HTML5 doesn’t really mean that much in the big picture. We need to solve the bigger problems. I hope that we don’t spend our time arguing over the politics of this or that, but on where we should go from here.

Speaking as a long-time Web Developer, I'm appalled by the dismissive

and insulting attitude taken by the constituency dictating HTML 5 as

pertains to the standards that myself and those like me are perfectly

capable of understanding, by declaring repeatedly that we're a bunch of

morons who can't understand resource/representation or anything else

the vendors are hell-bent on changing, as justification for said

changes ignoring those well-understood standards.

Which motivates me to participate in this thread, because I don't want

that vendor-centric approach to pollute HTTPbis, rendering the spec so

large and unwieldy that only browser vendors could ever hope to

understand its meaning, in terms of what they've implemented. A big,

emphatic -1 to the notion that HTTPbis should follow HTML 5 down the

road of standardizing error correction behavior for user agents, for

C-D or anything else.