A list of pages I added to Pocket.
-
If you are familiar with web accessibility that visual disabilities are both prevalent and multifaceted at the same time. It follows that one of the cornerstones of accessibility is making a page adaptable or allowing it to stay adaptable.
-
Most inputs have something in common — they are happiest with a companion label! And the happiness doesn’t stop there. Forms with proper inputs and labels are much easier for people to use and that makes people happy too.
-
33 min read Tools, Accessibility, CSS, JavaScript Saved for offline reading Share on Twitter, LinkedIn In a new short series of posts, we highlight some of the useful tools and techniques for developers and designers.
-
The Service Worker API is the Dremel of the web platform. It offers incredibly broad utility while also yielding resiliency and better performance.
-
My talk Applied Accessibility: Practical Tips for Creating more Accessible Front-Ends is now available to watch online.
-
If I’ve learned anything while coding for accessibility, it’s that I don’t know what I don’t know.
-
Learn how to identify and fix layout shifts. The first part of this article discusses tooling for debugging layout shifts, while the second part discusses the thought process to use when identifying the cause of a layout shift.
-
TL;DR: A lot has changed since 2017 when we last estimated a global baseline resource per-page resource budget of 130-170KiB. Thanks to progress in networks and browsers (but not devices), a more generous global budget cap has emerged for sites constructed the "modern" way.
-
Using display: contents should allow us to use semantic elements to ensure that our content is understandable by accessibility technology, while also not displaying boxes for those elements.
-
HTML is at the core of many things we do. It’s so ingrained in the frameworks we deal with on a daily basis, many of us might feel like we know it relatively well. I guess I was one of these people - I thought I knew what I was doing. At least sort of. Until I started diving into accessibility.
-
Safari 5.1, back in 2010, was the last WebKit browser that somebody released for the Windows platform. Since then debugging things in WebKit came down to either buying a whole Mac or using a remote Safari in Browserstack.
-
When I first learned CSS clip-path back in the days, I took more time than I had expected, and I struggled to memorize it, too. I don’t know the exact reason, but maybe because I didn’t use it that much? Anyway, I will re-learn it with you.
-
It is easy to get the idea that ARIA fixes everything for accessibility, but the reality is that ARIA serves a very specific purpose, for a very specific audience. ARIA is only supported in browsers and screen readers.
-
A lightweight web component helper for HTML5 videos. Intended for use with muted by default HTML5 videos. Only start playing when the video is visible in the viewport with data-visible-autoplay (via IntersectionObserver) Make sure you don’t use the autoplay attribute.
-
There are lots of ways to test your web site for accessibility issues. Services, software packages, even human testing companies. They all have their place and often a test with real people is the best thing to do.
-
The Progressive Web App term is now five years old, and it's time to sit down and understand where we are at 2021 within the platform, what has changed during 2020 and what we are expecting for the upcoming months. 2020 was a particular year for everyone, and Progressive Web Apps are no exception.
-
This is episode #23 in a series examining modern CSS solutions to problems I've been solving over the last 13+ years of being a frontend developer. When it comes to CSS, sometimes a border is not really a border.
-
The title for this page came from a slip of my tongue. I actually had wanted to say "responsive and accessible" web applications, but somehow "responsible" slipped out.
-
When we boil it all down, websites are really just a series of words and pictures. It’s a way for a person (or sometimes a robot, or sometimes a robot in a person trenchcoat) to tell you about a thing and you, a visitor to their internet page, to consume that thing in whatever form.
-
First we need to do some level-setting. The web, by its very nature, is a net-negative for the environment. It exponentially grows at a near-inconceivable scale, and with that comes an ever-growing demand for power.
-
-
I edit a lot of technical articles over at Smashing Magazine, and write a good few myself. Over the years I’ve absorbed a lot of information in terms of what works when writing tutorial content, and one thing I keep coming back to is that you need to know who the ideal reader of your piece is.
-
Screen readers are designed to do one thing: read what’s on the screen. That’s why they call them screen readers, right? You would think that screen reader software would have perfected the art of reading text by now, because that was the whole reason why screen readers were invented.