- What is accessibility?
Writing code using Semantic HTML to ensure that all people can equally access the website, its features and its content; regardless of their individual needs and/or abilities. This is includes visual impairments, hearing impairments, mobility impairments and cognitive impairments. It too includes groups of people with poor internet access and slow network connections.
Online content can be made accessible by making sure the correct Hypertext Markup Language elements are used for the correct purpose at all times.
- How do people interpret websites without vision?
Some may use magnifiers or screen readers, a technology that reads digital text aloud. Some screen readers are free and others are paid and some are built into operating systems.
- How does semantic HTML help make websites accessible?
Semantic HTML is naturally accessible. However, it becomes inaccessible when used incorrectly. It makes websites accessible when it is used correctly to provide excellent content structure with headings, paragraphs, lists, etc.
- Name a few practices to avoid when writing HTML.
- Using line breaks for styling
- Abbreviations, slang (anything that isnât properly written Kings English)
- Page layouts using HTML tables
- Buttons marked up using the âdivâ tag
- Bad link text e.g. âclick hereâ
- Form labels which donât make the location for editing text clear to the visually impaired
- Not providing typed text for audio and video content.
- Machine generated file names
- Alt text that is duplicated in the surrounding content
- Not including alt attributes for images
- Removing accessible styling from links
- or if JavaScript causes links to behave in unexpected ways
- Link colouring that blends in with the background of the page
- Using
onclick
with anchor tags to create pseudo-buttons to prevent the page from refreshing.
- Not indicating information on what will happen when an external link is activated.
- Not including skip links when websites have repetitive info.
5, What is a tab index?
This is an attribute that is 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. When done well, this is a particularly useful element for the visually impaired when they are filling out forms.