VisAssist Web Navigator Software Requirements Specification Trevor Adams Nate Bomberger Tom Burdak Shawn Busolits Andrew Scott Matt Staniewicz Nate Vecchiarelli
Contents Introduction... 4 Purpose... 4 Scope... 4 Applications... 4 VisAssist Web Navigator Menu System Overview... 4 VisAssist Navigator UI Overview... 5 VisAssist Navigator User Interface Requirements... 6 UI.1 Menu Interactions... 6 UI.2 Context Menu Interaction... 7 UI.3 Content Container Interaction... 8 UI.4 Gestures... 8 Media Wiki Overview... 9 Media Wiki Requirements... 9 MW.1 Wiki Selection Menu...10 MW.2 Wiki Main Menu...11 MW.3 Search Menu...11 MW.4 Article List Menu...12 MW.5 Article Main Menu...13 MW.6 Section Main Menu...14 VisAssist Facebook Browser Overview...15 VisAssist Facebook Navigator Requirements...15 FB.1 Login Requirements...16 FB.2 Main Menu Requirements...17 FB.3 News Feed Requirements...18 FB.4 Like or Unlike Requirements...19 FB.5 Like or Unlike Feedback Requirements...20 FB.6 Post a Comment Requirements...21 FB.7 Comment Feedback Requirements...22 FB.8 View Likes Requirements...23 FB.9 View Comments Requirements...24 FB.10 Update Status Requirements...25 FB.11 Status Feedback Requirements...26
FB.12 Friends List Requirements...27 FB.13 Photo Albums Requirements...28 FB.14 Photos Requirements...29 FB.15 Write on Wall Requirements...30 FB.16 Wall Feedback Requirements...31 FB.16 Profile Requirements...31 FB.17 Inbox Requirements...32 FB.18 Events Requirements...33 FB.19 Event Repliers Requirements...34 FB.20 My Profile Requirements...35 FB.21 My Profile Feed Requirements...35 FB.22 Search Requirements...36 FB.23 Search Results Requirements...36 FB.24 Logout Requirements...37 VisAssist Twitter Navigator Overview...38 VisAssist Twitter Navigator Requirements...38 TW.1 Login Requirements...39 TW.2 Twitter Main Menu Requirements...40 TW.3 Twitter Feed...42 TW 4. New Tweet...44 TW 5. Profile...44 TW 6. Search Twitter...46 TW 7. Direct Messages...47 Non-Functional Requirements...49 System Evolution...49
Introduction Purpose Visually impaired individuals are unable to experience many of the benefits of accessing the mobile web. The web experience on mobile devices is centered around visual feedback. The layout of mobile websites is designed around visual cues and does not provide support for the visually impaired. This lack of accessibility inhibits them from utilizing popular social networks, e-commerce sites and digital encyclopedias. The VisAssist Web Navigator Application Suite solves the accessibility problem for the visually impaired through proper design including auditory feedback, haptic feedback and a specialized user interface. This document specifies the software requirements for the VisAssist Web Navigator. These requirements relate to the general user interface for the Web Navigator Application Suite. The individual applications adhere to the specifications and describe the user experience for each application and its related web service. Scope This document describes the requirements for version 1 of the following VisAssist Web Navigator Applications Application Suite: VisAssist Facebook Navigator, VisAssist Twitter Navigator, VisAssist Amazon Navigator and VisAssist MediaWiki Navigator. Applications VisAssist Web Navigator Menu System Overview The VisAssist Web Navigator Application Suite (VWNAS) offers a unified, intuitive user experience for the visually impaired. The VWNAS relies heavily on auditory descriptions of options and simple navigation. The following outlines basic menu navigation and content handling that is implemented by the individual applications. Individual application menus are navigated by using the following gestures: left or right to traverse a menu, Double Tapping to select a Menu Item, and a up swipe to exit a menu. Menu Items that denote actions or options that typically would be accessed by a button are handled in a Context Menu. This allows the user to easily choose the desired action. The content cursor provides access to the content of a Menu Item. It allows users to easily start and pause when the content is vocalized by the system. It also supports jumping forward and backward by sentences for easy traversal of large sections of text.
VisAssist Navigator UI Overview Definition of Terms 1. Menu Item Sibling: If a Menu Item has choices to its left or right these are its siblings. 2. One Finger Swipe: The user takes a single finger and swipes it on the screen. This can be done horizontally or vertically. 3. Two Finger Swipes: The user takes two fingers and swipes them on the screen. This can be done horizontally or vertically. 4. Single Tap: The user taps the screen once. 5. Double Tap: The user taps the screen twice in rapid succession. 6. Long Press: The user places their finger on the screen for 1 second without moving it.
7. Menu Item Navigate: The user swipes on the screen telling the Navigator that they wish to change the focus to Menu Item to the left or right of the currently active Menu Item. 8. Select: a Double tap on a Content Cursor item that is a button or leads to an action. 9. Menu Item Child: A Menu Item Child is the Menu Item activated by Selecting a Menu Item. 10. Cursor Queue: Metaphor for the progress of the currently selected Cursor Content. If the user stops the Cursor while it is reading a Cursor Item the remainder of what needs to be said will be remembered here. 11. Context Menu: a menu that holds items that lead to specific actions relevant to its parent Menu Item. 12. Context Menu Highlight: the current item in the Context Menu that the user has active. 13. Back Button: the device s back button. 14. Active: something is displayed to the screen. VisAssist Navigator User Interface Requirements UI.1 Menu Interactions UI.1.1 When a Menu Item becomes active the Application vocalized its name. UI.1.2 If the Menu Item does not have Siblings the user cannot Navigate left or right. If the user tries to swipe left or right the Application creates a negative auditory signal and vibrates once. UI.1.3 If the Menu Item has Siblings and the user Navigates left the Menu Item to the left becomes active (UI.1.1). UI.1.4 If the Menu Item has Siblings and the user Navigates right the Menu Item to the right becomes active (UI.1.1). UI.1.5 If the Menu Item is a child of another Menu Item and the user Navigates up makes the parent Menu Item active(ui.1.1).
UI.1.6 If the current Menu Item is not a Child of another Menu Item the user Navigates up the Application creates a negative auditory signal and vibrates once. UI.1.7 If the Menu Item has a Child Menu Item and the user Selects it, the Child Menu Item is made active(ui.1.1). UI.1.8 If the user Double Taps the Menu Item s name and description are spoken by the Application. UI.1.9 If the user Long Presses and the Menu Item has a Context Menu, it is becomes active. UI.1.10 If the user Long Presses and the Menu Item does not have a Context Menu the Application creates a negative auditory signal and vibrates once. UI.2 Context Menu Interaction UI.2.1 When a Context Menu becomes active its name is spoken by the Application and it s first item is Highlighted(UI.2.2). UI.2.2 When an item is Highlighted its name is spoken by the Application. UI.2.3 If the use does a Select action the Highlighted item is activated(ui.2.1). UI.2.4 If the user swipes up and more than one item exists then the previous item is Highlighted UI.2.5. The items are set up in a circle pattern so if the user swipes up on the first item it will wrap around the last item. UI.2.6 If the user swipes down and more than one item exists then then the next item is Highlighted (UI.2.2). The items are set up in a circle pattern so if the user swipes down on the last item it will wrap around the first item. UI.2.7 If one option is available and the user tries to swipe up or down the device will re-vocalize the current item s name and vibrate once.
UI.3 Content Container Interaction UI.3.1 If the User Double Taps, the Application is not speaking and there is nothing in the Cursor Queue then the current selected Cursor Item will begin to be read by the Application. UI.3.2 If the User Double Taps and the Application is speaking then the Application stops speaking and leaves the remainder of the selected Cursor Item on the Queue. UI.3.3 If the User Double Taps, the Application is not speaking and the Cursor Queue is not empty the Application begins saying what is in the Cursor Queue. UI.3.4 If the user swipes left with two fingers while the Application is reading a Cursor Item the Application will restart reading from the beginning of the current sentence. UI.3.5 If the user swipes left with two fingers and the Application is not reading from a Cursor Item then nothing happens. UI.3.6 If the user swipes right with two fingers and the Application is reading from a Cursor Item then the Cursor will jump ahead to the next sentence of the currently selected Cursor Item. UI.3.7 If the user swipes right with two fingers and the Application is not reading a Cursor Item then nothing happens. UI.4 Gestures UI.4.1 Drawing a D on the screen activates the root menu item to the user. This is the first screen viewed when the Application starts. UI.4.2 Drawing a h on the screen at any time has the current help text for the current view be read to the user on how to use the view and it s neighboring views to help with navigation.
Media Wiki Overview MediaWiki is a powerful backend for creating encyclopedia-style websites. It is the framework that powers one of the largest user generated and maintained databases of knowledge in the world, Wikipedia. Users are capable of searching for articles on almost any topic from quantum physics to ancient mayan rituals. Most of these encyclopedia-style websites do not have an interface that provides visually impaired users access, therefore the VisAssist MediaWiki Browser will communicate with the MediaWiki API and expose the functionality of Wikipedia to the visually impaired. Media Wiki Requirements
MW.1 Wiki Selection Menu Wiki Selection Menu. Two Wikis available in the selection menu. The user navigates between these by swiping left and right. Users select one by swiping down. MW.1.1 The Wiki Selection Menu contains each of the available MediaWiki sites in alphabetical order. MW.1.1.1 When selected, the MediaWiki site Menu Item takes the user to the Wiki Main Menu relevant to the MediaWiki site (MW.2).
MW.2 Wiki Main Menu. Wiki Main Menu. Two screens available in the wiki main menu. Users navigate between these by swiping left and right. Users select one by swiping down. MW.2.1 The Wiki Main Menu contains the following Menu Items in the following order: Search, View Saved Articles. MW.2.1.1 When selected, the Search Menu Item takes the user to the Article List populated with results (MW.4). MW.2.1.2 When selected, the View Saved Articles Menu Item presents an Article List Menu populated with articles that have been saved by the user (MW.4). MW.3 Search Menu MW.3.1 The Application displays an empty textbox for entering the search keyword. This is limited to 256 plaintext characters. It is registered as an Input Field. MW.3.2 When the user fills the search criteria textbox and navigates down, the Application takes the user to an Article List Menu populated with articles relevant to the search criteria (MW.4).
MW.4 Article List Menu Article List Menu. Two screens of the article list menu populated with article results. Users navigate between these by swiping left and right. Users select one by swiping down. MW.4.1 The Application contains a Menu Item for each article that can be active. MW.4.2 If the user navigates down on an Article, the application presents an Article Main Menu.
MW.5 Article Main Menu Article Main Menu. Three screens of the article main menu populated with the titles of each section of the article. Users navigate between these by swiping left and right. Users select one by swiping down. MW.5.1 The Article Main Menu contains the following Menu Items in the following order: Introduction, <Section 1>, <Section 2>,, <Section n>. MW.5.1.1 If the user navigates down on any of the Menu Items, the application presents the Section Main Menu for the section. MW.5.1.2 Each Menu Item displays it s title as well as the first image that appears in the section or nothing if there is no image. MW.5.2 The Article Main Menu contains an Article Context Menu. MW.5.3 The Article Context Menu contains the following options: MW.5.3.1 Save Article Only present if the user navigated to the article through the search menu. If the user selects this option the Application saves the article to the saved article menu. MW.5.3.2 Delete Saved Article Only present if the user navigated to the article through the saved articles menu. If the user selects this option the Application will remove the article from the list upon next launch.
MW.6 Section Main Menu Section Main Menu. Three screens of the section main menu, each populated with one discrete displayable item. Users navigate between these by swiping left and right. MW.6.1 The Section Main Menu contains a discrete displayable item per screen starting with the first item available in the section. MW.6.2 The discrete item types are: MW.6.2.1 Image The item displays Image as the title and presents the image along with the caption if one exists. MW.6.2.2 Text The item displays Text as the title and presents one paragraph of the section. MW.6.3 The user can navigate left and right between the discrete section items.
VisAssist Facebook Browser Overview Facebook is the leading social networking website in the world with over 845 million active users. It allows users to keep in touch with each other, share photos, coordinate events, and more. Despite the popularity of Facebook, there is no support by the website for visually impaired individuals. This is compounded by the fact that the website changes its format frequently, forcing the visually impaired to relearn the already complicated interface. By using the Facebook API, the VisAssist Facebook Browser will provide a consistent and easy to use interface for the visually impaired to use Facebook. VisAssist Facebook Navigator Requirements
FB.1 Login Requirements FB.1.1 Login is handled via Facebook's Single Sign On. FB.1.1.1 The VisAssist Facebook Navigator launches a pop-over web browser directed to the Facebook login view. FB.1.1.2 After logging in via the Facebook website, the browser is closed and user is taken back to the VisAssist Facebook Navigator.
FB.2 Main Menu Requirements FB.2.1 The Application presents the Main Menu after a successful login. FB.2.2 The Main Menu contains the following Menu Items in this order: News Feed, "Update Status", Friends, Inbox, Events, "My Profile", "Search", "Logout". FB.2.2.1 Each Menu Item contains the name of the Item and an icon used to represent the Item as an image. FB.2.2.2 When selected, the News Feed Menu Item takes the user to the News Feed containing news updates of the user and all of the user s friends (FB.3). FB.2.2.3 When selected, the "Update Status" Menu Item takes the user to the Update Status view (FB.10). FB.2.2.4 When selected, the Friends Menu Item takes the user to the Friends List containing all of the user s friends (FB.12). FB.2.2.5 When selected, the Inbox Menu Item takes the user to the Inbox (FB.17). FB.2.2.6 When selected, the Events Menu Item takes the user to their Events (FB.18). FB.2.2.7 When selected, the My Profile Menu Item takes the user to their Profile (FB.20). FB.2.2.8 When selected, the Search Menu Item takes the user to the Search view (FB.22). FB.2.2.9 When selected, the Logout Menu Item takes the user to the Logout view (FB.24).
FB.3 News Feed Requirements FB.3.1 The News Feed contains a menu of individual News Feed Items. FB.3.1.1 Each News Feed Item contains a name, one or two photos, a timestamp, and news text. FB.3.1.1.1 The name displayed is the profile name of the user that generated the news. FB.3.1.1.2 At least one photo is displayed. FB.3.1.1.2.1 If only one photo is displayed, it is the profile photo of the user that generated the news. FB.3.1.1.2.2 If two photos are displayed, the first photo is the profile photo of the user that generated the news, and the second is the image they shared. FB.3.1.1.3 The timestamp displays when the news was generated. FB.3.1.1.4 The news text displays the message associated with the news. FB.3.2 Each News Item is auto populated from Facebook as it gets generated. FB.3.2.1 Only the 25 most recent News Items are displayed in order from newest to oldest. FB.3.3 The Context Menu contains "Like or Unlike", "Post a Comment", View Likes and View Comments. FB.3.3.1 When Like or Unlike is selected, the user is taken to the Like or Unlike view (FB.4). FB.3.3.2 When Post a Comment is selected, the Application presents the Comment view (FB.6). FB.3.3.3 When "View Likes" is selected, the user is taken to the View Likes view (FB.8). FB.3.3.4 When "View Comments" is selected, the user is taken to the View Comments view (FB.9).
FB.3.4 Navigating left activates the next most recent item. FB..5 Navigating right activates the previous most recent item. FB.4 Like or Unlike Requirements FB.4.1 The Like or Unlike view contains a title and a body of text. FB.4.1.1 The title informs the user of their current status on the item; either they like it, or don't like it. FB.4.1.2 The body informs the user of the action required to change their opinion - "Navigate down to like/unlike". FB.4.2 Navigating down likes or unlikes the item and takes the user to the Like or Unlike feedback view (FB.5).
FB.5 Like or Unlike Feedback Requirements FB.5.1 The Like or Unlike Feedback view is arrived at after the user likes or unlikes an item. FB.5.2 The screen reads "You have liked/unliked that item" for successful completion. FB.5.3 An error is presented for unsuccessful completion.
FB.6 Post a Comment Requirements FB.6.1 The Post a Comment view contains a title and an empty textbox. FB.6.1.1 The title reads "Post a Comment". FB.6.2 Navigating down posts the comment in the text box and takes the user to the Comment Feedback view (FB.7).
FB.7 Comment Feedback Requirements FB.7.1 The Comment Feedback view is arrived at after the user submits a comment on an item. FB.7.2 The screen reads "Comment Posted." for successful completion. FB.7.3 An error is presented for unsuccessful completion.
FB.8 View Likes Requirements FB.8.1 The View Likes view contains a title and a body of text. FB.8.1.1 The number of likes is presented as the title. FB.8.1.2 The name of each person that liked the item is presented as the body.
FB.9 View Comments Requirements FB.9.1 The View Comments view contains a title, a photo, and a body of text. FB.9.1.1 The name of the commenter is presented as the title. FB.9.1.2 The profile picture of the commenter is presented as the photo. FB.9.1.3 The text of the comment is presented as the body of text.
FB.10 Update Status Requirements FB.10.1 The Update Status view contains a title and an empty textbox. FB.10.1.1 The title reads "Update Status". FB.10.2 When the user navigates down, the text in the text box is submitted as a status update and the user is taken to the Status Feedback view (FB.11).
FB.11 Status Feedback Requirements FB.11.1 The Status Feedback view is arrived at after the user posts a status update. FB.11.2 The screen reads "Status Updated" for successful completion. FB.11.3 An error is presented for unsuccessful completion.
FB.12 Friends List Requirements FB.12.1 The Friends List contains a menu of individual Friend Menu Items. FB.12.1.1 A Friend Menu Item contains the name of the friend. FB.12.1.2 A Friend Menu Item contains the profile picture of the friend. FB.12.2 The Context Menu contains "Photos" and "Write on Wall". FB.12.2.1 Selecting "Photos" takes the user to the Photo Albums view (FB.13). FB.12.2.2 Selecting "Write on Wall" takes the user to the Write on Wall view (FB.15). FB.12.3 When the user selects a friend, the Application presents the Profile of the friend (FB.16). FB.12.4 Navigating left activates the next Friend Item in the list. FB.12.5 Navigating right activates the previous Friend Item in the list.
FB.13 Photo Albums Requirements FB.13.1 The Photos view is a list of photo albums. FB.13.2 Each album contains the title of the album. FB.13.3 Each album contains the cover photo for the album. FB.13.4 Selecting an album takes the user to the Photos view (FB.14). FB.13.5 Navigating left activates the next photo album. FB.13.6 Navigating right activates the previous photo album.
FB.14 Photos Requirements FB.14.1 The Photos view is a list of Photos. FB.14.2 The Context Menu contains "Like or Unlike", "Post a Comment", View Likes and View Comments. FB.14.2.1 When Like or Unlike is selected, the user is taken to the Like or Unlike view (FB.4). FB.14.2.2 When Post a Comment is selected, the Application presents the Comment view (FB.6). FB.14.2.3 When "View Likes" is selected, the user is taken to the View Likes view (FB.8). FB.14.2.4 When "View Comments" is selected, the user is taken to the View Comments view (9). FB.14.3 Navigating left activates the next photo in the list. FB.14.4 Navigating right activates the previous photo in the list.
FB.15 Write on Wall Requirements FB.15.1 The Application displays a title and an empty textbox. FB.15.1.1 The title reads "Write on Wall". FB.15.2 Navigating down posts the message to the selected user's wall and takes the user to the Wall Feedback view (FB.16).
FB.16 Wall Feedback Requirements FB.16.1 The Wall Feedback view is arrived at after the user writes on another user's wall. FB.16.2 The screen reads "Wall post successful" for successful completion. FB.16.3 An error is presented for unsuccessful completion. FB.16 Profile Requirements FB.16.1 A Profile is a News Feed (FB.3) containing only news feed items relevant to the owner of the profile.
FB.17 Inbox Requirements FB.17.1 The Inbox is a list of messages. FB.17.1.1 The most recent message is active. FB. 17.1.2 Each message has a profile name of the person that sent it. FB. 17.1.3 Each message has the profile picture of the person that sent it. FB. 17.1.4 Each message has a timestamp. FB. 17.1.5 Each message has the content of the message. FB.17.2 Navigating down takes the user to the View Replies view. FB.17.2.1 The View Replies view is a list of comments (FB.9), where each comment is a reply to the original inbox message. FB. 17.3 Navigating left activates the next most recent message. FB. 17.4 Navigating right activates the previous most recent message.
FB.18 Events Requirements FB. 18.1 The Events view is a list of Event items. FB. 18.1.1 An Event consists of the name of the event, an event photo, a location, an owner, a time frame, and a description. FB.18.1.2 A time frame is a start time and an end time. FB. 18.2 The Context Menu contains Reply as Attending, Reply as Maybe Attending, Reply as Not Attending, "See Who's Attending", "See Who's Maybe Attending", "See Who's Not Attending", and "See Who Has Not Yet Replied". FB. 18.2.1 When the user selects Reply as Attending, the user is marked as attending the event. FB. 18.2.2 When the user selects Reply as Maybe Attending, the user is marked as maybe attending the event. FB. 18.2.3 When the user selects Reply as Not Attending, the user is marked as not attending the event. FB.18.2.4 When the user selects "See Who's Attending", "See Who's Maybe Attending", "See Who's Not Attending", or "See Who Has Not Yet Replied", the user is taken to the Event Repliers view (24). FB.18.3 Navigating down activates the Event Feed view. FB.18.3.1 The Event Feed view is a News Feed (FB.3) containing only those news feed items posted on the event's wall. FB.18.4 Navigating left activates the previous event.
FB.18.5 Navigating right activates the next event. FB.19 Event Repliers Requirements FB.19.1 The Event Repliers view consists of a title and a body of text. FB.19.1.1 The title presents the number of people in the selected category (Attending, Maybe Attending, Not Attending, or Not Yet Replied). FB.19.1.2 The body of text lists the names of the people in the respective category.
FB.20 My Profile Requirements FB.20.1 My Profile presents the name of the currently logged in user and their profile picture. FB.20.2 The Context Menu contains "Photos" and "Write on Wall". FB.20.2.1 Selecting "Photos" takes the user to their Photo Albums view (FB.13). FB.20.2.2 Selecting "Write on Wall" takes the user to the Write on Wall view (FB.15). FB.20.3 Navigating down takes the user to the My Profile Feed view (FB.21). FB.21 My Profile Feed Requirements FB.21.1 My Profile Feed is a News Feed (FB.3) containing only news feed items relevant to the currently logged in user.
FB.22 Search Requirements FB.22.1 The search view contains a title and an empty text box. FB.22.1.1 The title reads "Search Friends". FB.22.2 Navigating left and right switches between searching through friends and searching through everyone on Facebook. FB.22.3 Navigating down submits the search query and takes the user to the Search Results view. FB.23 Search Results Requirements FB.23.1 The Search Results view is a friends list (FB.12). FB.23.1.1 The list is made up of only the users who fit the search query.
FB.24 Logout Requirements FB.24.1 Selecting logout logs the user out of the application. FB.24.2 Upon successful logout, the user is presented with "You have logged out". FB.24.3 If the user is already logged out, the user is presented with "Error - you are not logged in".
VisAssist Twitter Navigator Overview Twitter is a popular micro-blogging social network that has over 300 million users. The Application can be accessed from the website, http://www.twitter.com or from an application available on multiple platforms including Android, ios, Windows Mobile, Windows, Mac OSX, and Linux. Once a user signs up for the service she can view 140 character messages posted from other users around the world. The small size of the messages posted to Twitter enables one to post links, status updates and real time information that can be accessed from any of the 300 million users. Twitter allows the user to create social networks by enabling a user to follow certain users. By using this feature of the service, one can create a custom news feed that presents real time messages. Twitter allows the user to send direct messages to anyone that is a member of the service (unless the user chooses to block this feature). The direct messages are not public and enable private communication between users. The VisAssist Twitter Browser presents an interface that enables a visually impaired user to access the site by implementing the VisAssist Web Navigator and Content Cursor while retrieving Twitter data from the Twitter API. VisAssist Twitter Navigator Requirements
TW.1 Login Requirements TW.1.1 (UI.4.1) Log out Menu Item
TW.2 Twitter Main Menu Requirements TW.2.1 The Main Menu is presented after a successful login (UI.4.1) TW.2.2 The Twitter Main Menu contains the following Menu Items: Twitter Feed, My Profile, Search, New Tweet, Direct Messages. Swipe Left Swipe Right Swipe Left Swipe Right
TW.2.2.1 The New Tweet Menu Item contains a label identifying it as New Tweet. This is Registered as a header. TW.2.2.2 The New Tweet Menu Item contains a picture of a plus and the Twitter logo. This Item is registered as an image. TW.2.2.3 Selecting the New Tweet Menu Item makes the New Tweet (TW.4) Menu Item active. TW.2.3 The Profile Menu Item contains a label identifying it as Profile. This is Registered as a header. TW.2.3.1 The Profile Menu Item contains a picture of the Twitter profile image. This is Registered as an image. TW.2.3.2 Selecting the Profile Menu Item makes the Profile (TW.5) Menu Item active. TW.2.4 The Search Twitter Menu Item contains a label identifying it as Search Twitter. This is Registered as a header. TW.2.4.1 The Search Twitter Menu Item contains a picture of a magnifying glass over the Twitter Logo. This is Registered as an image. TW.2.4.2 Selecting the Search Twitter Menu Item makes the Search Twitter(TW.6) Menu Item active. TW.2.5 The Twitter Feed Menu Item contains a label identifying it as a Twitter Feed. This is Registered as a header. TW.2.5.1 The Twitter Feed Menu Item contains a picture of the Twitter Feed image. This is Registered as an image. TW.2.5.2 Selecting Twitter Feed Menu Item makes the Twitter Feed(TW.3) Menu Item active. TW.2.5.3 The Direct Message Menu Item contains a picture of the Direct Message image. This is registered as an image. TW.2.5.4 Selecting Direct Message Menu Item makes the Direct Messages Menu Item active (TW.7.3).
TW.3 Twitter Feed TW.3.1 A list of Tweets based on user selected criteria. TW.3.1.1 Each Tweet contains an image view containing the profile image of the Tweeter. TW.3.1.2 Each Tweet contains a textbox that contains the users Twitter name. This is limited to 15 characters. TW.3.1.3 Each Tweet contains a textbox containing the Tweet message. This is limited to 140 characters. TW.3.2 Swiping left and right selects the next tweet in the feed list. Swipe Left Swipe Right TW.3.3 The first Tweet in the list is selected and announced upon loading the Twitter Feed.
TW.3.4 If the user performs a long press, a Context Menu is presented with Direct Message, New Tweet, Follow/UnFollow, Profile and Re Tweet. TW.3.4.1 If the Tweeter is already being followed, the Un Follow Context Menu Item is presented. TW 3.4.2 If the user selects Direct Message, the view is changed to the Direct Message View (TW.7). TW 3.4.3 If the user selects New Tweet, the view is changed to the New Tweet (TW.4). TW 3.4.4 If the user selects Un Follow, the view is changed to the the profile view of the user being followed/unfolled. (TW.7). TW 3.4.5 If the user selects Profile, the view is changed to the the profile view of the tweeter (TW.5). TW 3.4.6 If the user selects Re Tweet, the tweet is posted and the user is taken to the Twitter Feed view (TW.3)
TW.4. New Tweet TW.4.1 A textbox for the for the user's message. This is limited to 140 characters. TW.4.2 An accessible keyboard is presented to the user. TW.4.3 Swiping down posts the tweet. TW.5. Profile TW.5.1 The user name of the profile is announced. TW.5.2 An image containing the users profile picture. TW.5.3 A label containing the user's Twitter name. This field is limited to 15 characters. TW 5.4 Sibling views containing other profile information are selected by swiping left and or right. TW.5.4.1 A label and text view containing the screen name. TW.5.4.2 A label and text view containing the number of tweets. TW.5.4.3 A label containing location information. TW.5.4.4 A label and text view containing profile description. TW.5.4.5 A label and text view showing count of followers. TW.5.4.5 A label and text view containing count of following. TW.5.5 A long press produces a Context Menu with Direct Message.
Swipe Left Swipe Right
TW.5.5.1 "Direct Message" is announced as the first item in the Context Menu. TW.5.5.2 If a user selects "Direct Message", the user is directed to the Direct Message dialogue (TW.7). TW 6. Search Twitter TW.6.1 Enter your search dialogue is announced to the user. TW.6.2 A textbox is for the search entry is presented. This field is limited to 50 characters. TW 6.2.1 Swiping down posts the query. TW.6.2.2 An accessible keyboard is presented to user.
TW.6.2.3 If the query fails, Nothing found is announced to the user and the user is prompted for another search. TW.6.2.4 If the query is successful, a Twitter Feed is announced and the user is directed to the Twitter Feed (TW.3) containing the results. Swipe Left Swipe Right TW.7. Direct Messages TW.7.1 When activated from Main Menu, a feed list of Direct Messages is presented in the view. TW.7.1.1 When the user swipes left or right, each Direct Message is presented and announced to user. TW.7.2 If a Context Menu is activated, the user is presented with the New Tweet. TW.7.3 A keyboard for entry is presented to the user.
TW.7.4 When the user swipes down, the direct message is sent.
Non-Functional Requirements 1. Software Constraints a. Android Operating System Version 2.2 or above b. Android APK (compiled source and resources) must be smaller than 50mb c. Minimum of two touch points supported by the touch screen d. Android Text To Speech 2. Hardware Constraints a. Internet Connection (Mobile Network or Wifi) 3. Acceptance Constraints a. Before accepting the system, the developers must complete the following: b. Demo the working system and any features upon request. c. Prove that all Priority 1 functional requirements are met. d. Provide sufficient test cases to show that the system is complete and correct System Evolution In the future the VisAssist Navigator Suite will be expanded to support more features. These include but are not limited to: 1. Additional Websites a. The Navigator Suite can be expanded to support more websites and potentially support web sites instead of web services with public API s. 2. Voice Commands a. These would allow the users to interact without using gestures and increase usability of the application. 3. Integration with future Android accessibility Services a. Android 4.0 greatly expanded the built in accessibility service and updating the Navigator Suite to use it would allow for a more seamless user experience.