PinnedPublished inUX CollectiveWhy you should stop using placeholders in text boxesYour text boxes don’t need them — plus, they’re pointlessJan 29, 2024A response icon11Jan 29, 2024A response icon11
PinnedPublished inUX CollectiveHow a developer should read WCAGA humble guide through the standard reference for web accessibility.Dec 17, 2023A response icon2Dec 17, 2023A response icon2
PinnedPublished inUX Collective5 ways to improve Accessibility in 2024Ring in the new year with a more accessible webDec 26, 2023A response icon4Dec 26, 2023A response icon4
PinnedPublished inUX CollectiveNever, ever disable buttons — Why not?In this article, I’ll explain why you shouldn’t disable buttons and answer the inevitable objections. In a subsequent article, I’ll…Nov 5, 2023A response icon33Nov 5, 2023A response icon33
PinnedPublished inUX CollectiveWCAG 2.2 — It’s finally hereThe incredibly long-awaited WCAG 2.2 standards are now the “Proposed Recommendation” for W3C. This is the last type status before becoming…Aug 26, 2023A response icon4Aug 26, 2023A response icon4
Published inUX Collective2024 showed we’ve learned nothing from our past accessibility mistakesThe 2024 WebAIM Million results are in and… it’s not goodJan 5Jan 5
Published inUX CollectiveAccessible form validation from scratch — JavaScriptPart 5: Performing validationSep 8, 2024A response icon1Sep 8, 2024A response icon1
Published inUX CollectiveAccessible form validation from scratch: StylingPart 4: Focus management, offloading to CSS, hiding irrelevant elementsJul 22, 2024A response icon1Jul 22, 2024A response icon1
Published inUX CollectiveAccessible form validation from scratch — preparing for validationPart 3: Help text, instructions, required fields, and validation containersJul 2, 2024A response icon3Jul 2, 2024A response icon3
Published inUX CollectiveAccessible form validation from scratch — the form’s basic structurePart 2: The MarkupMay 5, 2024May 5, 2024