572
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − ;Task: Identify which Sugar activities are in need modifications to support special needs. Research global changes to Sugar that could enhance the platform in regards to all users.+ − + + + + + + + + + + + + + + + + + + + + +
GoogleCodeIn2012/Special needs (view source)
Revision as of 10:28, 28 November 2012
, 10:28, 28 November 2012no edit summary
;Background: Sugar and Sugar activities by-and-large have been written with little consideration of the special needs of, for example, the visually impaired learner, the learner with motor difficulties or cognitive challenges.
;Background:
Sugar and Sugar activities by-and-large have been written with little consideration of the special needs of, for example, the visually impaired learner and the learner with motor difficulties.
;Contact: The Sugar Activity Team
;Task:
Define 2 basic scenarios, one per type of difficulty (IE, vision and motor). Each scenario should describe the problems (barriers) and (suggested) solutions that could exists in order to complete the next daily tasks:
(a) The user wants to access the different Sugar views (neighbourhood, friends and home) and frame options, and interact with these options.
(b) The user wants to access the control panel, browse the options and modify them.
(c) The user wants to access the journal, browse the entries and modify its properties.
(d) The user wants to access the list of activities, and start one.
(e) The user wants to access the activity tool-bar options and interact with the activity (use at least 3 activity as example).
(f) The user wants to manage (activate, deactivate and modify properties) of the the solutions you proposed.
If the solutions are general enough, you can reference them from another daily task.
;Contact:
The Sugar Activity Team
[[Category: GCI2012]]
[[Category: GCI2012]]