How I design
Accessibility is not a checklist I run at the end. It is the brief itself: if someone cannot reach it, read it, or understand it, it is not designed yet.
Everyone means everyone
Most products are built for the person holding the mouse, in good light, with time to spare. I design for the person using a keyboard, a screen reader, a cracked phone on a moving bus. When it works for them, it works better for everyone else too.
Behaviour before decoration
Cognitive science taught me that attention is a budget and memory is unreliable. So structure comes first: what can be reached, in what order, with how much effort. Colour and type arrive only once the page makes sense in black and white.
The path is the product
A keyboard path is designed, not inherited. Every route a mouse can take gets a keyboard twin, every screen reads aloud in the order it appears, and nothing important hides behind a hover.
Show the reasoning
Every decision on this site has a why written next to it, in plain language. If I cannot explain a choice to someone outside design, the choice goes.
Honesty is an accessibility feature
I claim only what I have measured, promise only what I can keep, and leave the process visible - wireframes, margin notes and all.
How I designed my Portfolio
These are the actual wireframes behind the site you're using - orange notes and all. Walk them as a click-through prototype, or lay every page out side by side.
19 words, real sentence - recruiters scan. plain language is an accessibility feature too (WCAG 3.1)
folders = your 4 buckets, yellow first - it's the thesis. black-on-yellow ≈ 12:1 contrast, and each folder is ONE link (one tab stop, not five)
reading tabs (Aa / ◐ / ≡) on the right edge - real buttons with aria-pressed, ≥44px, they remember your choice
follow a link, like a visitor would: