This is everything I posted in: thoughts
Is the accessibiliy of a website a binary thing? It depends!
I've worked in web accessibility in various positions, this post is about how the accessibility-specialised developer's position can be difficult.
As a follow up to my previous post about common accessibility issues, I have written out five more issues that you could fix today.
In which I explain why I feel it's still a great habit to test in many different browsers and browser engines.
Some thoughts on banning certain content from communities versus not doing that.
Tips based on WebAIM’s “Million” survey.
Curiosity and crossing disciplines can result in better products.
A quick response to Dave Rupert’s post on HTML and ARIA.
A write-up of my talk about semantics.
I think there are lots of exciting uses for the web outside the realm of ‘web3’.
Thoughts about auto-adding
Many ask ‘How many users with disabilities use our site?’ We probably don’t need to know, if we need to decide whether to improve web accessibility on our sites.
A look at Facebook’s new ideas through the lense of their current endeavors.
I’m a little torn on whether to see
prefers-reduced-motion as a sufficient way to meet 2.2.2 Pause, Stop, Hide. My thoughts.
I attended a conversation with Cecilia Kang. These are some thoughts about An Ugly Truth and Facebook.
Many use WCAG as a baseline to ensure web accessibility. In this post, I look at doing less and doing more than the standard.
This week I had some fun adding the experimental spicy-sections custom element to this website.
In which I argue app stores need fields for accessibility meta information.
In which I talk about why fallbacks are good.
It may not be easy, but it is important to include perspectives outside your own.
Meetings are better with queues. Here’s why.
Not all ‘accessible components’ are created equal. Find out which will work best for our end users with this checklist.
Web accessibility becomes easier and cheaper, when you address it earlier.
My browser blocked 22281 trackers since July, 2019.
What if more website-owners used Minimum Viable Data Collection as their strategy for complying with privacy regulations?
Useful HTML elements like date inputs and <video> could make the web a much better place, if browser accessibility bugs in their implementations were prioritised.
A written version of my lighting talk “Breaking barriers with your CMS”.
Some thoughts on seeing declarative component frameworks as a way to make the web more accessible, not less.
Are component frameworks at odds with a vanilla approach to web development? Well, partly, but not as much as I used to think. Some thoughts after I tried a framework.
A bit about designing min-content, max-content and auto, and how they can be used.
Recreating old posters, I figured there are at least two approaches to deciding how many grid tracks your component or page needs: one can make it visually perfect, the other is more flexible if content is bound to change.
With more people using tracking protection features, we should test our sites with content blockers.
Last week a poll about CSS got me thinking about the language and overlapping skills in front-end development.
Now that Grid Layout is seeing more adoption, it seems like a good time to remember that websites don’t need to look the same in all browsers.
Five books about artificial intelligence and the philosophy of AI that I can recommend.
According to WCAG 2, criterion 2.4.2, web pages should have titles. How to go about this in a single page world?
Some ways of how, as front-end developers, we can apply ethics in our work.
An introduction to CSPs for front-end developers.
On different meanings of ‘for everyone’.
On why I like newspaper apps that are not much more than PDF readers.
If you have learned how to use Grid Layout, you might wonder what to use it for. In this post, I will give some use cases where I think Grid will excel.
New CSS possibilities are ending the unrealistic content problem and the generic layout problem. It’s a great time to build layouts in CSS!
I’m starting to get more excited about Web Components, and think they can be very helpful to encapsulate compositions of elements.
I’ve found recruiters often look for specific frameworks, but I don’t think they are what matters in web projects.
Last Friday, De Volkskrant exposed how much trouble the Dutch tax office has had in recent years to build software and manage its IT projects. I’ve listed the four main things they lack according to the article.
Can pattern libraries be tested for accessibility? And if so, what do we test? In this post I will address those questions and look at accessibility testing in different levels of pattern library driven development.
In this article, I try to answer the question: is there much inherently wrong with setting standards for what we think is a real/good/professional/sufficient developer?
A look into the early days of CSS and changes that have occurred since.
Some thoughts after seeing the Ken Loach’s film I, Daniel Blake.
On jokes between friends and jokes on a corporate level.
A post about how the
hidden attribute works, how it differs from
[aria-hidden] and how it relates to just hiding with CSS.
In this post I explain why I think declaring behaviour in markup is advantageous rather than problematic.
Some thoughts about standards when it comes to cursors for buttons.
My thoughts about styling with classnames versus styling with HTML elements. TL;DR: we need both.
On the cognitive overhead of cascading
By documenting a web design as a system of components, your website can be an instantiation of your design system.
We can soon use ‘just’ CSS to describe our lay-outs. But, arguably, that leaves us with a naming problem.
I think for large websites and organisations, in addition to having a component system, it makes sense to have one agreed-upon, shared-between-projects grid system.
I think when designing apps that work offline, we should consider user intent and let users choose which content becomes available offline.
Web Components give developers lots of freedom, but also a big responsibility. In this post, I look at the kind of components we need.
Website slowness is optional, and I think that it can and should be avoided. The web is fast by default, let’s keep it fast.
To solve CSS problems, it is much more important to understand the spec and how browsers implemented it, than which abstraction to use.
Google’s algorithm for deciding wether sites are “mobile friendly” is great, but not perfect. In this article, I go into other things we could do to make sites more mobile friendly.
Why not adapt lay-out for languages, like we do for screen widths?