Hi,
I understand. Is there any chance you'd be willing to share the solution for the hashes with me privately? I'd just like to be able to add all my modules and then manually (or probably with a script) edit the row/column so that my case can stay updated. I can promise I won't leak/share this information, but as it stands the most useful part of MG for me is unusable, even with a paid membership. I am trying to get a copy of my rack (and keep it updated) so that I can ask for help/advice on it. Everyone wants to see racks on MG, and not being able to use them is a huge issue for me. I specifically paid for Unicorn thinking it would get around the issue. I'm happy to have paid, but I'm still stuck.

I am also a long-time software developer; my most notable work was CVStats, which was a site built with accessibility in mind to help people with disabilities get access to the COVID-19 stats that were not accessible or easily readable. This work was picked up by Vice and CNET among others. I mention this because I have a long history of accessibility advocacy and work. I don't know what your typical workflow looks like or if this is code written by a single person, but I'd be happy to sign any documents saying I won't leak the code or copy it. That said, I'd genuinely appreciate the chance to be able to make MG more accessible for free, without any cost to MG or anyone else. If you're willing, I'd be happy to make these changes through github pull requests, or whatever VC system you make and acceptance would be up to anyone else. I realize and understand that it's tough to make a site like this more accessible, and even more-so without prior knowledge or testing.
Thanks,

Hello,
I posted this a while back:
https://modulargrid.net/e/forum/posts/index/14173
I wanted to be able to create and easily edit my rack, and saw that with a paid membership you can import and export racks.
When I exported though so i could modify all my work, I noticed that there is a hash. Will the import fail if this doesn't match, and what is hashed? For example, would it be okay for me to just add all my modules, then manually edit row/column? It's time consuming, but this would solve the bulk of my problems and let me create the rack starting out.
Otherwise, if you're adding modules to a rack, how do you tell it to add to the next row? For example Ihave my top row done, but there's still space.
Thanks,

This is all super amazing and helpful, thank you.
I can confirm that I can now see modules as alt text. This is helpful when I'm looking at other people's racks, too. Thank you!

Maybe I was looking at the dom weird, but I was suggesting that the container divs have the roles of table, row and cell. This would make it navigable by table. Right now, the current table is below all the graphics; presumably the graphic could be in each cell. This makes it like a grid.

re: the row combobox, when I add a module (with the add icon in the search results), Ican't control where or which row it goes into. And because the mover isn't accessible (I can't just focus on the last module in the row), I can't easily just move everything far right so the next items would be added in the row below.

Thanks again. This is amazing to see; I really appreciate all your work!
Hi all,
I am a totally blind user, relying on a screen reader.
I'm building my first eurorack setup and would really love to create a modulargrid version so that I can share it out with others.
This is sort of usable, but it's a bit tough. I'm curious if there's a chance that I could help work on this to make it accessible (I'm fluent with python/php/javascript) or if people here are open to suggestions.
Here are my ideas just starting:

• add a role of h2 to all the module titles in search results; this will make it faster to view.
• When adding modules, it would be really helpful if there was a "row" combobox that was bounded from 1 to max rows, so if I click add and I'm on row 2, I can add it to row 2 (right now, I can only make one horribly long row)
• Can you add the module name to the alt text of a module? This would make it easy to view. Maybe even (hp) at the end so you know how many hp the module is?
• The following won't change the appearance but will make this navigable by table:
  • The enclosing container is a div with id of restraint. Add role="table" to this.
  • The rows are a div with class grid-row. Add role="row" to this.
  • for cells, add role="cell".
• A switch in the module build to make modules focusable. This would add tabindex="0" to the module images. Then you can focus on it and use the keyboard commands.
• Some way to select a slot (if I have module A and B and move B to the right, I might want to add a blank panel here.
• Where you have icons (like on the "add" links, for example, consider adding an aria-label like aria-label="add", which will announce the link as what it is. Right now they read as questionmarks.

These would make this much more usable.
Thanks,

Hi all,
I am a totally blind user, relying on a screen reader.
I'm building my first eurorack setup and would really love to create a modulargrid version so that I can share it out with others.
This is sort of usable, but it's a bit tough. I'm curious if there's a chance that I could help work on this to make it accessible (I'm fluent with python/php/javascript) or if people here are open to suggestions.
Here are my ideas just starting:

• add a role of h2 to all the module titles in search results; this will make it faster to view.
• When adding modules, it would be really helpful if there was a "row" combobox that was bounded from 1 to max rows, so if I click add and I'm on row 2, I can add it to row 2 (right now, I can only make one horribly long row)
• Can you add the module name to the alt text of a module? This would make it easy to view. Maybe even (hp) at the end so you know how many hp the module is?
• The following won't change the appearance but will make this navigable by table:
  • The enclosing container is a div with id of restraint. Add role="table" to this.
  • The rows are a div with class grid-row. Add role="row" to this.
  • for cells, add role="cell".
• A switch in the module build to make modules focusable. This would add tabindex="0" to the module images. Then you can focus on it and use the keyboard commands.
• Some way to select a slot (if I have module A and B and move B to the right, I might want to add a blank panel here.
• Where you have icons (like on the "add" links, for example, consider adding an aria-label like aria-label="add", which will announce the link as what it is. Right now they read as questionmarks.

These would make this much more usable.
Thanks,

EDITED Mar 22nd, 07:16