Accessible studio practices

A worked example: naming and versioning

When you cannot glance at a waveform or a colour-coded track, names do the work. A consistent pattern lets a screen reader tell you exactly what a file is:

• Project folder: ArtistName_SongTitle_2026
• Sessions: SongTitle_session_v03_2026-09-14
• Bounces: SongTitle_mix_v05_2026-09-20.wav, SongTitle_master_v02_2026-09-25.wav
• Stems: SongTitle_stem_drums_v05.wav, SongTitle_stem_vocal-lead_v05.wav

Put the most important word first, use the same order every time, and write dates as year-month-day so files sort correctly. The file-name cleaner can tidy names automatically.

Checking your work by ear

Listen to every export from start to end before sending it. Check the first and last seconds for clicks and cut-offs, confirm the fade-out, and compare loudness with a reference track. The loudness and audio check tool reports peak and loudness values in text, which a screen reader can read.

Setting up a workspace you can trust

• Keep physical controllers and cables in fixed positions so you can find them by touch.
• Use tactile markers on important buttons and ports.
• Save a template session with your usual tracks and routing already named.
• Back up projects to a second location on a schedule, and name backups by date.

Small habits like these remove guesswork, which matters most when you cannot check something at a glance.