Accessibility Show number eight was a fun one. For most shows, I’ve searched out specific sites that demonstrate particular problems so that we can demonstrate different ways that problem shows up in real sites. For this one, however, I wanted to show something else, as well: how ubiquitous keyboard accessibility problems really are. So instead of carefully pre-selecting sites, I just grabbed the first ones in the list as I saw it at the time. It would have been nice […]| Joe Dolson Web Accessibility
It’s the time of year again when browser makers ask which shiny new features they should implement in preference to fixing outstanding bugs. Despite my cynicism, I’m trying again with these submissions. They’re mostly typographic but in some cases important.| clagnut.com
Last week, the CSS WG resolved to add an inline if() to CSS. But what does that mean, and why is it exciting? Last week, we had a CSS WG face-to-face meeting in A Coruña, Spain. There is one resolution from that meeting that I’m particularly excited about: the consensus to add an inline if() to CSS. While I was not the first to propose an inline conditional syntax, I did try and scope down the various nonterminating discussions into an MVP that can actually be implemented quickly, discusse...| lea.verou.me
People often recommend using third-party libraries because we don't waste time on reinventing an untested wheel. In reality using third party libraries has its costs, and some of them are not immediately noticeable.| WaspDev
Can some organization create a new browser from scratch? Is it realistic and what will it take?| WaspDev
Applets. ActiveX. Flash. Flex. Silverlight. Angular. React. Plenty of corporations thought they knew better but failed to see the larger picture. Innovation as collaboration is one thing, but innovation as an attempt at displacement of compromise and collaboration is another.| GarrettDimon.com Full
I really appreciated Cory LaViska’s take on #WebComponents here. Especially this bit:| Aaron Gustafson: Latest Posts & Links
