Role

Product Design Intern

Skills and Tasks

Accessibility

User Research

Instructional Design

Figma Component Design

Conference Branding

Cross-team Collaboration

Tools

Figma

Duration

June 2025 - August 2025

Embedding Accessibility into Design

Embedding Accessibility into Design

As a Design Systems intern at State Farm, my main project focused on a big challenge: embedding accessibility into the UX design process. I led user research to uncover current gaps, then translated findings into actionable solutions. The outcome was a structured approach to make accessibility a consistent practice, including training resources, a simplified guideline system, and a framework for integrating accessibility into every stage of the design process.

Alongside this project, I also contributed to the design system by building components, designed branding concepts for two internal conferences (with my design selected by senior designers to move forward), and participated in Hack Day where my team won first place in the low-code category and advanced our idea into development.

Accessibility

Accessibility

Accessibility

The Problem

Accessibility was often treated as an afterthought rather than part of the design process. Designers lacked clear guidance, consistent tools, and accountability, which meant accessibility efforts were uneven across teams. This created usability risks for customers and costly rework for teams later in development.

The Problem

Accessibility was often treated as an afterthought rather than part of the design process. Designers lacked clear guidance, consistent tools, and accountability, which meant accessibility efforts were uneven across teams. This created usability risks for customers and costly rework for teams later in development.

Surveying Designers

Surveying Designers

Before I joined, 85 out of 120 designers responded to an enterprise survey, which is a strong signal that designers cared about solving accessibility challenges. I synthesized the results in FigJam, clustering related responses with sticky notes, and tested AI's ability to surface findings compared to my own. From this process, I surfaced four key themes:

Survey Insight 1

Perception of adequacy.

Many assumed the design system already handled accessibility.

“I like to think we already have accessibility optimized and don’t give it a second thought.”

Survey Insight 1

Perception of adequacy.

Many assumed the design system already handled accessibility.

“I like to think we already have accessibility optimized and don’t give it a second thought.”

Survey Insight 1

Perception of adequacy.

Many assumed the design system already handled accessibility.

“I like to think we already have accessibility optimized and don’t give it a second thought.”

Survey Insight 2

Lack of clear guidance

Designers weren’t sure what accessibility checks were their responsibility.

“It is not clear what we should be checking for, and how or what degree to investigate.”

Survey Insight 3

Competing priorities

Fast timelines meant accessibility was deprioritized.

“Gets lost in the shuffle of other priorities and not all units think their products need to focus on accessibility.”

Survey Insight 4

Knowledge gap

Designers believed they “knew” accessibility but often missed issues or weren’t aware of resources.

“I feel most of what I am designing has passed accessibility concerns.”

Survey Insight 2

Lack of clear guidance

Designers weren’t sure what accessibility checks were their responsibility.

“It is not clear what we should be checking for, and how or what degree to investigate.”

Survey Insight 2

Lack of clear guidance

Designers weren’t sure what accessibility checks were their responsibility.

“It is not clear what we should be checking for, and how or what degree to investigate.”

Survey Insight 3

Competing priorities

Fast timelines meant accessibility was deprioritized.

“Gets lost in the shuffle of other priorities and not all units think their products need to focus on accessibility.”

Survey Insight 3

Competing priorities

Fast timelines meant accessibility was deprioritized.

“Gets lost in the shuffle of other priorities and not all units think their products need to focus on accessibility.”

Survey Insight 4

Knowledge gap

Designers believed they “knew” accessibility but often missed issues or weren’t aware of resources.

“I feel most of what I am designing has passed accessibility concerns.”

Survey Insight 4

Knowledge gap

Designers believed they “knew” accessibility but often missed issues or weren’t aware of resources.

“I feel most of what I am designing has passed accessibility concerns.”

6 Interviews with Designers

6 Interviews with Designers

The survey gave us a broad view of accessibility challenges, but I wanted to understand how it fit into designers’ processes. I worked with the enterprise research team to refine an interview guide and conducted 1:1 interviews across teams, which uncovered deeper insights into daily workflows, pain points, and opportunities to better embed accessibility.

I conducted the interviews myself, keeping them calm and conversational while asking strong follow-up questions, something my managers specifically highlighted as a strength. Then, I affinitized the interview data by reviewing transcripts, capturing key points on sticky notes, and clustering them into themes. This process surfaced four key insights.

"I think about my parents struggling with tech, and that drives me to make sure our tools work for everyone."

Interview Insight 1

Designers are motivated to address accessibility.

Many have family connections or past roles tied to accessibility.

"I genuinely want to do right by the users. Making things accessible means including people who are often left out, and that’s a responsibility I take seriously."

"I think about my parents struggling with tech, and that drives me to make sure our tools work for everyone."

Interview Insight 1

Designers are motivated to address accessibility.

Many have family connections or past roles tied to accessibility.

"I genuinely want to do right by the users. Making things accessible means including people who are often left out, and that’s a responsibility I take seriously."

"I think about my parents struggling with tech, and that drives me to make sure our tools work for everyone."

Interview Insight 1

Designers are motivated to address accessibility.

Many have family connections or past roles tied to accessibility.

"I genuinely want to do right by the users. Making things accessible means including people who are often left out, and that’s a responsibility I take seriously."

"Most of the time, I’m focused on color contrast and font sizes because that’s what I understand and have time to check."

Interview Insight 2

Designers only check color contrast.

In practice, their checks stop at color contrast, which some see as the beginning and end of accessibility.

“Detailed checks like keyboard navigation usually fall by the wayside."

"Most of the time, I’m focused on color contrast and font sizes because that’s what I understand and have time to check."

Interview Insight 2

Designers only check color contrast.

In practice, their checks stop at color contrast, which some see as the beginning and end of accessibility.

“Detailed checks like keyboard navigation usually fall by the wayside."

"Most of the time, I’m focused on color contrast and font sizes because that’s what I understand and have time to check."

Interview Insight 2

Designers only check color contrast.

In practice, their checks stop at color contrast, which some see as the beginning and end of accessibility.

“Detailed checks like keyboard navigation usually fall by the wayside."

"Sometimes designs just get handed off without anyone checking for accessibility until after development, which is way too late."

Interview Insight 3

No consistent or mandatory review process.

They don’t go further because there are no clear requirements, no incentives, and no mandatory review processes.

"There’s no formal step for accessibility reviews, it’s more of an optional ‘nice to have’ if time permits."

"Sometimes designs just get handed off without anyone checking for accessibility until after development, which is way too late."

Interview Insight 3

No consistent or mandatory review process.

They don’t go further because there are no clear requirements, no incentives, and no mandatory review processes.

"There’s no formal step for accessibility reviews, it’s more of an optional ‘nice to have’ if time permits."

"Sometimes designs just get handed off without anyone checking for accessibility until after development, which is way too late."

Interview Insight 3

No consistent or mandatory review process.

They don’t go further because there are no clear requirements, no incentives, and no mandatory review processes.

"There’s no formal step for accessibility reviews, it’s more of an optional ‘nice to have’ if time permits."

"Designs are often interpreted differently because we don’t have enough direct communication about accessibility needs."

Interview Insight 4

Disconnected workflows can cause improper implementation.

Much of the responsibility is assumed to fall on developers, which leads to misalignment, rework, and costly design changes.

"Accessibility becomes someone else's problem once we hand off the designs."

"Designs are often interpreted differently because we don’t have enough direct communication about accessibility needs."

Interview Insight 4

Disconnected workflows can cause improper implementation.

Much of the responsibility is assumed to fall on developers, which leads to misalignment, rework, and costly design changes.

"Accessibility becomes someone else's problem once we hand off the designs."

"Designs are often interpreted differently because we don’t have enough direct communication about accessibility needs."

Interview Insight 4

Disconnected workflows can cause improper implementation.

Much of the responsibility is assumed to fall on developers, which leads to misalignment, rework, and costly design changes.

"Accessibility becomes someone else's problem once we hand off the designs."

Designers Need Structure

The research made it clear: designers cared, but lacked clarity on where accessibility fit, how to apply it, and what they were responsible for. Without structure and leadership support, accessibility was left until the end of the cycle, where fixes were harder, slower, and more expensive.

Designers Need Structure

The research made it clear: designers cared, but lacked clarity on where accessibility fit, how to apply it, and what they were responsible for. Without structure and leadership support, accessibility was left until the end of the cycle, where fixes were harder, slower, and more expensive.

Learning First-Hand

Learning First-Hand

When I started, I only knew accessibility at a surface level. To design credible solutions, I dove in and became certified in Deque’s Fast Track to Accessibility for Designers, read articles by experts like Stephanie Walter and NN/g, and researched competitor design systems.

Making Accessibility Accessible: Guidelines for Designers

Making Accessibility Accessible: Guidelines for Designers

The first step was to solve the knowledge gap. Designers need to understand all aspects of accessibility before they can integrate it into their process. So, I created guidelines that explain accessibility for designers, to align them on what needs to be checked and achieve a shared understanding.

Features


  1. Breaks down WCAG into plain language and follows the same structure incase designers want to cross-reference.

  2. Uses “do/don’t” image examples that use the State Farm design system.

  3. Explains how to annotate designs for accessibility.

  4. Matches the visual style and format of existing design system component guidelines to maintain consistency.

  5. Lives in a place designers reference often.

Creating the Guidelines


