Hey Twitter friends! I’ve just been laid off and am seeking my next role. If you looking for someone skilled in open source, design systems, architecture, React component libraries, #a11y, design tooling, front end engineering, #JAMstack, docs, & public speaking, give me a shout.
This is awesome! I usually fall short in trying to succinctly describe what Audio Description is to a client, but thanks to @svinkle I shall use Peppa Pig clips as an example of how a narrator would describe action on a screen! scottvinkle.me/blogs/blog/access… #a11y r/t @abrightclearweb
I just finished an accessibility audit for a client and I decided to share some quick checks I perform in every site I audit and build.
Have fun <3
If you’re going to write about accessibility, don’t publish your post on @Medium. It’s not accessible, doesn’t offer alt text for images. Despite multiple requests over the years, @MediumSupport has no plans to improve accessibility on their site. #a11y #accessibility
If @____lighthouse tells us that our site is 100% accessible, it doesn’t mean it is. To prove that, I built the most inaccessible site possible with a perfect Lighthouse score. #a11y
I’m looking for a frontend developer who wants to work in an open and inclusive company in Amsterdam. We need someone who can take accessibility and the front-end to the next level for our corporate site and ehealth platform. #frontend #jobs #a11y minddistrict.homerun.co/front-en…
A <div> isn’t a button. No matter how many hoops you jump through to try and make it behave like one. Use native HTML elements to achieve your purpose. #a11y
A great series of articles on #a11y for web devs
The 11 in a11y stands for the number of times you have to tell developers that accessibility is important #a11y
Many #a11y issues can be fixed w/ Find & Replace. “Find” devs who take time to write accessible code to “Replace” the ones who don’t 😉