Hmm, that's actually a good point. And in my experience, it really depends on your end users. If a majority of your users are not using assistive technologies, then semantics may not be as important for your needs (though it doesn't hurt to write semantic HTML anyway—in other words, it doesn't get in the way, and there's hardly any downside to it).
I can only think of these two benefits of writing semantic HTML, even if your users are not using assistive technologies like screen readers:
It's easier for you and other developers to read markup and understand what's what (this isn't too relevant if you're using JSX and creating well-named components).
It has built-in, cross-browser compatibility for focus and hover states on certain interactive inputs. This can make your user experience more consistent.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hmm, that's actually a good point. And in my experience, it really depends on your end users. If a majority of your users are not using assistive technologies, then semantics may not be as important for your needs (though it doesn't hurt to write semantic HTML anyway—in other words, it doesn't get in the way, and there's hardly any downside to it).
I can only think of these two benefits of writing semantic HTML, even if your users are not using assistive technologies like screen readers: