Accessible program operations for mission-driven teams

Small Appsfor OrganizationsDoingBIGThings

I build focused, accessible tools for faith communities, nonprofits, schools, and creative programs that need better registration, waitlists, check-in, attendance, reminders, and follow-up without adopting a giant platform.

A few pilot spots are open for teams with a real workflow problem and a willingness to test the first version honestly.

Quick first version
small enough to build quickly, useful enough to try with your real team
Accessibility first
built for keyboards, screen readers, contrast, clarity, and real people
Built beside your tools
focused enough to fit around your current forms, databases, and routines

Registration, check-in, attendance, reminders, and follow-up in one calmer path

Built personally by a legally blind engineer who treats accessibility as craft, not garnish

Pilot-friendly scopes for small teams that need relief before they need another platform

The workflow problem is usually humble: a form over here, a spreadsheet over there, reminders sent by memory, and attendance reconstructed after the room is already empty. SethBuilds turns that fragile chain into a small tool your team can actually keep using.

What I build best.

The strongest projects usually start with one painful workflow: getting people registered, checked in, counted, reminded, and followed up with clearly and accessibly.

Registration and waitlists

Public signups, capacity limits, waitlists, confirmation notes, and the tiny details that help people show up prepared.

Event and class check-in

QR codes, name search, walk-up arrivals, and check-in screens that volunteers can understand without a training saga.

Attendance and follow-up

Clean attendance records, no-show lists, exports, and next-step reminders that keep care from leaking through the cracks.

Volunteer coordination and reminders

Rosters, role preferences, swaps, reminder messages, and small coordination tools for people doing a lot with a little.

Accessible resource libraries

Searchable lesson pages, workshop materials, event resources, and archives built with headings, keyboard paths, and clarity from day one.

Small internal dashboards

Focused dashboards for program status, attendance exports, lightweight reporting, and the handful of numbers your team actually uses.

Every app I build is accessible by default because I use a screen reader myself. Keyboard navigation, screen reader support, and proper contrast aren't afterthoughts. They're how I work.

Selected projects

Real projects with a clear job to do.

These are live tools built around specific workflows, not generic mockups. Phase two can turn them into fuller case studies; phase one keeps the proof honest and qualitative.

Accessibility guidance tool

A11y Garden

Accessibility scanning and guidance designed to help teams find, understand, and fix WCAG issues.

Problem: Accessibility issues are hard to triage when reports are too technical or disconnected from the page.

Solution: A practical scanner and guidance flow that helps teams understand what needs attention next.

  • Centers WCAG guidance in plain language
  • Supports practical review instead of one-off scores
  • Reflects accessibility-first product judgment
Accessible learning app

Curio Garden

An accessibility-first Wikipedia listening app for turning curiosity into structured, navigable audio.

Problem: Long-form reading is not always the easiest way to explore, especially when listening would fit the moment better.

Solution: A structured audio-first exploration tool that turns curiosity into navigable listening.

  • Designed for screen-reader-aware navigation
  • Turns dense public knowledge into calmer sessions
  • Built as a focused alternative to bloated learning tools

Simple from start to finish.

Map the mess

Name the workflow that keeps breaking.

We start with who you serve, what you use now, where the handoffs fail, and what a calmer week would look like.

Build the useful bit

Ship a first version people can actually try.

The scope stays small on purpose: one public flow, one back-office view, one practical path from signup to follow-up.

Pilot and tune

Use it with real people, then refine.

Pilot feedback shapes the next pass. You keep the tool and the data, with optional hosting and support if you want me nearby.

Good fit / pilot spots

Best for one workflow that keeps stealing time.

SethBuilds is probably a good fit if your current tools almost work, but your team still loses time every week to manual signups, reminders, attendance cleanup, or follow-up.

  • You can name the workflow and the people who use it.
  • You want a simple first version before a big platform decision.
  • You care about accessibility from the first sketch, not the last audit.

A few pilot spots are reserved for organizations willing to test early and give honest feedback. Paid projects are scoped after discovery; optional hosting and support can be added if you want me to keep the lights on and the gears oiled.

Talk through your workflow wishlist

Who builds this stuff?

Seth Wilson holding a bass guitar

Hi, I'm Seth Wilson. I'm a legally blind software engineer living and working out of Tyler, Texas. With over eight years of full-stack experience — web front-ends, databases, APIs — I strive to bring a spark of joy and curiosity to everything I create.

I try not to take this life's rich tapestry for granted: the people who show up, the communities that make room, the small acts of care that quietly change someone's day. That gratitude is what drives this practice. I build for faith communities, educational institutions, nonprofits, and creative organizations because you're often carrying the work that matters most with the fewest extra hands.

Because I'm legally blind, everything I build is accessible from the ground up — it's not an afterthought. And I don't outsource or reach for off-the-shelf templates. Every project is artisanally crafted to fit your needs.

Workflow wishlist

Tell me what your current tools cannot quite do.

Start with the messy truth: who you serve, what is breaking, what you use now, and what better would look like. If a pilot makes sense, we can scope a small first version around the highest-friction path.

Start here

Share the workflow wishlist.

The project form will collect the lean details: Name, Email, Organization, Sector, Workflow problem, Current tools, Timeline, and Pilot interest.

The project form is still being connected. For now, send the workflow details by email and I will follow up personally.

  • Name
  • Email
  • Organization
  • Sector
  • Workflow problem
  • Current tools
  • Timeline
  • Pilot interest
Email hello@sethbuilds.app
Prefer a call?

Book time to talk it through.

The booking calendar will sit beside the form once it is ready. Until then, email is the fallback path.

The booking calendar is still being connected. For now, email me and we can find a good time to talk it through.

  • Name
  • Email
  • Organization
  • Sector
  • Workflow problem
  • Current tools
  • Timeline
  • Pilot interest
Email hello@sethbuilds.app