Who is Accessibility for?
Accessibility can mean many different things. In general, when we talk about web accessibility, we are referring to users with a physical, visual, or auditory disability, but accessibility can span many more things. Each type of disability has a huge spectrum on how it impacts users, for example, a person with significant vision impairment might expect to be able to easily scale up a font size, and so would a person who misplaced their glasses that morning.
Why Does Accessibility Matter?
Web accessibility is important because all users expect great experiences on the web. It is important to create inclusive experiences so that our websites are usable by everyone. Following accessibility best practices also can have a significant impact on the user experience for all users. …
As many of you know, the next major version of webpack was recently released , bringing with it the promise of significantly faster build times and a zero configuration mode for simple projects. In this post I’ll focus on how we upgraded our build system from webpack 3.10.0 to webpack 4.50.0.
Upgrading build systems can be very daunting and scary, because (if you’re like me) you’re not always sure what’s happening under the hood. Hopefully after reading this you’ll gain a better understanding of what webpack is doing!
So you wanna set-up eslint on all your projects globally? If you’re like me, one of the first things you do when you start a new project is wish you had your linter set up, then spend an embarrassing amount of time setting up eslint.
There’s lot of benefits to using a linter, like catching typos, small errors, and enforcing a consistent style. Sometimes you just want to start coding quickly, or you don’t want to modify / create a package.json, but you still want the benefits of a code linter
First, let’s talk about setting up eslint for a local…
The document-object-model (DOM) is the paradigm behind the modern web. Unfortunately, working with the DOM is a very slow process. To solve this, modern web frameworks like React work with a ‘virtual DOM’ that lives in a web browser’s memory.
React’s virtual DOM is the key to building fast single page websites. Manipulating the actual DOM is a slow process, but virtual DOMs solve this by only updating the parts of the DOM that changed.
But where is the virtual DOM? How can developers use it? The ‘normal’ DOM is very easy to see — it’s the HTML you get when you inspect a page. …