PLATFORM
Printer Application
ROLE
Senior Product Designer
TOOLS
Figma • Azure DevOps
DURATION
Nov 2024 – Oct 2025
Problem Statement
USDA employees faced barriers completing daily printing tasks because of poor keyboard navigation and accessibility features.
This problem was crucial to solve as it affected over 100,000 employees using at least 16,000 devices across 3,500 different government offices. The focus on keyboard navigation was outlined through a VPAT and ACR document.
Problem Statement
USDA employees faced barriers completing daily printing tasks because of poor keyboard navigation and accessibility features.
This problem was crucial to solve as it affected over 100,000 employees using at least 16,000 devices across 3,500 different government offices. The focus on keyboard navigation was outlined through a VPAT and ACR document.
Problem Statement
USDA employees faced barriers completing daily printing tasks because of poor keyboard navigation and accessibility features.
This problem was crucial to solve as it affected over 100,000 employees using at least 16,000 devices across 3,500 different government offices. The focus on keyboard navigation was outlined through a VPAT and ACR document.
Employees
100,000
Employees
100,000
Employees
100,000
Devices
16,000
Devices
16,000
Devices
16,000
Offices
3,500
Offices
3,500
Offices
3,500
Research and Understanding
Defined scope by understanding accessibility limits and development constraints
I conducted interviews with users, system engineers, and developers to uncover pain points and technical boundaries. These discussions clarified what could be improved while staying within strict project requirements.
Research and Understanding
Defined scope by understanding accessibility limits and development constraints
I conducted interviews with users, system engineers, and developers to uncover pain points and technical boundaries. These discussions clarified what could be improved while staying within strict project requirements.
Research and Understanding
Defined scope by understanding accessibility limits and development constraints
I conducted interviews with users, system engineers, and developers to uncover pain points and technical boundaries. These discussions clarified what could be improved while staying within strict project requirements.
User Interviews
Spoke with users to determine most common actions and tasks that they complete on the app and what their pain points where.
User Interviews
Spoke with users to determine most common actions and tasks that they complete on the app and what their pain points where.
User Interviews
Spoke with users to determine most common actions and tasks that they complete on the app and what their pain points where.
Review of VPAT and ACR
I reviewed the product’s Voluntary Product Accessibility Template (VPAT) and Accessibility Conformance Report (ACR) to identify gaps and ensure all proposed changes aligned with accessibility standards, preventing re-certification.
Review of VPAT and ACR
I reviewed the product’s Voluntary Product Accessibility Template (VPAT) and Accessibility Conformance Report (ACR) to identify gaps and ensure all proposed changes aligned with accessibility standards, preventing re-certification.
Review of VPAT and ACR
I reviewed the product’s Voluntary Product Accessibility Template (VPAT) and Accessibility Conformance Report (ACR) to identify gaps and ensure all proposed changes aligned with accessibility standards, preventing re-certification.
Clarifying Limits
I collaborated closely with development and system teams to ensure design solutions were technically feasible, aligned with timelines, and compatible with the existing system architecture. Additionally, the app needed to retain all functionality that it currently had. No features were to be added or removed.
Clarifying Limits
I collaborated closely with development and system teams to ensure design solutions were technically feasible, aligned with timelines, and compatible with the existing system architecture. Additionally, the app needed to retain all functionality that it currently had. No features were to be added or removed.
Clarifying Limits
I collaborated closely with development and system teams to ensure design solutions were technically feasible, aligned with timelines, and compatible with the existing system architecture. Additionally, the app needed to retain all functionality that it currently had. No features were to be added or removed.
Design
Exploring ideas and workflows to best optimize performance.
Design
Exploring ideas and workflows to best optimize performance.
Design
Exploring ideas and workflows to best optimize performance.
Improved contrast, layout, and navigation for accessibility.
Through sketches and wireframes, I redesigned key screens to address contrast issues, optimize touch targets, and restructure layouts. Accessibility-focused adjustments included replacing pull-to-refresh gestures with buttons and reorganizing forms to reduce scrolling and motor strain.
Improved contrast, layout, and navigation for accessibility.
Through sketches and wireframes, I redesigned key screens to address contrast issues, optimize touch targets, and restructure layouts. Accessibility-focused adjustments included replacing pull-to-refresh gestures with buttons and reorganizing forms to reduce scrolling and motor strain.
Improved contrast, layout, and navigation for accessibility.
Through sketches and wireframes, I redesigned key screens to address contrast issues, optimize touch targets, and restructure layouts. Accessibility-focused adjustments included replacing pull-to-refresh gestures with buttons and reorganizing forms to reduce scrolling and motor strain.
Unified accessibility and brand consistency across Xerox platforms.
I gathered feedback from internal teams to align the design with Xerox’s brand and accessibility best practices. Iterative reviews ensured consistency while maintaining usability across all screens.
Unified accessibility and brand consistency across Xerox platforms.
I gathered feedback from internal teams to align the design with Xerox’s brand and accessibility best practices. Iterative reviews ensured consistency while maintaining usability across all screens.
Unified accessibility and brand consistency across Xerox platforms.
I gathered feedback from internal teams to align the design with Xerox’s brand and accessibility best practices. Iterative reviews ensured consistency while maintaining usability across all screens.
Before and Afters.
Below are some before and afters of how the user interface had improved.
Before and Afters.
Below are some before and afters of how the user interface had improved.
Before and Afters.
Below are some before and afters of how the user interface had improved.
Previously, the landing screen and number pad displayed a lot of information, requiring users to scroll for additional details like confirmation numbers and QR codes. Progressive disclosure on this screen allowed employees to focus on logging in while new users accessed only the necessary information.
Initially, the application relied on using a gesture model to refresh the page. For accessibility reasons, gestures are often hard to execute. Instead, a simple, familiar refresh button was added to the global navigation.
The list of features (settings) users can adjust was updated to better reflect partner applications and other Xerox-based software solutions. Therefore, this brought consistency and improved navigation as users knew what to expect when it came to changing settings.
List items previously were misaligned, had poor contrast, and resulted in heavy scrolling. Instead, I introduced a clean and simple way to navigate and view documents that mapped the jobs to UX conventions found on similar platforms.
Developer Handoff
Established clear accessibility documentation to reduce developer friction.
Due to the high bar for accessibility, some developers became overwhelmed. Between new standards for screen readers, keyboard navigation, touch targets, and more, there was a lot of information to take in as a developer.
Developer Handoff
Established clear accessibility documentation to reduce developer friction.
Due to the high bar for accessibility, some developers became overwhelmed. Between new standards for screen readers, keyboard navigation, touch targets, and more, there was a lot of information to take in as a developer.
Developer Handoff
Established clear accessibility documentation to reduce developer friction.
Due to the high bar for accessibility, some developers became overwhelmed. Between new standards for screen readers, keyboard navigation, touch targets, and more, there was a lot of information to take in as a developer.
Updating the Spec
Shown below, I added snippets to parts of the spec that call out information regarding accessibility requirements. And unlike before, where accessibility was scattered throughout the application, I aggregated all of the tips into an accessibility section in the spec that was easy to find for developers.
Updating the Spec
Shown below, I added snippets to parts of the spec that call out information regarding accessibility requirements. And unlike before, where accessibility was scattered throughout the application, I aggregated all of the tips into an accessibility section in the spec that was easy to find for developers.
New Accessibility Section in the Xerox Interface Design System
To ensure that the accessibility guidelines taught during this project were well-documented, I collaborated with our graphic design team to establish best practices for our Xerox Interface Design System. This approach prevents future teams from repeating the effort.
New Accessibility Section in the Xerox Interface Design System
To ensure that the accessibility guidelines taught during this project were well-documented, I collaborated with our graphic design team to establish best practices for our Xerox Interface Design System. This approach prevents future teams from repeating the effort.
Tight-knit Communication
Even with a comprehensive specification and additional resources incorporated into XIDS, I was part of a collaborative environment where teams and individuals could reach out to each other and maintain open communication.
Tight-knit Communication
Even with a comprehensive specification and additional resources incorporated into XIDS, I was part of a collaborative environment where teams and individuals could reach out to each other and maintain open communication.
Tight-knit Communication
Even with a comprehensive specification and additional resources incorporated into XIDS, I was part of a collaborative environment where teams and individuals could reach out to each other and maintain open communication.
Weekly Product Development Meetings
As part of development, we held weekly product development meetings to ensure everyone was on track with delivery.
Weekly Product Development Meetings
As part of development, we held weekly product development meetings to ensure everyone was on track with delivery.
Weekly Product Development Meetings
As part of development, we held weekly product development meetings to ensure everyone was on track with delivery.
Tight Daily Communication
I had an open door policy, so developers were able to reach out to me over email and Microsoft Teams to get questions answered rather than having to wait until our weekly meeting.
Tight Daily Communication
I had an open door policy, so developers were able to reach out to me over email and Microsoft Teams to get questions answered rather than having to wait until our weekly meeting.
Tight Daily Communication
I had an open door policy, so developers were able to reach out to me over email and Microsoft Teams to get questions answered rather than having to wait until our weekly meeting.
Azure DevOps Tracking
I requested access as your dev ops, which helped me understand the progress developers and project managers had made on the project to ensure we met the deadline.
Azure DevOps Tracking
I requested access as your dev ops, which helped me understand the progress developers and project managers had made on the project to ensure we met the deadline.
Azure DevOps Tracking
I requested access as your dev ops, which helped me understand the progress developers and project managers had made on the project to ensure we met the deadline.
Results and Impact
Delivered a fully accessible print experience and Xerox’s first accessibility framework.
The project marked a significant milestone at Xerox. Completing a $164 million contract and delivering the project with new accessibility standards was an impressive feat by all the people that worked on the project.
Results and Impact
Delivered a fully accessible print experience and Xerox’s first accessibility framework.
The project marked a significant milestone at Xerox. Completing a $164 million contract and delivering the project with new accessibility standards was an impressive feat by all the people that worked on the project.
Results and Impact
Delivered a fully accessible print experience and Xerox’s first accessibility framework.
The project marked a significant milestone at Xerox. Completing a $164 million contract and delivering the project with new accessibility standards was an impressive feat by all the people that worked on the project.
Completely Met
WCAG 2.2 and section 508 requirements put in place by the ACR.
WCAG 2.2 and S.508
Completely Met
WCAG 2.2 and section 508 requirements put in place by the ACR.
WCAG 2.2 and S.508
Accessibility Documentation
Providing a framework for future teams.
New XIDS
Accessibility Documentation
Providing a framework for future teams.
New XIDS
Keyboard Functionality
Full keyboard functionality for the employees and other users that require different ways of navigating an application.
100%
Keyboard Functionality
Full keyboard functionality for the employees and other users that require different ways of navigating an application.
100%
Fewer Questions
Regarding accessibility, allowing us to focus on delivery.
45%
Fewer Questions
Regarding accessibility, allowing us to focus on delivery.
45%
Completely Met
WCAG 2.2 and section 508 requirements put in place by the ACR.
WCAG 2.2 and S.508
Keyboard Functionality
Full keyboard functionality for the employees and other users that require different ways of navigating an application.
100%
Accessibility Documentation
Providing a framework for future teams.
New XIDS
Fewer Questions
Regarding accessibility, allowing us to focus on delivery.
45%
