A decade spent making the invisible work.
Start with a browser extension that replaces the word "millennials" with "snake people" everywhere it appears online. It is a joke, and it has nearly two hundred stars on GitHub. It is also a tell: here is someone who treats the web as malleable, who reaches for code the way other people reach for a red pen, and who finds the medium itself funny. That instinct - to tinker, to rewrite, to ship - is the same one that now powers serious accessibility work at one of the largest software companies on earth.
Today Eric Bailey is a staff designer on Primer, GitHub's design system. The job is deceptively narrow and quietly enormous. Design systems are the component libraries that thousands of engineers pull from without thinking - the buttons, the menus, the file trees, the dialog boxes. Get accessibility right at that layer and it propagates everywhere, silently, into products built by people who will never read a WCAG success criterion. Get it wrong and you have shipped the same barrier ten thousand times. Bailey works at that leverage point on purpose.
He calls himself an "accessibility advocate and design systems wonk." The word "wonk" is doing real work there. It signals someone who genuinely enjoys the fine print - the difference between an ARIA role that helps and one that quietly breaks a screen reader, the gap between a component that looks done and one that actually announces itself to assistive technology. Much of his recent GitHub Blog writing is exactly this: bringing component behavior into parity with its coded counterpart, fixing how a file tree talks to a screen reader, reporting back on an experimental general-purpose accessibility agent and what it got wrong.
Inclusive by construction, not by apology
The throughline of Bailey's work is a refusal to treat accessibility as a thing you bolt on at the end. Inclusive design, in his telling, is not a compliance checkbox or a remediation invoice. It is the substrate. Build on it from the first commit and the result is straightforward solutions that meet people where they are - across practical, physical, cognitive, and emotional needs. Skip it and you are not building something edgy or new. You are just leaving people out and calling it innovation. Hence the line he keeps pinned to everything: if it's inaccessible, it is neither radical nor revolutionary.
His interests read like a manifesto for the unglamorous: semantics and interoperability, CSS architecture at scale, progressive enhancement, web performance, internationalization, and "working in the open." None of these trend. All of them are what makes a website actually usable by the person on a five-year-old phone, on a flaky connection, with a screen reader, in a language the designer never considered. Bailey has spent his career on the parts of the web that do not photograph well.
The keeper of The A11Y Project
If you have ever Googled a question about web accessibility, you have probably landed on The A11Y Project. It is a community-driven, open-source resource - part checklist, part encyclopedia, part front door for anyone trying to do better. Bailey became its lead redesigner and maintainer, and under his stewardship the project grew from a useful link into an authority. He added dark mode, reworked the accessibility checklist so people could actually find what they needed, and rebuilt the navigation. A handsome redesign by Tatiana Mac gave it a face; Bailey's maintenance gave it a spine.
Maintaining a popular open-source resource is thankless in a specific way. The work is continuous, the credit is diffuse, and the failure mode is silence - things just quietly stop working. Bailey kept it alive and current for years, which is its own kind of statement about what he values. He does the same on a smaller, stranger scale with a11y-webring.club, a webring for accessibility practitioners. A webring. In this economy. It is a deliberately retro format, a little wink at the early web, and a genuine community device that links practitioners to one another without an algorithm in the middle.
From a Boston studio to GitHub staff
Bailey came up through the craft. Earlier in his career he was a designer at thoughtbot, the Boston product studio known for its rigor and its writing culture - a place where blogging your process is part of the job. That ethos clearly stuck. With roughly a decade of cross-sector experience behind him, he blends hands-on front-end implementation with systems thinking, the rare combination of someone who can both write the markup and reason about the library it belongs to.
The writing is prolific and genuinely useful. More than two hundred articles across publications like CSS-Tricks, Smashing Magazine, and the GitHub Blog, most of them sitting at the intersection of semantics, accessibility, and usability. His open-source reference repos do the same job in a different format: accessible-html-content-patterns is a guide to getting HTML markup right, and a11y-syntax-highlighting offers accessible light and dark code themes - because if you are going to lecture people about contrast, your own code samples had better be legible. Both have hundreds of stars. He also contributes to MDN, the HTTP Archive, and the Disability Justice Project.
Generous on purpose
For someone whose subject can read as a list of rules, Bailey is conspicuously generous. He holds open office hours - virtual time offered to anyone who wants to talk through an accessibility problem. He runs his own Mastodon instance rather than renting attention from a big platform, and keeps a colophon and a public archive of his site, treating his personal website like a thing worth maintaining rather than a billboard. The pattern is consistent: build the resource, then give it away, then keep the lights on.
What makes him worth watching is not a single product or a viral moment. It is the accumulation - the articles, the maintained project, the patterns, the talks, the office hours, the webring - all pointed at the same stubborn goal. He wants accessible, inclusive design to be the default rather than the exception, and he is willing to do the slow, documented, unflashy work that actually moves a default. The snake-people joke and the staff-level standards work come from the same person, and that is the point. The web is for everyone, or it is broken. Bailey has decided which of those he is going to spend his time on.