About me
I’m a front-end developer in Northumberland. I care about building software that works for everyone, including people who use a keyboard, a screen reader or a magnifier. I’m looking for a role in a development team where I can keep learning, contribute from day one and help make services more accessible.
Download my CV (PDF, 74 KB)MSc research
Why accessibility
I built WebAudit first, then used it as the basis of my dissertation: a controlled experiment with 35 developers on how the format of an accessibility report affects which problems get fixed. The paper is being prepared for publication.
I care about accessibility because nobody should be shut out of a service that everyone else can use because of a health condition they didn’t choose. If my work makes everyday life easier for people living with disability, that is work I want to do.
Accessibility is also about quality. A website that some people can’t use is a great design with poor delivery: if the person it was built for can’t use it, it has lost its value the moment it arrives.
How I’ve grown
Starting in IT support
I began in IT support and administration, where I automated recurring reports with Excel VBA and cut the time they took by 80%. It taught me to look for the repetitive problem behind the everyday one.
Front-end developer
I spent almost five years building production web applications in React and TypeScript in an Agile team with designers, back-end developers and project managers. I turned designs into accessible components, integrated REST APIs, helped cut an e-commerce platform’s page-load time by 60%, and mentored junior developers in debugging and Git.
MSc and research
I moved to the UK to study for an MSc in Computing at the University of Sunderland. For my dissertation I built WebAudit and ran a controlled experiment with 35 developers on how the format of an accessibility report affects what they fix.
How I work
I solve problems at the root
When my map project worked in development but showed blank tiles in production, I traced it to a background worker the build had broken and fixed the cause, not the symptom. In a commercial team, I spotted a production failure 48 hours before a client deadline, escalated it straight away and applied the fix, and we delivered on time.
I adapt quickly
I’ve moved country, gone back to study, and picked up new tools when a project needed them. I learnt SvelteKit by building and deploying a tested map application with it.
I work well with others
I’ve reviewed colleagues’ code, delivered work in sprints and mentored junior developers. I’d rather explain how I fixed something than just fix it.
I build for real people
In a customer-facing role alongside my studies, I help people who find self-checkout technology confusing. I see every day what happens when an interface leaves someone behind.
What I work with
Frontend
React, TypeScript, Next.js, JavaScript, Svelte 5 and SvelteKit, Vite, HTML, CSS, Tailwind CSS, Bootstrap
Backend
PHP (OOP, PDO), Python, Node.js and Express, REST APIs, MySQL, PostgreSQL, MongoDB
Quality and Tools
Git and GitHub, GitHub Actions CI, unit testing with Jest and Vitest, Jira, Agile Sprint, code review, mentoring, Vercel deployment and serverless functions, Render
Accessibility
WCAG 2.1 AA, semantic HTML, keyboard access, colour contrast, automated auditing, ARIA (live regions, aria-pressed), inclusive design
Looking ahead
I don’t want to stop at web development. In the long run I’d like to build assistive tools, and one day robotics, that use technology to make life easier for the people who need it most.
Outside work
Outside work, I love history, and spend a lot of my free time visiting historic places across Northumberland: the castles at Bamburgh and Warkworth, Lindisfarne on Holy Island, and the harbour at Amble. Closer to home, you’ll find me walking my dogs on the beach at Cambois or Newbiggin-by-the-Sea, or along the River Wansbeck. I also enjoy time with my family, playing football.