Accessible block-based programming
Working on making Google Blockly more usable for blind and low-vision programmers.
Accessibility & HCI Researcher
I design and study technology that works for everyone — with a focus on blind and low-vision users, neurodivergent learners, and inclusive computing education.
This whole site is set in Atkinson Hyperlegible, a typeface built for low-vision readers. Try it: press Tab to see the focus ring.
Three threads, one question: how do we make computing usable for people it usually leaves out?
Making programming and everyday tools usable for people who are blind or have low vision.
How neurodivergent people, including those with ADHD, experience programming and computing.
The method behind both: studying how people really use technology, and designing for how they think and act.
Research and tools I have built and shipped.
Working on making Google Blockly more usable for blind and low-vision programmers.
A published Chrome extension that scans any site and reports a score for each disability profile, not one flat list. A local rules engine (mapped to WCAG 2.2) runs for free; an optional AI vision pass reads a screenshot the way a person sees it, catching text baked into images, meaning carried by colour alone, and mismatched alt text.
Ongoing research on how neurodivergent people experience programming. More to share soon.
Building tools that make learning to code more accessible. More to share soon.
Roles at the University of North Texas and beyond.
Across four courses I have learned to explain hard ideas plainly, meet students where they are, and turn feedback into better materials, the same instincts that drive my accessibility research.
I care most about the moment something finally clicks for a learner who was told the subject was not for them.
I am a PhD student in Computer Science, working at the intersection of human-computer interaction and accessibility. My research asks a stubborn question: the tools we build for programming, learning, and everyday web use assume a certain kind of user, so what does it take to make them work for everyone else?
That takes me from screen-reader semantics and audio interfaces, to the lived experience of neurodivergent students, to shipping real tools like AI-AC. I move between research methods and engineering because good accessibility needs both: evidence about people, and software that actually runs.
Open to research collaborations, PhD and industry conversations, and accessibility work.
Made it this far? Jump the blocks. It speeds up.