FRONTEND DEVELOPMENT & ACCESSIBILITY
KNOXVILLE, TN · OPEN TO REMOTE ROLES
A frontend developer with a designer’s eye and thirteen years of figuring things out.
I like making things work. Especially for the person trying to use them.
The problem, the people, and my part in it.
I worked on extensive WCAG remediation across healthcare websites, collaborating with accessibility auditors and reviewing automated Silktide findings. I helped identify false positives and confirm issues through manual testing, including keyboard navigation and contrast checks. In some cases, remediation required substantial changes to both the functionality and visual design of navigation and other complex components.
The work meant understanding the issue, working through a fix in the frontend, and checking the result. It helped me connect the technical details with what someone needs from the website.
WCAG remediation · Silktide · Keyboard testing · Contrast testing
I contributed to an accessibility working group that developed internal guidance, standards, and examples for developers, business analysts, QA, and content teams. The goal was to help teams apply those standards consistently throughout a project, with accessibility woven in from the beginning rather than bolted on at the end.
Over the years, I’ve also led small frontend teams, contributed hands-on implementation, reviewed code, and provided design feasibility feedback. I’ve used AI coding tools such as GitHub Copilot to streamline my workflow and speed up development.
Shared guidance · Code reviews · Technical leadership
A LITTLE SHOW, DON’T TELL
This form was built for this portfolio. Try moving through it with your keyboard, or submitting it empty.
// Excerpt from the signup form.
const nameMissing = submitted && !name.trim();
<input
ref={nameInput}
id="demo-name"
name="name"
autoComplete="name"
required
value={name}
onChange={(event) => setName(event.target.value)}
aria-invalid={nameMissing || undefined}
aria-describedby={nameMissing ? "name-error" : undefined}
/>
{nameMissing && (
<p className={ui.fieldError} id="name-error">
Please add your name.
</p>
)}An imaginary meetup. A real little component.
Nothing is sent or stored. Even the coffee is hypothetical.
A LITTLE MORE PLAY
Something a little more visual. Filter the ideas, switch the layout, and see the same components find their place.
Always curious.
A sample board inspired by the things I get into.
4 sample ideas · a bit of everything
Tinkering
Because organizing the filament is also a hobby, apparently.
Code
Reusable pieces that play nicely with the rest of the system.
Tinkering
For people whose idea of relaxing is optimizing a factory.
Code
A little room to experiment before calling it done.
Demo content. Actual interests. No extra browser tabs required.
type Filter = "Everything" | "Code" | "Tinkering";
const [filter, setFilter] = useState<Filter>("Everything");
const [view, setView] = useState<View>("grid");
const visibleProjects = projects.filter((project) =>
filter === "Everything" || project.category === filter
);
// One set of components. Two ways to see them.
<ul
data-view={view}
className={"group/board grid min-w-0 list-none gap-3.5 p-0 " + projectLayouts[view]}
>
{visibleProjects.map((project) => (
<ProjectCard key={project.id} project={project} />
))}
</ul>A BIT ABOUT ME
I came to frontend development through graphic design. I stayed for the problem-solving.
I started out as a graphic designer and taught myself development as the work called for it. I’ve spent the last decade in an agency environment, building healthcare websites alongside designers, project managers, business analysts, QA, and other developers. As clients took on more accessibility remediation over the last couple of years, that work became some of the most fulfilling I’ve done.
The best part of my career has been the people. I’ve made lifelong friends and learned so much from colleagues who still amaze me with how much they know.
As I look toward the next chapter of my career, I’d love to keep building on that experience. Making things more accessible, solving interesting problems, and working with people I can learn from and contribute alongside.
Outside of work, I’m into traveling, 3D printing, highland games, and games that somehow turn organizing complicated systems into recreation (Satisfactory, IYKYK). Apparently, the troubleshooting follows me home.
THE SHORT VERSION
I’m looking for fully remote digital accessibility or senior frontend roles, especially where making things accessible is part of the work.
2016–2026
Previously titled Lead Front-End Developer.
2013–2016
UI/UX layouts and website development with HTML and CSS.
The Art Institute of Atlanta · 2013