Updated description: Xeena, has language processing disability, can receive the symbols they are acquainted to because different components are properly identified
Script
Scene
Time
Audio
Visual
1
0:00 - 0:@@
Xeena is a middle school student with a language processing disability. He can type and read simple words but is much more comfortable using symbols instead. He uses a tool that replaces terms that he finds difficult to read into symbols that he recognizes more easily.
We see Xeena sitting in front of a computer and reading sentences of symbols on the screen. It is a school book.
2
0:@@ - @:@@
In addition to replacing words in the text, the tool can also convert buttons and links to symbols he recognizes. For example, the buttons to go to the next or previous sections in a book, or to go to the homepage.
We scroll to the bottom of the page, and there are “back” and “next” buttons; Xeena presses “next” to get to the next page with symbols.
3
@:@@ - @:@@
For this to happen, developers need to provide the correct code to identify the purpose of the buttons, links, and different sections of the page.
We see the code illustratively (not intended to be actually read), and the relevant attributes in the code highlighted (also illustratively)
4
@:@@ - @:@@
Another benefit of such coding, is that the individual page sections can be identified by Xeena’s tool. To reduce complexity and cognitive overload, Xeena uses a command in the tool that temporarily hides all parts of the page except the main content.
Xeena presses a button on the tool and the header, navigation, sidebar, and footer of the page disappear. The main content area expands to fill the regained space, and the text and symbols appear larger. Xeena seems content reading along.