A brief round up of what I did this year, mainly for myself but you can read it if you want.
Posted in: General
Definition of tabindex from w3.org:
This attribute specifies the position of the current element in the tabbing order for the current document. The tabbing order defines the order in which elements will receive focus when navigated by the user via the keyboard.
In general you shouldn’t need to explicitly set the tabindex of an element on a page, however there are a few exceptions to this
Today I got a comment on Autoplay is bad for all users which asked:
So why does this high-traffic site designed by a former top-Google UX designer use it?
The comment has linked to a page which has video as a background element playing underneath the introduction text and call to action button, the images are moving but there is no sound on page load. At times this apparently important information is completely invisible.
Using video as a background is on the increase so it’s important to know how to make it accessible for everyone.
My professional life as a front-end developer started just before the Web Standards Project, everyone was working to make sure style was separated from content. It was drummed into me and I drummed it into you for many years, so it’s been difficult to forget.
Are you bored of looking up which vendor-prefixes are still required for a particular rule on a particular day, or you want to remove the bloat that a catch-all mixin gives you? Then read on.