What I bring to
any
project
Twenty years building for the web means I've seen most of the problems before. Accessibility, design systems, JavaScript architecture, SEO, analytics, UX, and federal compliance aren't separate disciplines to me. They're just the job.
Start a conversationTypes of work
Accessibility Audit
A full WCAG 2.1 AA and Section 508 review of your interface. Not a Lighthouse report with a bow on it. Manual testing, screen reader evaluation, keyboard navigation review, and a prioritized remediation list you can actually work from.
- ▸Manual testing across NVDA, VoiceOver, and JAWS
- ▸WCAG 2.1 AA and Section 508 gap analysis
- ▸Prioritized, dev-ready remediation list
- ▸Documentation suitable for ATO / compliance packages
JavaScript Development
Vanilla-first, framework-optional. Browser APIs over build tools. Native before npm. I build things that are fast, maintainable, and don't rot when a dependency drops a major version.
- ▸Vanilla JS utilities, widgets, and interactive components
- ▸npm package authoring and scoped library publishing
- ▸Framework evaluation and migration support
- ▸Code review and dependency audits
Design System Consulting
Whether you're starting from scratch, inheriting a mess, or trying to get USWDS to do something it wasn't obviously designed to do, I've been in all three situations and can shorten the timeline considerably.
- ▸Design token architecture and governance
- ▸Component library structure and API design
- ▸USWDS customization and extension patterns
- ▸Documentation and adoption strategy
SEO & Performance
Core Web Vitals, semantic markup, structured data, and analytics setup. Most SEO problems on the technical side are HTML problems. I fix them at the source, not with workarounds.
- ▸Core Web Vitals audit and remediation
- ▸Semantic HTML, structured data, and schema markup
- ▸GA4 and GTM setup, audit, and event tagging
- ▸Page speed and load strategy optimization
USWDS Implementation
USWDS is the right answer for federal web work, but the gap between "installed" and "actually compliant and maintainable" is real. I can get you across it, whether you're on Drupal, a static site, or something custom.
- ▸USWDS 3.x setup and configuration
- ▸Drupal, static site, and custom framework integration
- ▸Theme layer and custom token mapping
- ▸Migration from USWDS 2.x
Front-end Architecture
Code review, tech stack decisions, build tooling, or a second opinion before something becomes load-bearing. Useful for teams that want a senior eye on a direction before they're too far down the road to change it.
- ▸Tech stack and framework evaluation
- ▸Code review and architecture audit
- ▸Build tooling and CI/CD pipeline review
- ▸Hands-on implementation for short-term gaps
What working together actually looks like
No onboarding tax
Federal web context isn't something you can teach in a kickoff call. I already know the acronyms, the compliance requirements, and why the procurement process works the way it does.
Direct, not delegated
You're not buying access to a firm that assigns a junior resource. You're working directly with me. That means faster feedback, fewer handoffs, and no translation layer.
Written deliverables
Audits, recommendations, and architecture notes come as actual documents your team can reference and act on, not slide decks or verbal summaries that evaporate after the call.
Have a project in mind?
Tell me what you're working on. If it's a good fit, I'll say so. If it isn't, I'll tell you that too.