Accessibility Instrument Survey

This chapter presents the main results of the Accessibility Instrument Survey (AIS), collecting basic information on each of the accessibility instruments reviewed in this report (for more detail on these Instruments see Chapter 3). The aim of the survey was to enable quick, objective and comparable overviews of each of the reviewed accessibility instruments. The information collected will enable the categorization of accessibility instruments present in this research, aiming to be a reference for future categorization of accessibility instruments for planning practice. These categories will support the analysis of the coverage of accessibility instruments in this research, i.e., identify how representative this research is across different accessibility instrument types. In addition, these will be used to analyse the characteristics and concerns which most frequently underlie the development of accessibility instruments. Finally, the survey also collects developer’s perceptions on the usefulness of their accessibility instruments in planning practice, enabling the first insight into the main research question of this COST Action, although limited to the developer’s point of view. In summary, the results of the survey will be used for four purposes: Development of an accessibility instrument sheet for each accessibility instrument summarizing its main characteristics (Appendix A); Identify the coverage of accessibility instrument types present in this research (Section 4.3.1) discussing the representativeness of this Action; Provide a glimpse on the characteristics and concerns which most frequently underlie the development of accessibility instruments (Section 4.3.2); Provide a first insight into the perceived usefulness of accessibility instruments in planning practice from the point of view of the developer (Section 4.3.2 and Section 4.3.3). The next section provides an overview of the Survey describing the information collected. This section also describes the development process of this survey including data collection, dates and means. The results of the survey are analysed in the third section starting with a discussion on the coverage of accessibility instruments reviewed by this research (Section 4.3.1), identifying accessibility measure types which are represented and which are absent. This discussion is accompanied by the presentation of the main categories of accessibility instruments from the perspective of the end user. These categories try to summarize the main concerns planning practitioners are expected to have when searching for an accessibility instrument and is built upon some of the information collected by the survey. Following, the third section also presents a general analysis of the results (Section 4.3.2), focussing on the dominant characteristics of the accessibility instruments reviewed and on the developer’s perception of the usefulness their instrument will have for end users. The section ends with a brief cross analysis of results (Section 4.3.3) trying to identify relationships between accessibility instrument characteristics and perceptions of usefulness by developers. The fourth and last section presents the main conclusions of this study.

The user's view level of the GOQL graphical query language

The paper addresses issues related to the design of a graphical query mechanism that can act as an interface to any object-oriented database system (OODBS), in general, and the object model of ODMG 2.0, in particular. In the paper a brief literature survey of related work is given, and an analysis methodology that allows the evaluation of such languages is proposed. Moreover, the user's view level of a new graphical query language, namely GOQL (Graphical Object Query Language), for ODMG 2.0 is presented. The user's view level provides a graphical schema that does not contain any of the perplexing details of an object-oriented database schema, and it also provides a foundation for a graphical interface that can support ad-hoc queries for object-oriented database applications. We illustrate, using an example, the user's view level of GOQL