Personal site to archive digital accessibility-related learnings, mostly focused on technical implementations.
Over the past decade, Gerard has built and advised top-notch digital accessibility teams that have impacted millions of individuals worldwide. His experience ranges from supporting commercial financial applications responsible for transferring trillions of dollars globally, to enhancing accessibility on pre-Elon Twitter.
You don't have to be an accessibility expert to make your sites accessible. This course will help you attain the knowledge and skills to meet web accessibility guidelines and make your sites accessible to all users.
Set yourself above other front end engineers by learning the core concepts and rules needed to architect and build any accessible custom component with ARIA, in order to provide inclusive experiences for all users.
This course will teach you different techniques to efficiently and thoroughly test your websites for accessibility, using a combination of testing tools and various assistive technologies like screen readers.
It's time to shift accessibility past the designer-to-engineer handoff & expand further left, up, down, & right into other areas. This discussion is for Accessibility/DEI leaders, or anyone looking to move digital accessibility to higher levels.
I had the privilege of talking to the legend, Mike Paciello, about how accessibility can be a catlyst for positive change when it is prioritized.
Semantics are the backbone of digital accessibility. Not just for developers, this is also crucial for designers, especially when expected to provide accessibility annotations.
A massive amount of work has been done over the years to shift digital accessibility from an engineering afterthought to better planning in the design stages. However, there are lots of gaps remaining in other directions and areas to truly achieve full digital accessibility. It's time to move past the focus and responsibility being strictly on engineers.
A few months ago, I wrote about solving an issue with VoiceOver and list–style–type: none;. The response that I got was surprising, for a few different reasons.
With that bit of additional CSS, we are able to return the list semantics for VoiceOver users without needing to touch the markup.
UPDATE June 2018 — I would like to assume that, based on this post/ conversation, Google has updated the checkbox...