A11y Report Card
Paste a URL and get a plain-English accessibility report card with a score, letter grade, WCAG-style issue buckets, affected elements, and suggested fixes. Deployed here with a static demo fallback for portfolio hosting.
I’m Ereg Erig, a Python-focused software engineer and CS student aiming for AI engineering and agent-development roles. I build clean backend APIs, RAG workflows, tool-calling systems, eval-ready product demos, dashboards, and full-stack tools that are easy to use and maintain.
These featured projects are live, portfolio-ready demos: an accessibility report card, a scroll-driven data essay, and a budget-first recipe planner.
Paste a URL and get a plain-English accessibility report card with a score, letter grade, WCAG-style issue buckets, affected elements, and suggested fixes. Deployed here with a static demo fallback for portfolio hosting.
A scroll-driven data essay showing that chocolate, not sugar, is the stronger signal in candy popularity. The chart transforms as readers move through the story.
Choose a weekly dinner budget and diet preference, then get recipes ranked cheapest-first with an under/over budget receipt. Deployed with clearly labeled demo data on static hosting.
An interactive study workspace with lessons, IOS-style command practice, subnet drills, quizzes, bookmarks, saved progress, Markdown notes, a timed mock exam, and an AI tutor roadmap.
I’m strongest where backend, data, UI, and AI workflow design meet: making the system understandable, testable, useful, and safe for the person opening it.
Designing FastAPI and Django services, REST endpoints, auth-aware flows, background jobs, and clean integration boundaries.
Turning messy real-world tasks into schemas, state, validation rules, PostgreSQL tables, and useful domain objects.
Building React, HTMX, and responsive interfaces that make workflows obvious without overloading the page.
Designing LLM features with intent routing, retrieval, tool calling, guardrails, evaluation checks, and clear human approval boundaries.
I like the parts of the stack where things either work or they don’t: data models, API contracts, AI workflow boundaries, state transitions, integration edges, and product details that make a tool feel reliable.
My favorite projects start with a real annoyance — school planning, budget tracking, AI assistants, study prep — and end as something usable enough to click, test, and improve.
If you’re hiring, collaborating, or curious about one of the projects, email is the fastest place to start. I read everything.