Found 235 bookmarks
Newest
How long until your website is accessible? - Karl Groves
How long until your website is accessible? - Karl Groves
Are you prepared for it to take 7 months (or more) to make your website accessible? If you're like me, you don't go to the store until you're ready to buy something. There's a difference between window shopping and shopping, and I usually don't go into the store and look at specific products until I'm
How long until your website is accessible? - Karl Groves
Semantic inline lists
Semantic inline lists
Sometimes, you want an list to be displayed in a line (like a nav menu) rather than vertically.ul class="list-inline" liMerlin/li liUrsula/li liRadagast/li /ul To do that, you typically set list-style to none, then style the list items with some padding in some way (using Flexbox or margins)..list-inline { list-style: none; margin-left: 0; /* This approach uses flexbox */ display: flex; align-items: center; column-gap: 1em; flex-wrap: wrap; } /* You could alternatively style the list items themselves This isn't needed if you use flexbox */ .
Semantic inline lists
Designing for accessibility beyond compliance
Designing for accessibility beyond compliance
Companies approach accessibility as a checklist of standards — but a client with disabilities showed me how to think beyond compliance.
Designing for accessibility beyond compliance
Don't disable buttons
Don't disable buttons
One of the most common accessibility issues I find (and fix) on client projects is dynamically disabled form buttons when a form is being submitted. Today I want to talk about why developers do it, why it’s bad, and what you can do instead. Let’s dig in! Why developers disable buttons Typically, I see the pattern used to prevent a form from being submitted a second time while waiting for the form is processed.
Don't disable buttons