This paper presents an account of the experience observed when obtaining a set of requirements for the development of educational software for people with impaired vision. Numerous techniques of requirements engineering, specifically review and prototyping techniques, were applied to elicit, analyze, and validate 51 requirements for educational software for the vision impaired. Requirements were documented and subdivided in functional requirements (FR) and non-functional requirements (NFR). To improve the understanding of these requirements, they were represented via Use Cases at UML. The results were the elicitation, analysis and negotiation, modeling, and validation of 40 functional requirements, and 11 non-functional requirements, as well as the diagram of the resultant of use cases.