

Accessibility for Agentic Experiences
UX Designer II · Oracle . Present
Oracle Fusion agentic applications bring AI agents into enterprise workflows, helping people access information and take action as part of their work. These experiences introduce interaction questions around how users navigate and understand what happens as they interact with AI.

Working with a small but mighty team
Our accessibility team reviews designs and implementations, holds office hours, and helps product teams work through accessibility questions.
My work focuses on creating accessibility specs for designers and building an internal AI skill to support designers, developers, and QA teams across Fusion Agentic and Redwood Design System.



Bringing accessibility details into the design
A mockup shows what an interface looks like. It also leaves questions to resolve: How does someone navigate with a keyboard? Where does focus move after an action? What information does a screen reader receive?
I create accessibility specifications that document these behaviors for components and pages, giving designers and engineers a shared reference for the intended experience.


Giving designers a consistent starting point
I developed a reusable accessibility annotation and specification template in Figma, along with guidance for using it. Visual callouts connect elements in the interface to their written requirements, making it easier to follow which behavior belongs where.
The specifications cover semantics, keyboard interactions, focus behavior, and screen reader guidance. I continue to create and update them as designs evolve.

The specification template shown has been modified to protect confidential information under NDA.


My Approach
Start with the experience
I connect each requirement to an element and explain what should happen when someone interacts with it.
Keep the design and specs connected
I connect each requirement to the design and describe the expected behavior so designers, engineers, and QA teams know what to build and review.
Make unanswered questions visible
When an interaction is unclear, I bring it back to the team. Writing the specs is also an opportunity to work through decisions before they reach implementation.


Helping teams apply accessibility guidance with AI
I built an internal accessibility skill for design, development, and QA workflows across Fusion Agentic and Redwood. The goal is to help teams use accessibility guidance while they’re working on a design, implementing an interaction, or testing a feature.
I’m shaping the workflows while defining the information the skill needs, and establishing criteria for reviewing its output.

Building on the specs
For the design workflow, the skill brings together the Figma design, specification template, and supporting guidance to help create or refine accessibility specs.
The skill uses the design and existing guidance to help fill out or update a spec, which the designer can then review. Part of my work is deciding when there’s enough context to make a recommendation and when the skill needs to ask for clarification. Beyond design, I’m also working on how the skill can support developers and QA teams as they implement and test these experiences.


_edited_edited_edited_edited_edited_edited.png)