When redesigning our customer-facing form which contains different kinds of questions - text, currency, selects, radio buttons and checkboxes - the design team did not put any consideration in designing for good accessibility and the engineers did not put enough care in making the product work in screen readers at all. It just had to work and look good.
The form is a react app tha displays the questions one by one and a "next" button on the bottom. We haven't tested this yet but I imagine this is a nightmare for screen readers.
Would it be a good UX practice to aria-hide the whole "fancy" app and have an alternate bare-bones, browser-native
<form> that is only visible by screen readers?