To build the guidelines, I studied accessibility resources from IBM, Google, and Apple for inspiration on visuals and examples. I also sourced real examples from State Farm products and internal sites. I referenced Stark’s WCAG Simplified and Stephanie Walter, and used AI to rewrite WCAG rules into accurate, concise, easy-to-understand summaries.

Reviewed by the Accessibility Team


These guidelines were reviewed by the accessibility team, who provided specific feedback to both the text and images to ensure accuracy, which I revised in the final guide.

Testing the Guidelines with 7 Designers

Testing the Guidelines with 7 Designers

I tested the guidelines with seven designers to assess clarity and usability. Partnering with the Research Team, I refined my testing plan and script. I also created a demo exercise using a State Farm page with built-in accessibility errors, allowing us to see how effectively the guidelines supported designers in practice.

Task 1

Find the Guidelines

"Open up a brower tab and show us where you would go to find the guidelines"

Observance

All designers expected to find them in either the design system docs or internal site.

Task 1

Find the Guidelines

"Open up a brower tab and show us where you would go to find the guidelines"

Observance

All designers expected to find them in either the design system docs or internal site.

Task 1

Find the Guidelines

"Open up a brower tab and show us where you would go to find the guidelines"

Observance

All designers expected to find them in either the design system docs or internal site.

Task 2

Read the Guidelines

"Take some time to read the Adaptable and Distinguishable sections of the Perceivable guideline. Think aloud. I'll ask you some questions about these sections when you are finished".

Observance

Many skimmed over the text and relied on the images for understanding, but still had a-ha moments about new topics they hadn’t considered. Some felt there was too much text and wanted more complex visuals for harder rules.

Task 2

Read the Guidelines

"Take some time to read the Adaptable and Distinguishable sections of the Perceivable guideline. Think aloud. I'll ask you some questions about these sections when you are finished".

Observance

Many skimmed over the text and relied on the images for understanding, but still had a-ha moments about new topics they hadn’t considered. Some felt there was too much text and wanted more complex visuals for harder rules.

Task 2

Read the Guidelines

"Take some time to read the Adaptable and Distinguishable sections of the Perceivable guideline. Think aloud. I'll ask you some questions about these sections when you are finished".

Observance

Many skimmed over the text and relied on the images for understanding, but still had a-ha moments about new topics they hadn’t considered. Some felt there was too much text and wanted more complex visuals for harder rules.

Task 3

Apply the Guidelines

"I have created a file with some accessibility errors related to the sections you just read. Use the guidelines to help you find some of these errors".

Observance

Designers who cross-referenced the guidelines found more issues than those who relied on memory or prior knowledge.

Task 3

Apply the Guidelines

"I have created a file with some accessibility errors related to the sections you just read. Use the guidelines to help you find some of these errors".

Observance

Designers who cross-referenced the guidelines found more issues than those who relied on memory or prior knowledge.

Task 3

Apply the Guidelines

"I have created a file with some accessibility errors related to the sections you just read. Use the guidelines to help you find some of these errors".

Observance

Designers who cross-referenced the guidelines found more issues than those who relied on memory or prior knowledge.

Task 4

Annotating the Design

"Use this annotations kit to annotate your design for accessibility. Use the guidelines as a reference to help you."

Observance

Many had never annotated for accessibility before, and it remained a point of confusion on why and when they needed to annotate.

Task 4

Annotating the Design

"Use this annotations kit to annotate your design for accessibility. Use the guidelines as a reference to help you."

Observance

Many had never annotated for accessibility before, and it remained a point of confusion on why and when they needed to annotate.

Task 4

Annotating the Design

"Use this annotations kit to annotate your design for accessibility. Use the guidelines as a reference to help you."

Observance

Many had never annotated for accessibility before, and it remained a point of confusion on why and when they needed to annotate.

After testing, I collaborated with the design and accessibility teams to revise the guidelines by simplifying text, enhancing visuals, and clarifying annotation instructions. I also analyzed tester behavior, what they skimmed, which visuals helped most, and where confusion remained, to refine the content for better clarity and usability.

Instructional Videos on Accessibility Annotations

Instructional Videos on Accessibility Annotations

The design team was building a Figma plugin to make annotations a quick process. To support this, and since annotations remained a point of confusion from my testing, I created six short training videos explaining why annotations matter, when they’re needed, and how to use the plugin. I drafted scripts, presentations, and demos and reviewed them with the accessibility and design systems teams before recording.

Accessibility Checklist

Accessibility Checklist

Since some testers found the guidelines to have too much text, I summarized accessibility principles into a one-page checklist. Each point was phrased as a single actionable sentence, making accessibility easier to embed.

Concerns About Workload

Through my research, concerns arose about the added time it will take to verify, fix, and annotate accessibility. And it’s true, all of this is a BIG ask for designers. But we also heard designers say that they prioritize accessibility and want to add it into their process. For this to succeed, resources are not enough. We also need workflow changes, leadership support, and formal requirements.

