H810 - Navigation Tips for students with visual impairments
Tuesday, 18 Dec 2012, 06:03
Visible to anyone in the world
Edited by Jonathan Vernon, Friday, 4 Jan 2013, 16:50
Fig.1. Google Docs help center - navigation
I was looking for a way to an an Umlaut to the name 'Engestrom' in Google Docs help but instead stumble upon something far more valuable in relation to access to e-learning for students with disabilities - navigation short cuts. These apply to how a person with sight impairment might move through a text and so, like basic web usability, informs on best practice when it comes to writing, proof reading and lay-out, i.e. editing with a reader with a visual impairment in mind.
Somehow the clear way the guide is laid out caused the penny to drop in a way that hasn't occurred in the last three months however many times I have observed, listened to, read about or tried to step into the shows of a student with a visual impairment.
Web usability recommends a way of laying out text that is logical, clear and suited to the screens we use to access content from the web. This logic of headings and multiple sub-headings, let alone plain English in relation to short sentences as well as use of paragraphs makes reading not only easier for those with no disability, but assists those with varies degrees of visual impairment as content is then better able to respond to standard tools of text enlargement and enhancement, but also of screen readers that work best when reading through text.
What assistive technology does, a control that doesn't require a mouse and keeps a manageable set of keys under the fingers rather than needing to run back and forth across the keyboard, is to reduce the above commands to actions that a visually impaired or blind person can then use to control their web viewing experience.
H810 - Navigation Tips for students with visual impairments
Fig.1. Google Docs help center - navigation
I was looking for a way to an an Umlaut to the name 'Engestrom' in Google Docs help but instead stumble upon something far more valuable in relation to access to e-learning for students with disabilities - navigation short cuts. These apply to how a person with sight impairment might move through a text and so, like basic web usability, informs on best practice when it comes to writing, proof reading and lay-out, i.e. editing with a reader with a visual impairment in mind.
Somehow the clear way the guide is laid out caused the penny to drop in a way that hasn't occurred in the last three months however many times I have observed, listened to, read about or tried to step into the shows of a student with a visual impairment.
Web usability recommends a way of laying out text that is logical, clear and suited to the screens we use to access content from the web. This logic of headings and multiple sub-headings, let alone plain English in relation to short sentences as well as use of paragraphs makes reading not only easier for those with no disability, but assists those with varies degrees of visual impairment as content is then better able to respond to standard tools of text enlargement and enhancement, but also of screen readers that work best when reading through text.
What assistive technology does, a control that doesn't require a mouse and keeps a manageable set of keys under the fingers rather than needing to run back and forth across the keyboard, is to reduce the above commands to actions that a visually impaired or blind person can then use to control their web viewing experience.