Accessibility Specialist & Web Developer · Shawnee, KS
I do accessibility work: remediation, consulting, and front-end dev built the right way.
I'm an accessibility specialist and front-end developer with low vision. I don't just test with assistive technology. I actually use it every day. That makes the work different than just checking boxes.
I got into accessibility because the web kept getting harder to use as my vision got worse. At some point I figured I'd rather fix it than just deal with it.
Everything in my portfolio was built accessible from the start. I've used WCAG, ARIA, and real screen reader testing on every project, not as an add-on at the end.
I work in both hand-coded and AI-assisted workflows and know how to get good results from either.
I'm job hunting right now. I'm most interested in accessibility remediation, consulting, or any engineering role where accessibility is the actual focus.
I also hold an AAS in Business Administration and am open to office operations, admin, or coordinator roles where my organizational background and tech skills are both useful.
Summer 2026
A multi-page film fan site I originally built as a college final project. I came back to it after learning accessibility properly and fixed every issue I found, bringing it up to WCAG 2.1 AA. Both versions are still live so you can see exactly what changed and why.
id="main-content" targets on every page,
enabling keyboard and screen reader users to bypass repeated headers (WCAG 2.4.1).
alt text on the logo image and added aria-label
to the logo anchor; added aria-label="Main navigation" to every <nav>
and aria-current="page" to active nav links (WCAG 1.1.1, 2.4.4).
<div>/<span> patterns in the film vitals
and cast list with proper <dl>/<dt>/<dd> elements so
screen readers expose the term and value relationships correctly (WCAG 1.3.1).
<blockquote> citation markup to use the correct
<footer>/<cite> nesting pattern; added aria-labelledby
to all <section> elements tied to their heading IDs; marked
decorative dividers aria-hidden="true" (WCAG 1.3.1, 4.1.2).
A medieval-themed Rock Paper Scissors game I built to be fully accessible. It's an actual playable game, but it's also meant to show what accessible front-end development looks like in practice. WCAG 2.1 AA, semantic HTML, ARIA, keyboard navigation, screen reader tested.
aria-live="assertive" for
real-time game feedback, and focus management throughout, all at
WCAG
2.1 AA.
An accessible recipe site built specifically with blind and low-vision users in mind. Every interaction, from browsing to cooking step by step, is designed to work with a keyboard or screen reader as the primary input.
prefers-color-scheme system detection), high contrast, and
larger text. Each toggle uses aria-pressed and saves to
localStorage so preferences persist across visits.
tabindex keyboard navigation for cooking steps, with
arrow keys, Home, and End so screen reader users can move through
instructions without losing their place in the list.
aria-live regions for real-time screen reader announcements
on step navigation and recipe search results.
A remediated three-page extract from a real 104-page Kansas state public health report (the PRAMS Surveillance Report). I scoped a representative sample, tagged and fixed it in Adobe Acrobat, then validated the result against the stricter PDF/UA standard rather than stopping at a clean Acrobat check.
Graduated May 2019
Graduated June 2025
I'm looking for accessibility work and happy to talk. Drop me a message.
Message sent!
Thanks for writing. I'll get back to you soon.