Concerns About Workload

Through my research, concerns arose about the added time it will take to verify, fix, and annotate accessibility. And it’s true, all of this is a BIG ask for designers. But we also heard designers say that they prioritize accessibility and want to add it into their process. For this to succeed, resources are not enough. We also need workflow changes, leadership support, and formal requirements.

Proposing a Clear Process to Leadership

Proposing a Clear Process to Leadership

I wrapped up my internship by presenting findings and solutions to design leadership, structuring the presentation to tell a clear story:

  1. Problem: Accessibility isn’t consistently embedded in design

  2. Evidence: Survey and interview insights, key pain points

  3. Solutions: Guidelines, checklist, annotation plugin, and instructional videos

  4. Asks: Leadership support, accountability, mandatory accessibility reviews, testing with disabled users, and ongoing communication to raise awareness


This approach clearly conveyed the problem’s urgency and provided actionable steps leadership can take to integrate accessibility into the design process. The presentation was well received with leadership expressing strong interest in addressing accessibility and support for implementing the recommended solutions.

Leading the Accessibility Project

Leading the Accessibility Project

My manager entrusted me with leading the accessibility initiative, expecting me to propose next steps, define solutions, and map out the details of what was needed. While I could seek his guidance, I was responsible for shaping the direction and driving the project forward.


I had to:

  • Identify problems and opportunities through research and testing.

  • Propose solutions that were realistic, actionable, and scalable.

  • Tailor my approach based on feedback, adapting solutions to align with designers’ needs and priorities.

  • Coordinate with multiple teams (design systems, accessibility, research) to refine ideas.

  • Make decisions on what to prioritize, what to simplify, and how to present the work.


Leading this project taught me how to balance independence with collaboration. I learned how to advocate for solutions, gain buy-in from stakeholders, and translate research into actions the company could realistically adopt.

XD Beyond

XD Beyond

XD Beyond

Branding for XD Beyond

Branding for XD Beyond

I joined the creative team to design the 2025 theme for XD Beyond, a State Farm design conference aimed at elevating UX, revealing trends, and educating designers. The 2025 theme, Spark Inspiration, reflects the sudden creative spark when ideas connect. My bold, playful visual style was selected by leadership to move forward, bringing energy and confidence to the conference experience.

Tech Astra

Tech Astra

Tech Astra

Branding for Tech Astra

Branding for Tech Astra

Tech Astra is a design conference that inspires young girls to pursue STEM. I co-designed the 2025 branding with two interns, Hannah Swan and Agustín Montalvo, creating a logo of a girl reaching for the stars to symbolize ambition and possibility. Bright purple and pink tones make the conference feel inviting, energetic, and inspiring.

Hack Day

Hack Day

Hack Day

Hack Day Winners of the Low-Code Category with Our Concept in Development!

Hack Day Winners of the Low-Code Category with Our Concept in Development!

In my first week, I joined a 24-hour Hack Day with two product design interns and two software engineers. We created an app to help Gen Z understand insurance through personalized AI recommendations, short-form videos, and a community forum. I co-designed the UI in Figma, while engineers prototyped the forum interaction. Our concept won the low-code category and is now moving into real development.

Components

Components

Components

Component Design with the Design Systems Team

Component Design with the Design Systems Team

On the Design Systems Team, I contributed to daily reviews of components and icons for the new design system and AI features. I proposed AI prompt controls, AI icons, an AI-generated form field, and motion concepts for AI chat, researching patterns, iterating, testing in context, and building Figma components that other designers could easily use and customize.

Growth

Growth

Growth

What I Learned from My State Farm Internship

What I Learned from My State Farm Internship

While I gained valuable skills in accessibility, research, component building, and branding, the most impactful learning from this internship was how to communicate and collaborate within a large corporate environment.


I learned how to adjust to a 9-5 schedule, balance meetings with tasks, and conduct one on ones with leaders. I became comfortable asking questions, sharing feedback with experienced designers, and advocating for my own ideas. Leading parts of the accessibility project taught me to make decisions, provide daily updates, and take ownership of outcomes.


This experience was both intimidating and exciting, I felt like a full-time employee making a real impact on the company. Some key takeaways I’ll carry forward:


  • Seek feedback early and often. Colleagues with more experience helped strengthen my work and gave me perspectives I wouldn’t have seen on my own.

  • Speak up. Even as an intern, sharing my thoughts in meetings added value and often influenced discussions.

  • Build relationships. Meeting new people across teams not only expanded my knowledge but also opened doors to future opportunities and unexpected support.

KARA RIVENBARK

KARA RIVENBARK

KARA RIVENBARK

Create a free website with Framer, the website builder loved by startups, designers and agencies.