As a designer, I care about this site being usable by as many people as possible, regardless of ability or the device they browse with. I'm actively working toward meeting WCAG 2.1 Level AA guidelines, and accessibility is treated as part of the design process here, not an afterthought bolted on at the end.
What's already in place
Descriptive alt text on every image, so screen reader users get the same context a sighted visitor gets from looking at the work.
Keyboard-operable navigation, the mobile menu can be opened, used, and closed without a mouse, with its open/closed state announced via aria-expanded.
Semantic HTML structure, proper landmarks (nav, main, footer) and heading order, so the page makes sense when read by assistive technology rather than just when looked at.
Reserved image dimensions so pages don't jump around as content loads, useful for anyone with motion sensitivity or a slower connection.
Decorative motion is muted and looped quietly in the background rather than autoplaying with sound or demanding attention.
Implementation
Recent work here has mostly been about keyboard use and layout stability, added a skip-to-content link, made focus states more visible, and animations now respect it when someone's system is set to reduced motion.
July 6, 2026
Fixed focus management within the case study drawer views. Keyboard users can now navigate through project details and cleanly close out modules without losing track of their selection indicator.
July 4, 2026
Added proper ARIA states to the mobile nav menu, and made sure the background animation turns off automatically when reduced motion is on.
Compatibility
This site is built with standard, semantic HTML and CSS and is tested to work with recent versions of major browsers (Chrome, Firefox, Safari, Edge) as well as common screen readers.
Feedback
If you run into an accessibility barrier anywhere on this site, I want to know about it. Reach out at muhammadsoheb91@gmail.com and I'll aim to address it directly.