Do forms need semantics?

Question

HTML

Good afternoon! The question was, do forms need semantics? We are talking about both semantic HTML markup, the use of appropriate, semantic tags for form markup, and additional technologies like ARIA.
Maybe I don't understand something... Let's say there is a site that sells multi-colored cards with finely perforated (about 5 acres) quotes from great people. This site has filters (large form). It is clear that all those who see poorly, and even more so the blind, are not the audience of the site))
Search engines, as I understand from what I have already read, are not very interested in forms ...
So what happens? If the site initially does not take into account people with disabilities, can accessibility be neglected for the sake of simplicity and minimalism? Or are there other reasons to pay attention to accessibility?

Answer 1

Semantics is needed not only for the convenience of the blind and lovers of the TAB key. Read articles on how this affects Google search, plugins, add-ons and bots. Even the same AI is tuned for semantics. You can dive into this topic for a very long time, but the basis (in short) is the ability to understand each other. The time spent creating the project architecture can be more than writing the code. What for? And this is the most interesting! Firstly, you save yourself and your colleagues from possible bugs and make it easy to navigate through the files, regardless of the size and knowledge of the project. Good code is one that is easy to read. You often have to sacrifice performance for the sake of readability. Sticking to semantics means writing in the same style with all developers. Even if we omit the architecture, then semantics is needed for various bots. So I wrote a plugin for chrome that makes mini-navigation in the form (in fact, I didn’t write anything, I’m just giving an example) and the search is guided by the tag with the form, but you don’t even have this on the page and that’s it, the plugin will not work . Now imagine what feature you are missing when you hide markup from Google bots. Any tables, rules, lists and other semantic data are displayed on the search page. Try to google some country or instructions for, for example, ubuntu. Google will display information from Wikipedia or another resource without going to the site. Think Telegram doesn't use semantics? Here all such is optimized thanks to it. Look on YouTube for seminars from HTML Academy on semantics. Everything is clearly explained there (which is very rare for online courses). Understandably, that when building a site through frameworks or by embedding html from js, bots will not see this semantics, but just one tag with Id="root". If you take Figma as an example, then you will not see the semantics, since it was not conceived as a website, but rather as an application. They haven’t come up with such tags in html as “draw with a pen” or something like “page template template”. In general, semantics should be where it is appropriate. If you don't need semantic markup privileges, or if it's a solo project with no development, or if you're doing a fucking project for a bad $5 client, then don't bother. But in other cases, it is good practice, and just for yourself, it will be appropriate and very useful to use semantics. then you will not see the semantics, since it was not conceived as a site, but rather as an application. They haven’t come up with such tags in html as “draw with a pen” or something like “page template template”. In general, semantics should be where it is appropriate. If you don't need semantic markup privileges, or if it's a solo project with no development, or if you're doing a fucking project for a bad $5 client, then don't bother. But in other cases, it is good practice, and just for yourself, it will be appropriate and very useful to use semantics. then you will not see the semantics, since it was not conceived as a site, but rather as an application. They haven’t come up with such tags in html as “draw with a pen” or something like “page template template”. In general, semantics should be where it is appropriate. If you don't need semantic markup privileges, or if it's a solo project with no development, or if you're doing a fucking project for a bad $5 client, then don't bother. But in other cases, good practice, and just for yourself, it will be appropriate and very useful to use semantics. If you don't need semantic markup privileges, or if it's a solo project with no development, or if you're doing a fucking project for a bad $5 client, then don't bother. But in other cases, good practice, and just for yourself, it will be appropriate and very useful to use semantics. If you don't need semantic markup privileges, or if it's a solo project with no development, or if you're doing a fucking project for a bad $5 client, then don't bother. But in other cases, it is good practice, and just for yourself, it will be appropriate and very useful to use semantics.