All posts in My Talks & Workshops
Accessibility is unfortunately still an afterthought on many projects. User interaction and accessibility requirements are poorly documented, at best. Or forgotten, when handing over designs to developer teams. And fixing it later costs a LOT more than building it right to begin with. Why, what and how designers can document different aspects of accessibility and user interactions requirements, to build better more inclusive products.
With CSS and JS progress, implementing animations on websites has never been easier. But how do we make sure that our CSS animations and transitions will be meaningful to our users? That they will not be just some annoying “in-your-face” eye candy? That they will not trigger motion sickness and cause accessibility issues to some?
You will find here a transcript with CSS codepen and video examples and LOT of resources to dig further in specific topics. I also published the PDF version of the slides at the end of the article.
How to design systems of components that go beyond responsive adaptation to different screen/viewport size and can also be used in different layout and container contexts? How to make sure that my components work beyond the perfect “happy path perfect situation”: what happens with super long text, missing images/content for example? And how about adapting components to user needs across specific points in their journey and build truly adaptive systems?
I’ve spent last Saturday mentoring and coaching some startups at a WIDE (women in digital empowerment) event. The whole day was about helping them build a more user centered product and come up with a paper prototype of some of the features so that they can test it later. In this context, I gave them a small introduction to User Journey Maps, a tool that helps designers get a visual representation of the whole experience users have with a product or a service. This article is a transcript of this introduction. I will guide you step by step on how to build a user journey map for your product or service. At the end of the article you will find the slides but also two templates to help your build user journey maps for your own projects.
I facilitated a workshop on: “User eXperience – starter crash course for Startups”. The audience was a nice mix between students and entrepreneurs with a project/ website. The goal was to help them discover how to build a product with a user centric approach and why startup people should focus on users needs and talk to their potential users as soon as possible.
In this article, you will find the slides of the workshop.
I’m honoured to be the opening keynote speaker of the LOIC’s Innovation dating event dedicated to User Experience – User Interface in Luxembourg.
In this keynote, I explain to companies and organisations why “Investing in User Centric Design is a Good Business Decision”.
The slides of the keynote are available in this article.
It was a great honour for me to be invited to the first CSSCamp Barcelona ever. I had an amazing day and learned a lot about CSS, but also how to build inclusive design systems, about SVG animations, Houdini, accessibility and aria-live areas, performance and so much more. The slides of my talk are online and the video will be soon.
I gave a talk at CSSDay Amsterdam for the UI special call “Pretty but not Usable”. This talk is based on my years of experience working with dev teams that used Bootstrap, Material UI, Ant, PrimeNG, iOnic, etc to build the projects. I share my experience and process, some design/dev relations tips to help people build a user centric product while working with a UI framework. This whole process is only possible with a lot of communication between the dev and design team. Because this kind of project is not a dev only project, designers needs to be involved in the early stages.
In this small talk, I go through the different kind of issues I encountered while using the web as a user with a “é” in her name. This is a talk about user experience and how encoding and database decisions about formats and characters can create an awful experience. Because we must stop putting the needs of our systems, database, before the needs of our users!