PUBLIC MARKS with tags css & [en]

While preparing my HTML workshop, I’ve been re-reading W3C specs in far further detail than I ever would’ve imagined. The reading experience is far from delightful. Not only is the text the entire browser width in measure, but it’s dense and laborious to read. No wonder browser vendors have traditionally missed subtle details.

The techniques in this article explain how we can leverage this powerful capability of CSS to also change imagery, alter the navigation on hand-held devices, and set up default CSS for compatibility older browsers.

I think vendor prefixes are hurting the Web. They are hurting Web authors. They are hurting users of browsers. They are hurting competition in the Web browser space. I think we (people developing browsers and Web standards) should stop hurting the Web. It would also make sense for browsers to implement other browsers’ prefixed features to the extent existing content uses prefixed features.

The common conception among Web designers is that a good style sheet is created by hand, each curly bracket meticulously placed, each vendor prefix typed in manually. But how does this tradition fit in a world where the websites and applications that we want to create are becoming increasingly complex?

This article is about how screen readers speak the content added with CSS pseudo-elements :before and :after

a { outline: none; } Don't do it!

The screenshots are taken from 8 browsers on 4 operating systems, for a total of 14 different browser + OS combinations.

HTML and CSS version of Simple Web Buttons by Orman Clark. Free to use