toki! i'm lakuse. or jan Lakuse. or chelsea.
i am currently learning new skills in web accessibility/#a11y auditing and design. i'm contained by a place where two rivers meet and complicit in an exploitative settler colonial apparatus known as 'canada'
en/tok/eo
profile picture alt: bundled up in the cold, slight condensation on my glasses, masked up with a white N95
| pronouns | any |
| blog | https://chelsea11y.com/ |
It's been two years since the bump on my leg was lopped off and I swear to god, it said hello again today.
Sitting here at the library, I felt a familiar pain. I accepted it and we stayed together for a couple minutes. And then the pain said good-bye.
I had to scour through my photos to remember how long it has been. Two years, and two days.
This year I have done more walking than I thought possible.
I hope the pain was just from sewi and not the tumour growing back.
I was laid-off and am looking for a new role.
Working where design meets code is my jam. I am skilled at building accessible design system components, working with Web Components APIs, and creating scalable CSS architecture.
I work remotely from my home in Manitoba, Canada. 🇨🇦
Shares appreciated! #GetFediHired
Are you a megacorp making ‘things’?
If ‘the thing’ doesn’t meet WCAG at Level AA, don’t release ‘the thing’.
If ‘the thing’ is for the web platform (HTML, CSS, SVG, etc.), don’t propose ‘the thing’ until its WCAG conformance is sorted.
https://adrianroselli.com/2025/05/my-request-to-google-on-accessibility.html
Hey, Alphabet or Google or Chrome or whomever in that illegal monopoly continues to release things to the web platform that are full of accessibility barriers, I have what I think is a straightforward request. My Request Please, if your team cannot explain how the thing satisfies all WCAG Success…
compliance deadline for the Accessibility for Manitobans Act's IC standard kicks in for the private sector tomorrow.
websites of all businesses with a minimum of 1 employee are required to meet WCAG 2.1 Level AA if their websites are updated or if new websites are launched.
haven't seen much fanfare about it.
maybe i'll get myself a slurpy or something to celebrate.
@emmaDawsonDev this! not naming the WCAG SCs specifically makes it super hard for me to make notes and to apply the techniques they introduce in practical scenarios.
i still struggle to understand many of the ideas they share. for example, classifying a missing title attribute on an iframe as a bypass blocks failure? what?
I'm so bored of #accessibility and #inclusiveDesign conferences with obvious accessibility issues on their websites. Like this one, with submenus that can only be opened on hover/focus, four links in the main nav that have no accessible name, and 11 level 1 headings on the landing page.
Do better.
So the email that told me that I passed the #CPACC opened up with "Congrats, [Legal Deadname], you passed!"
The name on my candidate profile is not [Legal Deadname], so this was surprising. (They did have my legal deadname for ID verification at the testing centre).
I just wanted to share so that other folks can emotionally prepare for that to happen, because I wasn't.
like, *sucker punch* you passed, you trash!
They didn't apologize, by the way.
Nathan Knowler
Adrian Roselli, pH0
James Scholes