---
title: "This Synth Had All the Buttons. It Still Needed a Mental Map"
locale: "en"
url: "https://irz.fr/en/articles/vstage-accessibility-mental-map-en"
markdown_url: "https://irz.fr/en/articles/vstage-accessibility-mental-map-en.md"
category: "creative"
tags: ["accessibility", "music", "synthesizer", "product design", "documentation"]
published_at: "2026-08-22T09:20:00.000Z"
author: "Arthur Lacoste"
translation: "https://irz.fr/fr/articles/vstage-accessibility-mental-map-fr.md"
---

# This Synth Had All the Buttons. It Still Needed a Mental Map

V-STAGE is covered in physical controls. Jason Dasent and Roland still had to add spatial descriptions, accessible text and audio to make the instrument learnable without sight.

The Roland V-STAGE panel almost looks like a reaction to the rise of music interfaces that have spent the last fifteen years moving their controls onto screens. Buttons, knobs and sliders cover separate piano, organ, synth and effects sections, leaving much of what a player wants to change during a performance directly under their fingers.[4](https://www.roland.com/global/promos/v-stage_series/)

For Jason Dasent, a musician, producer and accessibility consultant who has been blind since birth, that abundance of physical controls is precisely what made the instrument interesting, because descriptions from other people were enough for him to build a representation of the keyboard and memorize where each section lived.[1](https://articles.roland.com/designing-access-an-interview-with-jason-dasent/)

One revealing problem remained, however. **An object can be tactile without being independently learnable.**

V-STAGE had the buttons, but the map between them still had to be made.

For six months, Dasent worked with Roland Future Design Lab to build that map in several forms, including structured text for screen readers, audio files, downloadable documents, videos and spatial descriptions of the panel. Roland describes the result as a proof of concept, not a hardware redesign of the keyboard.[1](https://articles.roland.com/designing-access-an-interview-with-jason-dasent/)[2](https://www.roland.com/us/company/press_releases/2026/Roland-Future-Design-Lab-Launches-V-STAGE-Accessib/)

That makes the experiment more interesting than a routine manual update, because it catches the point at which **documentation stops being an accessory to a product and becomes part of its interface**.

## Touch is not enough

A physical button has one enormous advantage over a patch of glass. It stays put. Once a player has learned the distance between two controls, the edge of a row or the shape of a neighboring knob, the hand can return there without asking the eyes to confirm the route. Sighted players rely on the same trick on stage, where nobody wants to aim carefully at a graphic widget halfway through a song.

Roland pushes this approach quite far on V-STAGE. Its four sound engines have dedicated sections, effects have their own controls, and many common adjustments remain on buttons, knobs and faders. The company's description of the panel as a set of direct-access controls organized around each function is therefore more than marketing shorthand.[4](https://www.roland.com/global/promos/v-stage_series/)

> Illustration: A hand adjusting physical knobs on the Roland V-STAGE control panel. V-STAGE already has many direct physical controls. That is a strong tactile foundation, but the existence of a button does not tell a blind player where it is, what it does or what appears next on the display. Credit: [Roland](https://www.roland.com/global/promos/v-stage_series/).

But the mistake would be to conclude that the work is finished.

A complex physical interface still carries a huge amount of visual information. A player needs to know that one row belongs to the organ, that a button enables a section, that an encoder changes a different value inside a menu, or that a desired setting is eight right-arrow presses away. V-STAGE also has a 4.3-inch color display and illuminated rings around some controls, useful cues for somebody looking at the panel but cues that do not become tactile merely because the knob beneath them is physical.[4](https://www.roland.com/global/promos/v-stage_series/)

That is the difference between **finding a control** and **understanding a system**.

## Building the map

Dasent has dealt with that gap since the first machines he used, and over the last few decades the tools around him have changed far more than the underlying problem. Long before affordable screen readers became common, his brother learned the positions of buttons on drum machines and synthesizers with him, while his mother recorded entire manuals onto cassette and reproduced some diagrams on raised paper.[1](https://articles.roland.com/designing-access-an-interview-with-jason-dasent/)

But the family system worked only after somebody else had translated the interface first. The cost of making it work was easy to miss precisely because that labor happened before Jason could use the machine.

Years later, Sarah Dasent described much the same method when a manufacturer sent them equipment to evaluate. She would move across the device row by row and label the controls in a document, while Jason gradually memorized the geography. Sound On Sound documented that routine in 2025 while discussing their work with Native Instruments, Ableton, Focusrite, Arturia, Softube and other manufacturers.[5](https://www.soundonsound.com/people/jason-sarah-dasent-making-music-tech-accessible)

V-STAGE turns that improvised method into a public resource.

What matters is that the accessibility guide does not merely **read the existing manual aloud**. A linear narration of a document built around diagrams would retain the original visual logic, whereas Dasent reconstructs the information around the way a hand actually explores the object.[1](https://articles.roland.com/designing-access-an-interview-with-jason-dasent/)

## Left to right

The rear panel is an almost boring example, which is why it is so useful.

A conventional manual can show the back of the keyboard with a photograph, callout lines and numbers, and for somebody looking at the image the topology arrives at once. Outputs are here, pedal sockets are farther over, USB is beside another group; the diagram quietly delivers both identity and relationship in the same glance.

Remove the image and a list of connector names loses much of that information.

Dasent therefore describes the panel as a journey. Stand behind the instrument, begin on one side and move toward the other, naming the first socket, then the next, then the next group. The description thereby preserves something the diagram provided without stating it outright, namely **spatial order**.[1](https://articles.roland.com/designing-access-an-interview-with-jason-dasent/)

> Illustration: Full rear panel of the red and black Roland V-STAGE showing its many connectors. In the accessibility guide, the rear panel is not converted into a flat inventory of sockets. It becomes a route, with connectors described in the order a hand encounters them. Credit: [Roland](https://www.roland.com/global/promos/v-stage_series/).

To be sure, the translation looks obvious once somebody has done it. But that only makes its absence from so many technical manuals more striking.

A diagram is often treated as an illustration that may need some alternative text, yet when it actually explains an object it contains relationships such as left and right, above and below, grouping, distance, order and direction of travel. A useful description has to carry those relationships, not merely name what appears in the picture.

The same distinction applies to a machine tool, camera, mixing console or laboratory instrument, because the problem appears whenever a device has enough controls for its geography to become part of its operation rather than remaining a peculiarity of synthesizers.

## Eight routes

Roland's published page makes the method unusually explicit by dividing the guide into eight chapters — rear panel, organ section, acoustic piano, center section, electric piano, synthesizer, total effects and master section — instead of treating the keyboard as one undifferentiated object.[3](https://www.roland.com/global/accessibility/v-stage_guide/)

Roland publishes each chapter as an HTML transcript, Word document, PDF, MP3 and ZIP package, and bundles the whole guide for download as well. There is also a video playlist and, unusually for what could have been treated as finished support material, a survey asking users what happened when they actually tried it.[3](https://www.roland.com/global/accessibility/v-stage_guide/)

To be sure, no single format solves every accessibility problem, but publishing the same material this way avoids deciding on the user's behalf which medium is supposedly "for blind people."

A screen-reader user may prefer HTML, somebody else may download the audio and listen while both hands remain on the keyboard, and a partially sighted player may combine video, magnification and narration. Dasent says he wanted the videos both for people with some usable vision and for sighted musicians trying to understand how he navigates an instrument.[1](https://articles.roland.com/designing-access-an-interview-with-jason-dasent/)

The duplicated formats are therefore less like administrative clutter than a way of letting the situation choose the interface.

> V-STAGE
> **The manual becomes multimodal**
> - The keyboard is divided according to physical and functional regions.: 8 chapters
> - HTML, Word, PDF, MP3 and ZIP are offered chapter by chapter.: 5 formats
> - Descriptions preserve the order in which hands encounter controls.: 1 route
> - Roland calls the project a proof of concept and is collecting user responses.: Feedback
> Based on Roland's official V-STAGE Accessibility Guide resources, checked August 22, 2026.

## Documentation acts

In many product teams, accessible documentation arrives late, after the object is built and somebody eventually asks whether its PDF can be read. This project exposes a stronger relationship: the document **changes what the object allows a person to do independently** without changing a mechanical part.

That matters because **the cost of** missing information is easy to hide during a demonstration, when another person is already standing nearby.

With another person standing nearby, many products can appear accessible. That person can point out a button, read the current value, explain a menu or remind the user where a socket is, quietly filling information gaps that make the object look more complete than it is.

Dasent describes that scaffolding quite plainly when he talks about learning V-STAGE. Roland recorded video calls and walked him through the instrument, while Sarah sent message after message describing what appeared on screen as they moved through menus. It worked, but it also exposed the problem, because the next musician opening the same box would not necessarily have Sarah, a colleague or a Roland engineer standing by.[1](https://articles.roland.com/designing-access-an-interview-with-jason-dasent/)

The guide turns temporary assistance into reusable infrastructure.

The synthesizer remains just as complicated. What changes is that the route through that complexity can be repeated without keeping a third person in the room.

## The same difficulty

That fits a principle Dasent has argued for throughout his work with manufacturers. Blind musicians should meet the same musical complexity, choices and learning curve as sighted musicians, while the extra difficulty created solely by missing information is the part he wants manufacturers to remove.[5](https://www.soundonsound.com/people/jason-sarah-dasent-making-music-tech-accessible)

That distinction changes product decisions.

That can mean less speech, not more. Three sentences merely slow the operator down when two words already convey a button state, and every control need not become an oversized special key. The more useful question is whether state, position and action can be perceived through another channel when vision is unavailable.

RNIB product-design guidance follows a similar logic. Controls should be easy to locate and distinguish, button groups should remain coherent, orientation should be discoverable, and instructions should come in alternative formats including audio, braille and large print.[6](https://www.rnib.org.uk/documents/2272/Complete_Product_Design_Guide.pdf)[7](https://www.rnib.org.uk/professionals-old-version/business-professionals/accessibility-for-product-design/)

Roland does not claim V-STAGE is the endpoint of all those recommendations. It illustrates a narrower and more transferable case: **good tactile hardware can gain a great deal from documentation that takes its topology seriously**.

## What it fixes

In practice the guide closes three rather mundane gaps that are easy to overlook when the panel is visible. It gives people a shared vocabulary for sections, buttons and connectors. It also preserves the spatial relationship between those parts, so a hand has a landmark rather than merely a name, while the audio can be followed in place with both hands on the keyboard instead of bouncing back and forth to a visual document.

Those properties transfer easily to professional equipment, because a drill press, oscilloscope, CNC controller or mixing desk also has a control space the operator must internalize, and documentation that assumes somebody can visually scan that panel imposes a mode of learning the machine itself may not require.

A design team can therefore improve accessibility without waiting for an entirely new hardware generation. **Describing the existing geography is already a product intervention.**

## What it leaves

A good manual is likely to be useful only where the hardware already gives it something to work with. Documentation cannot make any device accessible by itself.

V-STAGE still carries information visually. Some operations run through the LCD, while illuminated rings report the state of controls. A guide can teach the sequence and establish landmarks, yet every changing visual state does not magically acquire a sound or a texture.[4](https://www.roland.com/global/promos/v-stage_series/)

Roland is correspondingly careful to call the project a **proof of concept**, saying it will gather feedback from blind and visually impaired music creators and use that response to build the case for possible future work across other instruments.[2](https://www.roland.com/us/company/press_releases/2026/Roland-Future-Design-Lab-Launches-V-STAGE-Accessib/)

The useful reading is less flattering and more informative. The guide reveals what was already well designed for touch, what documentation can unlock, and what will remain difficult until the hardware or firmware itself changes.

For designers, the face of the problem changes at that boundary. Some gaps belong in documentation, others plainly belong in the product.

If a value changes continuously and exists only as pixels, an audio chapter will probably not be enough. If one button is physically indistinguishable from ten others, text can teach somebody to count, although a tactile landmark would be better. If a panel already contains stable groups and direct controls, by contrast, a spatial description can unlock capability that was present but hard to learn.

## The wider product

We tend to draw the boundary of a product around its enclosure.

For a professional instrument, that boundary is usually false, because the real product includes the manual, presets, updates, drivers, training videos, control names and the method a player uses to recover a function they forgot six months ago.

Jason Dasent's V-STAGE work makes that extended product hard to ignore. When the manual cannot be used independently, the consequence is concrete: either the musician learns the instrument alone, or another person has to sit beside it and translate the interface first.

That may be the most transferable lesson in the project.

Accessibility does not begin only when a team adds speech output or a tactile marker. It can begin earlier with a less glamorous question: **what information does our product communicate only through the habit of looking?**

Then comes a less spectacular part of product design: writing the relationships, naming the landmarks, preserving the order of gestures and making the same knowledge available through more than one medium.

V-STAGE already had many of the right buttons. Making them genuinely learnable without sight required building the interface that was not inside the box.

## References

1. [Roland Articles, Designing Access: An Interview with Jason Dasent, August 5, 2026](https://articles.roland.com/designing-access-an-interview-with-jason-dasent/)
2. [Roland Future Design Lab, V-STAGE Accessibility Guide press release, August 6, 2026](https://www.roland.com/us/company/press_releases/2026/Roland-Future-Design-Lab-Launches-V-STAGE-Accessib/)
3. [Roland, V-STAGE Performance Keyboard Accessibility Guide](https://www.roland.com/global/accessibility/v-stage_guide/)
4. [Roland, V-STAGE Series](https://www.roland.com/global/promos/v-stage_series/)
5. [Sound On Sound, Jason & Sarah Dasent: Making Music Tech Accessible, June 2025](https://www.soundonsound.com/people/jason-sarah-dasent-making-music-tech-accessible)
6. [RNIB, Accessible product design guide](https://www.rnib.org.uk/documents/2272/Complete_Product_Design_Guide.pdf)
7. [RNIB, Accessibility for product design and testing](https://www.rnib.org.uk/professionals-old-version/business-professionals/accessibility-for-product-design/)