Frontend developer · Accessibility · Applied AI

Thoughtful interfaces. Built for people.

I’m Ignatius Seto. I build frontend interfaces with React, TypeScript, and web components. My focus: clear interactions, accessible experiences, and practical AI features that people can review and control.

01

Frontend engineering

Interfaces, component boundaries, and reliable states. Explore the React and web component projects below.

02

Accessibility

A focus on keyboard interaction, clear feedback, and documented testing. Project audits are the next evidence to publish.

03

Applied AI

The next experiment: reviewable, validated template drafts. The feature is planned; no model integration is claimed yet.

01 / Work

Selected work

Three projects, with room to show the decisions behind the code. Each case study separates the existing implementation from the next improvements.

Screenshots of local development versions; deployed demos may differ.

02 / Now

Now

A small, dated view of where my work is heading.

Direction reviewed:

Current direction

Turn Template Studio into a documented example of frontend engineering, accessibility, and useful AI.

Next evidence to publish

A baseline case study and a manual accessibility report before starting the AI-assisted drafting experiment.

Read case study

Template Studio / Roadmap

What comes next

A sequence of small releases. Each milestone is complete when its evidence is published, not simply when its code is written.

  1. 01

    Document the baseline

    Explain the editor’s user task, architecture, ownership, and limitations.

    Planned
  2. 02

    Test and improve accessibility

    Test complete keyboard and screen reader tasks; fix and retest findings.

    Planned
  3. 03

    Build reviewable AI drafts

    Validate structured output, show a draft preview, and require explicit application.

    Planned
  4. 04

    Evaluate and publish

    Publish quality, latency, cost, failures, and a dated maintenance note.

    Planned

03 / Notes

Engineering notes

Portfolio maintenance · Security and storage

Keeping offline storage bounded

I added browser security headers and limits to the portfolio’s offline cache: seven-day expiry, 40 entries, and a clear-data control. Expired entries are removed when the service worker next runs. Production dependency checks found no known vulnerabilities; an unpatched issue remains in development lint tooling. The behavior was verified locally. Hosting logs and manual screen reader review remain separate work.

Portfolio development · Decision note

A portfolio that shows its working

This update introduces multilingual pages, clearer project context, and a roadmap with evidence gates. Accessibility findings and AI results will be published after testing, rather than presented as finished work.

About this portfolio

This is a growing record of my work and learning. The project pages link to demos and source, explain planned improvements, and will accumulate dated evidence as the work develops.

Accessibility & verification

04 / Contact

Let’s talk about useful interfaces.

For professional conversations, connect with me on LinkedIn. For code and experiments, visit GitHub.