No, ‘AI’ Will Not Fix Accessibility
Public
Some blogging myths
Nvidia Should Sell GeForce.
Nvidia Should Sell GeForce.
Watch Out for Layout Shifts with ‘ch’ Units
Since `ch` units are based on your current font their value can change when fonts are loaded and cause unexpected layout shifts.
Re-evaluating px vs em in Media Queries
We used to say ems were the best unit to use in media queries.
Is that still the case in 2023?
How to use the placebo effect to (actually) feel better
The placebo effect is way weirder than you think.
The Accessibility to Burnout Pipeline
A Richer Canvas - Mark Boulton
Content out
Grid system design should begin with a constraint. Something that is knowable and unchangeable.
Responsive design: seams & edges
In some ways, responsive design was an attempt to move past the idea of a “page.” How’s that worked out for us?
as soon as a page is published online, we can’t predict how someone experiences it. Their screen might be wildly smaller or larger than mine, sure. But any number of factors might change the user’s experience: their network might be punishingly slow; their data plan could be stringently capped; they may use their voice to interact with my design; they may not see the screen like I do. In other words, we’ve never had any kind of control on the Web. And that lack of control can feel scary, sure — but if we approach it properly, it can be incredibly powerful.
codedisplay: contents/code considered harmful
Should vs Want | Matt Wilcox, Web Developer & Tinkerer
A blog post from some months ago, which I never published. Here it is, finally published.
Markdown images are an anti-pattern
Boringness in Design Systems
The Most Exciting Design Systems Are Boring | Big Medium
Design systems should solve problems that designers confront over and over again, so that they can turn to more interesting challenges.
Thinking on ways to solve color palettes
The ongoing defence of frontend as a full-time job
Things You Should Never Do, Part I
Whose web is it, anyway?
Sir Uncle Timbo (Tim Berners-Lee to you) famously designed the web for all people, whatever their hardware, software, language, location, or ability. As mobile devices become ubiquitous, yet controlled by a de facto duopoly, how can we ensure that the web remains open, affordable, and accessible for our 3 billion neighbours who are as yet unconnected?
This session is from the Development Track.
About the Speaker:
Bruce was a member of the committee that drafted the British Standard for commissioning accessible websites, and an editor of the HTML5.3 spec for the W3C. He’s also a musician and has been a Bollywood movie extra, tutor to a Princess in Thailand, a tarot reader in Istanbul and arrested (mistakenly!) for espionage in Moscow.
Learn more about axe-con at https://www.deque.com/axe-con/
On browser compatibility and support baselines · molily
Evaluating new web technologies and using them safely
Meeting WCAG Level AAA - TetraLogical
Accessibility consultancy with a focus on inclusion. We can help you with knowledge, experience, strategy, assessments, and development.
Design Systems Collection
Explore our free collection of design systems courses taught by Ethan Marcotte.
It is not me who is bad, it is the machine, you see. - Chris Coyier
Slow design
A call to slow down in a fast-moving world.
Build the Archive
I think my website should archive everything; every website I’ve ever made, every weirdo CSS demo, every little thing.
I want to earnestly look back on what I’ve made — the stuff that I think is cool and punk rock as well as the stuff that was half-baked, inexperienced, or headed in the wrong direction from the start.
Sometimes the job is an assembly line
A riff on a post by Robb Owen
creative work is much better suited by a prototyping demo loop or a hot-potato process to overcome the tension between design and development
Anyways. If you do find yourself stuck on an assembly line, I recommend a good set of headphones and chill lo-fi beats or whatever music helps you focus.
Accessibility auditing tips from Nathan Knowler
@elly@front-end.social I know this feeling to well. (I’m still refining my approach, so take all of this with a grain of salt.) If there is a tonne, I would avoid being exhaustive or overly detailed. I try to limit my auditing sessions to a fixed amount of time so that it doesn’t turn into an endless task or wear on me mentally. In situations where there’s a lot, I think it’s more important to call that out, but then focus on the high impact issues. Those will help a client get a sense of where to start and the resources they’ll need for it (which might include followup audits). Also, remember: you didn’t make this mess and you don’t need to burn yourself out to fix it.
Icon transcendence: customizing icons to complement fonts
There are many lovely open source icon sets out there, but sometimes, we just need to 'transcend' them. Product Designer Gleb Stroganov shows us how to craft customized icons by leveraging product font styles, bridging two key interface elements—and giving our products some serious style.
Functional documentation: HeydonWorks
[](https://front-end.social/@elly/110327098611403837){.u-syndication rel=syndication hidden}
Realtime Colors
A tool to visualize color choices and color palettes on a real website to help with branding and UI design decision making.
An alt Decision Tree
Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI).