Greetings! This is an invite to attend my thesis defense, which is a public, hybrid-friendly event. This event will not be recorded.

Details

April 29th, 2026 at 12pm noon Eastern Time

In person (NSH 4305) as well as on zoom (zoom info in calendar link below).

There will, of course, be refreshments and snacks at the event. Please feel free to invite others whom you believe might be interested in attending.

You may add this event to your calendar using this link.

If the google calendar link above doesn’t work, shoot me an email at fje@cmu.edu and I’ll send you the details!

⚠ NOTE:

Woah there folks! I guess google calendar has a limited number of people who can sign up to a calendar event. Use this zoom URL (intentionally not encoded as a link, to avoid bots) to join at noon EDT on April 29th:

https://cmu[DOT]zoom[DOT]us/j/2252051674?pwd=IWCIYbg6Y9cCKb9yMWc1K4eLUxOKHI.1&omn=96096322845&jst=2.

(Replace [DOT] with . in that link text, of course.)

The talk is expected to be 45-50 minutes, followed by anywhere between 15 and 30 minutes of questions. We will likely start a couple minutes after the hour (turns out many wizards are, in fact, often late). You’re welcome to attend any part of the event that interests you.

My thesis is titled, “Tool-making as an intervention on the accessibility of interactive data experiences” and focuses on my research studying tools at the intersection of data visualization and accessibility.

My committee

(This is my council of wizards, who will decide my fate. They are some of the most powerful wielders of magic in the world, in their respective disciplines!)

Dissertation Document

The dissertation draft is stored at this link.

What is a “thesis defense?”

This is a mystical event where a council of wizards decide if I am worthy of ascending to wizardhood myself. The process is relatively simple: I give an oral defense (a talk) regarding the contents of my dissertation, which is a document that represents the research journey I have taken during my PhD. At the end, the council (my “committee”) interrogates me with some questions, and then we open the floor for questions from anyone in attendance. After that, the public part of the event concludes (everyone is kicked out, including me) and the council makes their final decision. At the end, they let me know what they’ve decided. If they decide that I pass my defense, this is generally considered the point where I complete my PhD and become Dr. Frank, the Wizard 🎉 (we technically still have paperwork to do, but that is for the mystical bureaucracy).

Should you attend?

Hah! Have you been to one before? It’s a proper, ancient ritual. It can be neat to see a thesis defense at least once in your life. Will I get fried by a high level spell? Which magic will I choose to defend myself with? You won’t know unless you attend! But if you’ve been to several thesis defenses before, or you have no interest in the business of wizards, then you’re absolutely welcome to skip.

What is the thesis about?

My core argument (the “thesis statement” at the heart of the dissertation) is this: “This dissertation argues that the tools practitioners use to build interactive data experiences are themselves sites where accessibility barriers are produced, prevented, or alleviated for both end users and authors. This work contributes five tools—Chartability, Data Navigator, Softerware, Cross-perception, and Skeleton—that collectively center accessibility work on the empowerment of disabled and non-disabled practitioners across the full arc of evaluation, data navigation, analytical interaction, and personalization.” My work is interesting primarily because I argue that the work practitioners do is a rich site for research. I don’t just make a proverbial “hammer” but study what sort of hammers we need, whether hammers really work, and then how people actually use them.

Should you read my dissertation?

I highly doubt it! But that being said, there are some pretty fun parts in it, worth a skim (depending on who you are). For the most part, my dissertation is a “stapled paper” type of thesis, where the bulk of the document is comprised of my top-papers (that are the projects I personally led and executed) inserted without editing as the main “body” chapters of the dissertation. Then, the thesis itself generally has (up front) an acknowledgements section, introduction, overview of contributions, and (at the end) some kind of summary/discussion as well as a biographical sketch.

🤓 📚➟📖 I’ve generated miniature versions of my thesis document, to make reading easier! The basic document has 142 pages of content. That’s a lot! But I wondered… would more people actually look at my thesis if the page count wasn’t so intimidating? (See below sections for these mini-docs.)

Here is the link to the thesis itself.

That being said, many folks may want to check out one or some of the sections in the dissertation without having to read all of it. So here are some suggested readings for folks I know who are of different kinds:

1. Anyone who attends my thesis defense

Download my “personal-only” thesis doc! 📚 (142 pages) ➟ 📖 (6 pages)

Anyone who attends my thesis defense should probably check out my acknowledgements section. You’re probably in there! If you aren’t but think you should be, let me know!! I am terribly forgetful and would hate to leave out a friend, colleague, or supporter.

It also might be worth it to skim my biographical sketch, especially because the introduction to it pokes fun at many other bio sketches where people love to point out their origins as a genius child in high school who then ascended to harvard/MIT/etc; brilliant because of their own individual genius, of course. By contrast, I have largely been an unremarkable and unaccomplished person. I was a terrible student in high school and mostly didn’t “deserve” or earn the opportunities I had in life. And yet I did remarkable things regardless, mostly thanks to all the folks who have helped me out over the years. I hope my biography is a testament to the power of social support and that I have never really been a “main character” in my life. (Note that my own advisor joked that he wished he had paid more attention to my PhD application, because my undergraduate closed and I did poorly in high school. I probably shouldn’t have been admitted to CMU, haha. He is certainly from a “real” academic and technical pedigree; he would know!)

2. You are a technical practitioner of some kind (non-researcher)

Download my “for the toolmakers” thesis doc! 📚 (142 pages) ➟ 📖 (7 pages)

I’d recommend that anyone technical (whether a designer or developer) checks out 1.2, 9.1, and 9.3. Pretty much everyone who works with “tools” (including AI/genAI/LLM/ML tools) should check those out (as well as my blog post on tools.)

You are specifically an accessibility practitioner

Download my “accessibility practitioner” thesis doc! 📚 (142 pages) ➟ 📖 (50 pages)

Definitely read 1.1 of the introduction because it has a way of thinking about accessibility work that everyone doing any accessibility work should consider: is “accessible visualization” really an oxymoron?

I think that academic papers can be awkward to suggest, but I genuinely think that if you check out any main chapter, you should read the one on skeleton, since it is about making accessibility work more accessible for sighted practitioners. A lot of accessibility work is (ironically) inaccessible! We should change that. Chartability is another good read along those lines, too.

You are specifically a visualization practitioner

Download my “visualization practitioner” thesis doc! 📚 (142 pages) ➟ 📖 (46 pages)

Absolutely read 1.1 of the introduction: is “accessible visualization” really an oxymoron? I wrote that with visualization folks in mind. There have been some tricky, even subtle ableism in our field that I wanted to clear up before outlining my work. The part where I engage misconceptions about accessibility is worth reflecting on as well as the part where I outline what visualization is actually about.

I think that academic papers can be awkward to suggest, but I genuinely think that if you check out any main chapter, you should read the one on skeleton, since it is about making accessibility work more accessible for sighted practitioners. Chances are: that’s you. I also think that softerware should be a chapter that anyone who builds or designs visualization systems and tools should think about: how do you enable end user personalization?

3. You are an HCI/HAI/visualization/accessibility/”tools” researcher of some kind

Download my “summarized for researchers” thesis doc! 📚 (142 pages) ➟ 📖 (7 pages)

All researchers will probably benefit from at least reading chapter 3 (my overview of contributions) and my final section, who is responsible for repair? Read those in addition to any subsection below that applies to you:

You are an accessibility researcher

Download my “accessibility researchers” thesis doc! 📚 (142 pages) ➟ 📖 (16 pages)

I think the introduction (sections 1.1 and 1.2) as well as the conclusion’s sections on what is a tool? (9.1) and applied accessibility research (9.2) are especially valuable, and hopefully provocative. I’ve done a good job if a few people from the ASSETS community are flustered about 9.2, in particular.

Download my “accessibility researchers who care about practitioners” thesis doc! 📚 (142 pages) ➟ 📖 (104 pages)

You might want to do more practitioner-focused work (or have an interest in this), in which case I’d recommend skeleton, chartability, and softerware especially. Read data-navigator if you want to get mad that I didn’t run a user study to validate our system (challenge mode: think about whether this kind of work is valuable or not in/for accessibility research as a broader discussion).

You are a visualization researcher

Download my “summary for visualization researchers” thesis doc! 📚 (142 pages) ➟ 📖 (17 pages)

Absolutely read 1.1 of the introduction: is “accessible visualization” really an oxymoron? I wrote that with visualization folks in mind. There have been some tricky, even subtle ableism in our field that I wanted to clear up before outlining my work. The part where I engage misconceptions about accessibility is worth reflecting on as well as the part where I outline what visualization is actually about.

But “visualization researcher” is a funny categorization to me. Visualization research has cognitive and perceptual scientists (our “real” science-doers), feminist and critical theorists, ethicists, interaction designers, system-builders, graphic designers, data people, and applied researchers. My thesis is mostly written from the perspective of system-building and a little bit of interaction design.

Cognitive/perception vis researchers

Download my “perception+vis” thesis doc! 📚 (142 pages) ➟ 📖 (38 pages)

If you’re into cognitive and perceptual science, you’ll probably get little of value from this thesis (perhaps other than just to reflect on someone else’s very different methods: building systems and doing mostly qualitative work). You might enjoy cross-perception, but I have a feeling it is too technically-focused to really pique the interest of a “pure” cog/perceptual scientist.

Critical/ethics/humanities vis researchers

Download my “sexy murder poet” thesis doc! 📚 (142 pages) ➟ 📖 (18 pages)

That being said, the slightly-more-critical parts of my dissertation (which I enjoy the most) are found in the introduction (1.1/1.2) and discussion sections (9.1-9.3). That might be good for the critical folks, theorists, ethicists, humanities-oriented researchers, and proper “sexy murder poets” of the field to check out.

Systems/tools for vis research

Download my “systems+vis” thesis doc! 📚 (142 pages) ➟ 📖 (79 pages)

System-builders might get value from reading data navigator, skeleton, and softerware. Maybe the whole thesis, too, to be honest. I’m this kind of researcher, so it’s all generally written with myself in mind.

Data-focused vis researchers

Download my “data structures+vis” thesis doc! 📚 (142 pages) ➟ 📖 (40 pages)

Data people might really love data navigator, specifically if you enjoy data structures and graph theory. It’s graph theory, but for an HCI/systems/UI software problem!

Interaction and input design vis researchers

Download my “interaction+vis” thesis doc! 📚 (142 pages) ➟ 📖 (38 pages)

Interaction design researchers might really enjoy the hardware work I did in cross-perception. You folks love when electronics and hardware work sneaks in. And some of our field’s existing hardware work actually has potential for accessibility work!

Graphical design vis researchers

Download my “design+vis” thesis doc! 📚 (142 pages) ➟ 📖 (60 pages)

Purely graphic designers should probably check out chartability, to apply to your own work. Skeleton isn’t a bad chapter either, since the whole idea is that we apply visualization to an accessibility problem.

Practitioner/applied vis researchers

Download my “practitioners+vis” thesis doc! 📚 (142 pages) ➟ 📖 (76 pages)

And folks who work with practitioners at all (in applied contexts) will probably enjoy chartability, softerware, and skeleton, in particular.

You are a visualization and accessibility researcher

Download my “accessibility+vis (latest-only)” thesis doc! 📚 (142 pages) ➟ 📖 (63 pages)

You probably know my work from the main chapters (my 5 papers), but you can skim them if you want. There are some exciting new pieces in there too, that I have recently submitted for publication. You might find chapters 6 (skeleton) and 7 (cross-perception) the most interesting, as they are my latest pieces. You might also benefit from at least skimming my introduction section 1.1: is “accessible visualization” really an oxymoron?

I’m tempted to say you should just read the whole thesis though. You’re probably among the two dozen people in the world at our intersection and if you aren’t familiar with my work or why I do it, then it’s certainly going to be enlightening as a reflection on your own work.