Your Web News in One Place

Help Webnuz

Referal links:

Sign up for GreenGeeks web hosting
September 9, 2020 05:10 pm GMT

5 most annoying website features a blind person faces every single day

For blind and visually impaired people, accessibility is the difference between them being able to use a website and we click off it.

How screen readers work

Screen readers allow blind and visually impaired people to use computers, phones, and tablets independently. Most screen readers use the software, and a Text To Speech (TTS) engine, which is what converts the text from the screen reader into speech. Screen readers convert the text displayed on screen into a format that blind users can process.

Screen readers read out loud everything thats on the screen and allow people to navigate using touch gestures and shortcut keys. They also work with other output devices such as a braille display.

1. Unlabelled links and buttons

Screen reader users rely on links and buttons to navigate around a website and to find the information we need. If links and buttons are not labeled correctly or if at all, then it makes it difficult for screen reader users to find the information they need. Ultimately, unlabelled links make it much harder to navigate the website easily, quickly, and independently.

For example, when linking to an about page, click here doesnt give any clue as to where it leads to, but find out more about who we are is clear.

If links and buttons are labeled correctly, screen readers can read the label out loud. It means that blind and visually impaired people dont have to press the link or button without knowing where it will take them.

As well as unlabelled elements, links, and buttons that do not have a clear description are also really frustrating. They must have a clear description of where they will lead to when pressed, rather than click here. Never make your users guess where a link will take them or force them into a trial-and-error situation. This makes for a tedious user experience.

2. No image descriptions

This is probably the most common issue a blind person encounters when browsing the web. Using image descriptions is essential for accessibility. Image descriptions are also known as alt text (alternative text) which is a written description of an image.

Screen readers read image descriptions out loud. This means that blind and visually impaired people can understand the content of the image in an accessible way. If images do not have alt text, then screen readers will simply say image or graphic which gives no context or meaning.

Images often convey valuable information. Its therefore important that people with a visual impairment can access this information as well. Alt text should be clearly written and give an accurate description of the image.

3.Poor use of headings

For quick and easy navigation, many screen reader users navigate using various elements on the page such as headings. They are a great way to find the information we need quickly and effectively. Especially when they follow a logical heading structure with H1s, H2s, and H3s helping to prioritize the content.

If websites dont use headings, it means screen reader users are unable to use the keyboard shortcuts to navigate through the webpage this way. If thats the case, they have to resort to tabbing or arrowing through a long web page to find the information they need.

Heading Hierarchy

Headings also help to break up the web content visually and improve readability. Other elements that screen reader users use to navigate webpages include links, lists or landmarks.

4.Inaccessible web forms

Most websites use forms in one way or another. Whether its to help you search for a product or to get in touch through a contact form. However, when these forms are not labeled, or not labeled correctly, it means they cannot use them.

For example, if a search box is not labeled, it means screen reader users have no idea of the purpose of that box. It means people who use screen readers cannot access the same functionality.

Contact forms are an effective way for customers to get in touch with your brand or business. And as a screen reader user, theres nothing more frustrating than these forms being labeled incorrectly.

Especially CAPTCHA checkout requirements. Without an option to hear the audio, its not accessible. It means we are unable to fill in the form independently. They often have to enlist help from a sighted person, but this isnt possible for everyone.

5.Auto-playing audio and video

Most people will know how annoying it is to load a web page with noisy adverts that start playing suddenly. But for screen reader users, it can be even more alarming. When video or audio starts playing automatically, it can drown out the voice of the screen reader. This makes it harder to find the pause or stop buttons.

(And if these buttons are unlabelled, then its practically impossible for them to stop the video quickly which causes extra frustration.) If they are unable to stop the sound or video, they normally click off.

The solution? Make sure theres no auto-playing video or audio when your website loads. If you really want to use video, make sure the audio is muted and the user can pause, stop, or hide the media player.

These issues may seem small to sighted users. But theyre the difference between being able to use a website independently or not. And they make a huge difference when implemented correctly.

I read this story at the The Big Hack by Holly Tuke @lifeofablindgrl. Sometimes developers don't think much about accessibility while developing the websites, even I made many of these mistakes but after reading this and understanding the negative impact it can make to blind people I had to share it with you all, so we always take care of these things.

Have a good day,
Happy Learning.


Original Link: https://dev.to/kedark/5-most-annoying-website-features-a-blind-person-faces-every-single-day-2jm5

Share this article:    Share on Facebook
View Full Article

Dev To

An online community for sharing and discovering great ideas, having debates, and making friends

More About this Source Visit Dev To