I know accessibility for low vision users was mentioned, but I wonder, with all these changes, whether version 4 will be accessible to screen reader users, and if so, whether any major features will nevertheless remain inaccessible.
We're using the framework my team on MuseScore Studio created for the UI in Audacity. This allows us to port over the significant amount of screen reader support we built over there too.
We'll need to spend time making sure it's applying correctly to every corner of the app - but when it's done, the app will be far more broadly supported than V3.
The privacy policy now reads
For the purposes of this Notice, MuseCY SM Ltd., a Cyprus company with an address at Spyrou Kyprianou, 84, 4004, Limassol, Cyprus (“Audacity Team“, “us“, “we“, or “our“) acts as the data controller for the personal information that is collected via the App and through the use of the App, as further outlined in section 2 (“personal information”). As a data controller, the Audacity Team makes sure that any processing of your personal information complies with applicable data protection law, and specifically with the General Data Protection Regulation (“GDPR”).
I don’t know when it happened, but earlier in the week a non-tech member of staff, who was trying to install Audacity, called me really confused because it was asking about installing and then saving to some sort of cloud storage that was being pushed during the installation process. I personally haven’t used Audacity for a couple of years, so the cloud storage stuff added in 2024 is new to me showing up during install. It appeared again in the choice of save locations even after rejecting it during install and I have no interest in someone calling me in two years asking where their files are after the cloud storage shuts down or gets paywalled. For 95% of casual users looking to just split/combine/trim/etc some basic audio files, I’m just gonna tell them to use Ocenaudio.
These videos by Tantacrul are sooooo good to watch, from the perspective of making product decisions for a software product. They are really well made, too
10 comments
[ 3.7 ms ] story [ 31.1 ms ] threadWe'll need to spend time making sure it's applying correctly to every corner of the app - but when it's done, the app will be far more broadly supported than V3.
As someone who's never worked with either (only web UIs), I thought this would be a good chance to understand: why is wx bad, what makes Qt good?