Which is frightening, because two years ago I had a terrible experience trying to modify a web app to be accessible using VoiceOver (I gave up after over a week of solid effort).
We couldn’t afford[1] to pay a third party to modify our 100% custom HTML framework[2], and VoiceOver seemed the most approachable for me to try and see how far I could progress on making our web app accessible.
VoiceOver just felt so very buggy - although perhaps the issue was the integration of VoiceOver within Mobile Safari (my dev experience is that Mobile Safari is a steaming pile of problems - current example is that iPadOS15 Safari crashes twice on many pages then goes blank so you can’t use it!).
As a dev, there also needs to be some better online training for using VoiceOver, since small teams do not have easy access to a colleague that uses it.
[1] We could pay 100% blind users to give us feedback, but couldn’t afford to pay a skilled team to consult and do the work.
[2] Custom framework because we started our product before reliable frameworks existed. Modern components are often designed to support accessibility out of the box, which is far preferable!