UX Learning-Based Internship
Jan 2024 - April 2024
As a UX researcher intern for SAS (Statistical Analysis Software), I participated in studying:

“How does the design of Data Viewer interactions meet usability and accessibility needs of data users?”

I studied the UX of Data Viewer, a tool to streamline the initial view of datasets, and evaluated the accessibility of this tool using WCAG (Web Content Accessibility Guidelines) guidelines in collaboration with accessibility experts.
data viewer usability studies
My involvement with Data Viewer (DV) included four stages: (1) designing and moderating pilot studies, (2) analyzing study findings, (3) finalizing the study design to be conducted with SAS customers and analyze data, and (4) presenting findings with product team managers.

Data Viewer interface.

pilot studies
During the first stage, I conducted unstructured, exploratory pilot studies. My manager, colleague and I designed three research protocols that we tested with pilot participants. One protocol was exploratory, one protocol had separate tasks to examine individual interactions, and one protocol grouped interactions into three tasks. 

After testing the effectiveness of the different research approaches, we decided to move forward with an exploratory and task-based observation. Seeing how participants explored the interface shaped how my manager, colleague and I responded to users during studies with subject matter experts (SMEs). For example, when a participant was more experienced with the product, we put more time towards unstructured observation over structure tasks.
qualitative analysis
Although I had experience with qualitative analysis, I learned how to use Dovetail, a collaborative online qualitative coding tool. The benefits of using Dovetail for this project was the ability to collaborate in real time. Beyond coding the transcripts, Dovetail supported the collaborative effort of grouping codes to develop insights.
WCAG Evaluation of Data Viewer
I was apprehensive of evaluating the accessibility of DV, as it was an unfamiliar task for me. Despite my first hesitation, I discovered ample online resources and examples to guide me through testing WCAG standards. Throughout the evaluation, I met difficulties in grasping how accessible solutions could be integrated into user interface (UI) design. However, my personal evaluation of DV was only the first step of an overall accessibility evaluation. 
After simple accessibility violations were recorded into JIRA as bugs, a comprehensive accessibility clinic was performed on DV by accessibility experts. Meeting with the accessibility experts after their evaluation led to insightful discussions and prompted my interest in delving deeper into how UX designers address accessibility needs, particularly when designing digital tools. Additionally, while I focused on evaluating specific features using examples and tools, it became clear that even minor details are scrutinized before the interface is evaluated by accessibility experts. This underscores the overarching goal of designing interfaces to be as accessible as possible from the outset.
presenting accessibility findings
Upon receiving a report from the accessibility clinic, my colleague and I presented the accessibility violations to members of the product team. The challenge was to visually express the accessibility violations which largely included issues with (1) screen readers, (2) keyboard shortcuts, and (3) the focus of accessibility tools. The process of making a visual representation of non-visual accessibility violations included pinpointing specific interactions.

Example of how I presented WCAG violations to UX designers and managers at SAS within the design & UX teams.

In designing the presentation of accessibility violations, my goal was to share which WCAG standard was violated, present an example, and provide a potential solution. My intention was to make this knowledge clear and simplified, since accessibility can often be an overwhelming experience to implement.
final reflection
During this internship, I met with user experience (UX) designers, researchers, and developers. From these conversations, I learned about the challenges of conducting usability testing and the significance of selecting the right user participants. One designer emphasized the need to thoroughly understand end-users' behaviors and expectations to effectively communicate design needs within technical departments. Additionally, advice for new designers emphasized the value of learning neuroscience and understanding the affordances and limitations of technology, particularly in the context of emerging mediums like GenAI.
Conversations also touched on ethical considerations surrounding AI, including its potential contributions to misinformation and the need for regulation and accountability. Furthermore, discussions on the agile development process highlighted the importance of balancing rapid iterations with keeping the stability and customer experience of projects.
Moreover, I gained insights into the collaborative nature of UX work, with discussions on design systems, accessibility audits, and the narrative aspect of UX projects. Finally, the analogy of the Ship of Theseus sparked contemplation on the evolving nature of technology and its implications for intellectual property. My colleague and I wrote about our experiences as SAS UX interns in a medium blog published by SAS Product Design.
Being a learning-based intern with SAS was a very educational experience, and I learned a lot about applying UX skills, networking and working with others in industry, and how individuals apply their personal interests to their work. Ultimately, I was grateful for the chance to advance my skills in a collaborative and welcoming environment like SAS.
Back to Top