As an extension to our From URL to Interactive series, designer and front-end developer Melanie Richards takes a deep dive into how our content is accessed by a wide array of screen readers, which are highly customizable to users. Understanding the nuances of accessibility APIs, thorough testing approaches, and the wealth of resources available, site creators can create the most widely accessible content for the most users possible.
We continue on A List Apart’s four-part “From URL to Interactive” series with Greg Whitworth, a member of the W3C CSS Working Group and the CSS Houdini Task Force. He’ll walk through how CSS is parsed, how values are computed, and what the “cascade” in style sheets actually means. Then we’ll discuss layout, painting, and composition. Brace yourselves, we’re about to drive through a one of our most scenic and winding parts of our journey.
In the second installment of A List Apart’s four-part “From URL to Interactive” series, Travis Leithead, former editor of W3C’s HTML spec, walks us through the process of parsing HTML: from how browsers create trees to how the DOM responds to events. Equipped with this knowledge, you’ll be able to make smarter DOM decisions, reduce time to interactive, and eliminate unintended reflows.
Kicking off the first installment in our “From URL to Interactive” series, Ali Alabbas takes us through the journey of how our code makes it to the browser. In “Server to Client”, he discusses how server connections are made, caching, and how service workers factor into the request and response process. You don’t want to miss this master class from a networking expert; grasping this aspect of how things run under the browser hood is essential to understanding performance.
The `img` element remains one of the biggest challenges for website performance, especially in responsive designs. In this excerpt from Image Performance, Mat Marquis tells us why, but he also shines a light on the solution.
Should our development practices be hemmed in by the gaping chasm between Internet Explorer and every other major browser? Or should we dash into the future leaving IE users behind? Oliver Williams argues for a middle ground: We can make life easier for ourselves without breaking the backward compatibility of the web.
Now that HTTP/2 is enjoying greater ubiquity than ever, it’s especially important to challenge the once unquestionable rule of resource bundling in client side performance. Join Stefan Baumgartner as he walks you through the potential pitfalls and ill effects of bundling in HTTP/2 environments.