Other: Getting Started with web accessibility auditing

Technology   Dec 4, 2015 by Donald

FIVE PERSONAS AND THEIR POTENTIAL ACCESSIBILITY ISSUE

1. Persona A: A blind person needs to rely on developers to have their applications coded in an accessible way. important Diagrams and images that are not explained or described with regular text will pose a barrier on a blind man using an assistive technology like the Screen Reader.

2. Persona H: She needs websites to be simple and readable, even when the concept is complex. she might not get all the messages on the website if the web page does not support text-to-speech, spell checkers, word completion system and most importantly "captioning" in case of videos and audio messages. if the transcript of the webpage is not available she will not get all information on the website.

3. Persona I: I has to be careful when visiting brightly-colored pages or pages aimed for younger people,   if its a system with very high resolution he may not be able to work on it. he needs a web pages where he can turn OFF styles in the browser and adjust the brighten and contrast settings. a website that does not have all this features is not inclusively design. "Braille display/output devices" is a very useful tool for Mr. I.

4. Persona N: N has poor hearing in both ears, and hearing aids. Functionally, she’s deaf. any website that has no transcript is of no use to her.  web pages with audio and videos messages without proper 'captioning" will be lost to her hearing. if audio and videos is important to the message conveyed by a page and it does not have a text alternative or good caption the reader will not receive the intended message.

5. Persona R; R post-concussion syndrome A complex website will definitely be a problem cos such victim cannot read longer text. absence of text to speech software, word completion system and spell checker will pose a big difficulty in using the internet.