@jfayre @tristan @alexhall Excellent point, yup it is a very complex piece of software with lots of web UI for sure! I’ll look into spinning up a VM to check things out.

@tristan @alexhall @jfayre Wow, that is seriously awesome news!
OPNsense was quite inaccessible when I last tried it 2 or so years ago, which is why I’m still using PFSense here. Guess it’ll be time for some serious reinstallation / reconfiguration work soon.

@stirlock I am so shocked and sad to hear… Brandon was such an incredible pioneer in the world of blind accessible gaming who truly made a difference… I sadly never had a chance to get to know him, but from his streams and videos he always stood out to me as having a super cheerful personality and being very passionate about his work. I am so, so sorry about your loss and sending lots of positive energy your way.

@podfeet Super glad to hear it worked, yay! Feel free to reach out if you have any other questions about VO, absolutely happy to help where I can :-).

@podfeet As a blind VO user, I first of all want to seriously thank you for doing this! Doesn’t matter honestly if your experience using VO might be limited, as long as you test what you can and keep an open ear for user feedback on accessibility issues, that already goes a super long way and is significantly more than what some other devs / companies out there are doing, great job!!! Unfortunately it’s true that there isn’t a reliable way of rearranging status menu icons using VO. However, it is possible to navigate to all the icons which are in there by pressing the VO keys (either CTRL+Option or Caps Lock) + M twice, which will move VO focus to the first icon. You can then navigate through the various icons by pressing VO + Right Arrow / Left Arrow and activate the focused icon using VO + Space. Hope that helps!

@dynobo Thanks! Started looking into Nox already as it was previously suggested, and planning to adopt it not only for this use case but in general. Really appreciate the suggestion!

@cazabon Thanks for that, excellent point and honestly sounds like a super reasonable approach. That’s actually how I was gonna do this as well. However, I then needed to install dj-rest-auth into my project, which has the same dependency (django-allauth) as my own package, but pinned to a much older version than what was specified as a minimum requirement in my own package. I then downgraded to the latest version of django-allauth supported by dj-rest-auth, only to find that it now broke my package in all kinds of ways. So that’s what got me to the point where I started thinking about some automated way which would let me figure out the oldest version of django-allauth that my package is still compatible with :-).

@amethyst Excellent, thanks so much for that! Think this is exactly what I was looking for, seems like I also should be able to integrate this in my CI pipeline as a good sanity check. Will try this and @jscholes suggestion to see which one works best for me.