1. What is accessibility?
A great deal of web content can be made accessible just by making sure the correct Hypertext Markup Language elements are used for the correct purpose at all times.
2. How do people interpret websites without vision?
They are navigating with the aid of screen reading technology
3. How does semantic HTML help make websites accessible?
Semantics is one of the areas that gets most broken with ''spaghetti" html, hence why proper semantics in HTML make markup lighter, but also properly accessible.
4. Name a few practices to avoid when writing HTML.
Using language and characters that don’t get read out clearly by the screen reader.
- Don’t use dashes if you can avoid it. Instead of writing 5–7, write 5 to 7.
- Expand abbreviations — instead of writing Jan, write January.
- Expand acronyms, at least once or twice. Instead of writing HTML in the first instance, write Hypertext Markup Language.
5. What is a tab index?
- The tabindex attribute is primarily intended to allow tabbable elements to have a custom tab order (specified in positive numerical order), instead of just being tabbed through in their default source order. This is nearly always a bad idea, as it can cause major confusion. Use it only if you really need to, for example, if the layout shows things in a very different visual order to the source code, and you want to make things work more logically. There are two other options for tabindex:
- tabindex=“0” — as indicated above, this value allows elements that are not normally tabbable to become tabbable. This is the most useful value of tabindex.