- Make the right thing easy
- Always answer “so what”?
- Close the gap between “something is wrong” to “we fixed it”
The primary goals of this strategy are to inform decision-making and enhance the success of accessibility-related activities within the GOV.UK Design System team.
Interestingly, accessibility concerns are put into two categories: theoretical and evidenced (with the evidenced concerns being prioritised):
- Theoretical: A question or statement regarding the accessibility of an implementation within the Design System without evidence of real-world impact.
- Evidenced: Sharing new research, data or evidence showing that an implementation within the Design System could cause barriers for disabled people.
I’ve personally never really seen frontend as an assembly job. Lego is admittedly awesome, but for me the mental model of assembling Lego bricks in the required order until a Jira ticket can be marked as “done” feels too linear and too rigid for how I like to work. And that’s not to mention the pain that comes when you have to partially dismantle your bricks to correct some earlier misstep.
I like the pottery analogy.
Over the past 10 years or so, we’ve slowly but very surely transitioned to a state where frameworks are the norm, and I think it’s a problem.
The whole article is great, and really charmingly written, with some golden nuggets embedded within, like:
- You’ll find that spending more time getting HTML right reveals or even anticipates and evades accessibility issues. It’s just easier to write accessible code if it’s got semantic foundations.
- In my experience, you will almost always spend more time overriding frameworks or compromising your design to fit the opinions of a framework.
- Always style from the absolute smallest screen your content will be rendered on first, and use
@media (min-width)queries to break to layouts that allow for more real estate as it becomes available.
- Always progressively enhance your apps, especially when you’re fucking with something as browser-critical as page routing.
Styling a list of nested
details elements to create a beautiful lokking tree view, all in CSS, all nicely accessible.
The first day back at work after some time away is a kind of reentry: you’ve been in orbit, untethered from the gravity that typically keeps you in your chair, and now the friction of the atmosphere is rapidly warming you up, and weight is coming back into your bones, and it’s a lot to feel all at once.
If you’ve made a computer do something - anything - in a logical fashion, you’re a programmer. Scratch? Programmer! CSS? Programmer? Conditional formatting in Excel? Programmer!
Strong—and true—words from Alex.
Frontend’s failure to deliver in today’s mostly-mobile, mostly-Android world is shocking, if only for the durability of the myths that sustain the indefensible. We can’t keep doing this.
If you disagree, I encourage you to dive into the data that Alex shares.
A look at back at what wasn’t in the headlines this year.
Pluralistic: Web apps could de-monopolize mobile devices (13 Dec 2022) – Pluralistic: Daily links from Cory Doctorow
But you can’t have a web app without a web-app-compatible browser, and you can’t get a web-app-compatible browser in Apple’s App Store. The only browsers permitted in the App Store are those based on WebKit, the browser engine behind Safari. This means that every browser on iOS, from Firefox to Edge to Chrome, is just a reskinned version of Safari.
All along, from the frothy 1990s to the percolating 2000s to the frozen 2010s to today, the web has been the sure thing. All along, it’s been growing and maturing, sprouting new capabilities. From my vantage point, that growth has seemed to accelerate in the past five years; CSS, in particular, has become incredibly flexible and expressive. Maybe even a bit overstuffed — but I’ll take it.
For people who care about creating worlds together, rather than getting rich, the web is the past and the web is the future. What luck, that this decentralized, permissionless system claimed a position at the heart of the internet, and stuck there. It’s limited, of course; frustrating; sometimes maddening. But that’s every creative medium. That’s life.
Almost no-one has given informed constent to being tracked through spy pixels in emails, and yet the practice is endemic. This is wrong. It needs to change.
This is a genuinely lovely use of machine learning models: provide a prompt for an illustration to print out and colour in.
Mike explains his motivation for building this:
My son’s super into colouring at the moment and I’ve been struggling to find new stuff for him.
A profile of the life and work of the brilliant Octavia E. Butler.
It sounds like Remix takes a sensible approach to progressive enhancement.
The speed with which Twitter recedes in your mind will shock you. Like a demon from a folktale, the kind that only gains power when you invite it into your home, the platform melts like mist when that invitation is rescinded.
This extract from Baldur’s new book is particularly timely in light of the twipocalypse.
A lovely fansite dedicated to the life and work of Paul Rand.
I often use the word quality when referring to apps, products and services I hold in a high regard but another word that often comes up in this context is craft. Craft, as in something that is handcrafted where something someone spent a lot of time on and maybe even embedded their own personal touches and personality in it. Often something handcrafted feels more premium.