A conversation with Itza, in Spanish: Marta clicks the bar that reads “Pregúntame lo que necesites” (Ask me anything you need), the window opens and the assistant asks what to call her. She types “Me llamo Marta” (My name is Marta), picks the suggested question “¿Hacéis auditorías de accesibilidad?” (Do you do accessibility audits?) and the assistant replies that we audit the website against WCAG 2.2 and current regulations, explain each barrier, provide a plan to remove them and prepare the accessibility statement.

No question left unanswered.

Itza · Case study

Product: Accessible assistant
Year: 2026
Role: Development
Standard: WCAG 2.2 A/AA
Website: Discover Itza (opens in a new window)

The project

Itza is an assistant that answers the questions of people visiting an organisation’s website: what it does, how to sign up, what its opening hours are, whether there are places left. It’s available 24 hours a day, points each person in the right direction and collects the details of anyone who wants to be contacted.

We designed it for associations, foundations, schools and cultural projects, which tend to answer those questions by hand, one by one.

The screenshots on this page show Itza installed on this very website, in its Spanish version, with a sample conversation.

The same conversation on a phone: the Itza window fills almost the whole screen, with the answer about the audit, the text field and the bar with the voice button below. — On a phone

The challenge

An assistant that is accessible too.

A chat is a window that opens on top of the page. If it can’t be used with a keyboard, if the screen reader doesn’t announce the answers or if it traps focus with no way out, it shuts out exactly the people who need help most.

By keyboard, by voice and with a screen reader.

It opens and closes with the keyboard, focus stays inside while it’s open and returns to where it was on closing. Every answer is announced automatically, and you can ask out loud and listen to the reply.

Itza on this website, in Spanish: Marta clicks the bar at the foot of the page, types her name, and the assistant greets her and offers four suggested questions, “¿Qué servicios ofrecéis?” (What services do you offer?), “¿Hacéis auditorías de accesibilidad?” (Do you do accessibility audits?), “¿Cómo es trabajar con vosotros?” (What is it like to work with you?) and “Quiero contaros mi proyecto” (I’d like to tell you about my project), which the cursor moves over one by one. — Suggested questions

The structure

A bar, a conversation and a contact.

Itza lives in a bar at the foot of the page: “Ask me anything you need”. Clicking it opens the conversation. First it asks what to call the person writing, then it offers suggested questions, each organisation’s own.

It answers with the organisation’s own information and is instructed not to make anything up. On closing, it suggests leaving a name and email address, and it can be closed without leaving them. If the person sends their details, the conversation is saved with them, so the team knows what was asked and can pick it up from there.

On closing the conversation, Itza asks, in Spanish, “¿Te ha sido útil? Déjanos tus datos” (Was this helpful? Leave us your details). Marta types her name and email address, clicks “Enviar y cerrar” (Send and close) and the assistant thanks her and gives her the studio’s email address. It can also be closed without leaving any details. — On closing

Design decisions

A useful assistant doesn’t replace the team: it answers the usual questions so the team has time for everything else.

First, the name.
The conversation starts by asking what to call the person writing. The tone is that of someone from the organisation, not a form.
A bar, not a floating button.
“Ask me anything you need” says what it is and what it’s for before you click it. An icon in a corner makes you guess.
In each organisation’s own voice.
The assistant’s name, colours and welcome message adapt to each website.
We install it for you.
No developers and no long contracts: we leave it up and running on the organisation’s website.

No question left unanswered.

Project details

The project

An assistant that is accessible too.

By keyboard, by voice and with a screen reader.

A bar, a conversation and a contact.

Design decisions

First, the name.

A bar, not a floating button.

In each organisation’s own voice.

We install it for you.

If your project is inclusive, your website should be too.