Jessica the VI Artist music & Patches

Hello all,

I guess it’s time to start one of these threads, as I’ve been looking around and figuring stuff out for some time and am filanny feeling just a little bit confident. I’ve always loved the weird and the wonderful, and lately have been contributing to the Disquiet Junto Project.

To start things off, I thought I’d share a little thing I made showing how I do what I do. Enjoy!!

14 Likes

Welcome to VCV rack. I like how confident you are on the VCV computer, modular synth and the Arturia synth. Good for you and all other ‘disabled’ users or different abilities is a better way to look at that word. For music creation methods, you are a shining example of diversity.

Pretty cool you can patch like that, Jessica. That’s gotta require a lot of patience.

Any thoughts on things that module developers can do to make using their modules easier for you? Or anything we should consider not doing? Accessibility is something I attempt to spend time thinking on and working on, but it’s often hard to perceive the issues you don’t have.

Mahlen

2 Likes

These are few of the guidelines for User Interface accessibility:

  • Perceivable: Information must be presentable to users in ways they can perceive (e.g., text alternatives for images, sufficient color contrast).

  • Operable: User interface components must be operable (e.g., keyboard navigation, no keyboard traps).

  • Understandable: Information and operation of the user interface must be understandable (e.g., predictable navigation, input assistance).

  • Robust: Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies.

  • Color Contrast: Text and images of text must have a contrast ratio of at least 4.5:1 (or 3:1 for large text).

  • Keyboard Accessibility: All functionality must be operable via keyboard (no mouse required).

  • Focus Indicators: Visible indicators showing which element has focus when navigating via keyboard.

  • Alt Text: Descriptive text for all non-text content (images, icons).

This is US Guidance regarding web sites accessibility, which can be applied in this context as well:

Rack itself is missing fundamentals that are table stakes for accessibility, full keyboard access being one of the major ones. It’s just not designed with accessibility in mind. Individual modules are that much harder to make accessible without Rack providing the fundamentals.