3 followers
I'm Paul (he/him). I code for the browser and nodejs. I strive to further accessibility and Inclusive Design. I work to break down barriers that prevent people from having or loving a career in tech.
No doubt, if you've been following web standards development for the last few years, you've come across Web Components. Some folks will continue to dunk on Web Components for the lack of HTML Imports support. But I want to talk about the power of the...
Accessibility Review (Part 4): Screen Reader and Markup This post continues the accessibility review for the main page. You can get a nice write up of how to do this sort of review from Web Accessibility Initiative (WAI) Easy Checks. I generally save...
In Web Content Accessibility Guidelines (WCAG) principle terms, I reviewed Perceivable and Operable. I only covered the reader experience. I will need to repeat the process for the authoring experience. I will also want to check if author customizati...
Last time, I covered a quick keyboard review. I avoided some important bits like accessible name and role which come little later, when I review content. I'm impressed Hashnode responded positively to my review. Over the past few years, I grew weary...
This title first appeared with my article in 24a11y at the end of 2019. I picked that topic because it dealt with inclusivity, accessibility, and development but didn't step in legal mucky areas based on my work at the time. I'm going into more depth...
Hashnode promises to provide a clear, honest platform for teaching and learning code stuff. Sounds great. I own my content? I can write markdown? And I don't have to do the devops stuff? Sounds really great. But is it accessible? Accessibility Review...