devly

WCAG has 13 guidelines and 86 success criteria across three conformance levels. The good new, you don't need to memorise any of them. What you do need is a mental model, a way to think about accessibility that makes the specifics easier to understand and apply. That mental model is 𝗣𝗢𝗨𝗥. Every WCAG guideline sits underneath 4 principles: → Perceivable: can users sense the content? → Operable: can users interact with it? → Understandable: can users make sense of it? → Robust: does it work everywhere? That's it. 4 questions. Every accessibility failure traces back to one of them. Short article in the comments, covering each principle with code snippets, practical tips, and why POUR matters beyond compliance. 90% of what you need to know, in simple terms.

Don Norman coined the term 𝗨𝘀𝗲𝗿 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 (𝗨𝗫) Then he spent his later career arguing that designers have been solving the wrong problems. In Design for a Better World (2023), he lays out a framework called Circular Design. Here's the core of it: The world runs on a linear model: Take raw materials → Make products → Discard as waste. Waste happens at every stage. Not just at the end. Half of all waste is produced before a product is even manufactured: in mining, refining, and transportation alone. Norman defines three types of planned obsolescence: → Breakdown: components fused so repair is impossible → Progress: new standards that make old products incompatible → Fashion: cosmetic changes that make the old feel outdated And three principles of Circular Design to counter them: → Treat waste and pollution as design flaws → Design products to last, to be repaired, to be reused → Design so end-of-life materials regenerate, not degrade It is too late to stop the damage, but it is not too late to slow it down and reverse its progress. Full article in the comments, covering the complete framework, the recycling myth, and how circular design applies to UX.

Google Analytics loads ~45 KB of JavaScript on every page of your website. Every visitor. Every page view. Every time. For a site with 100k monthly visitors, that's 4.5 GB of analytics JavaScript transferred per month. Just the script. Meanwhile, tools like Umami do the same job with under 2 KB. Plausible Analytics does it with under 1 KB. Both are open source. That's not a small difference. It's 20x to 45x less JavaScript, fewer network requests, faster pages, and less energy wasted on data most website owners never look at. Full breakdown in the comments.

86% of the top million websites don't have a skip navigation link. Press Tab on your website. Count how many times you have to press it before you reach your content, and this goes for every single page. When someone navigates your site with only a keyboard, they have to Tab through every single element in your header: logo, nav links, search bar, toggles ... before they reach the actual content. On a typical website, that's 20+ Tab presses / page. Who navigates with a keyboard? More people than you think.  - Users with motor disabilities who can't use a mouse  - Blind users who rely on screen readers  - People with temporary injuries: a broken arm or a wrist in a brace  - People who choose the keyboard over the mouse for speed A skip navigation link fixes this. It takes one anchor tag, a few lines of CSS, and a tabindex attribute. It's a Level A requirement under WCAG 2.4.1. It's referenced in the ADA, Section 508, and the European Accessibility Act. And yet only 13.7% of the top million websites have one. Of those that do, 10% are broken. Full article (link in the comments) covering: → What skip navigation actually solves → How it works → Common mistakes and how to avoid them → When you might not need one #accessibility #a11y #frontend

Only 13.7% of the top million websites have a skip navigation link. And 10% of those are broken. This is a feature that takes about 15 minutes to implement and directly improves the experience for every keyboard user. In this article, you'll find what skip navigation is, why it matters, how to add it to your site and mistakes to avoid. https://lnkd.in/djNWmFR4 #accessibility #a11y #frontend