This is the backend concept coding web server containing the reference ontologies and the reference representation dictionaries. The service will provide a mechanism for moderating extensions to the concept code database, for adding and extending representation sets and for adding natural language sets. A developer forum will be hosted to assist developers to interact when build client based bridges and local user ontology mechanisms.
The Trialing Methodology Guidelines encapsulate the practical experience gained from the trials in the WWAAC project. They give a set of concrete recommendations about the running of trials of Internet services with AAC users. Essentially, the evaluation plan consists of 8 main phases: Simulation study; Evaluation of the WWAAC web browser, alpha version; Evaluation of the WWAAC email program, alpha version; Pilot evaluation of the linguistic support module; Evaluation of the browser and email software, beta version; Longitudinal case study of the browser and the email; Longitudinal case study of the supportive writing software; and Additional investigations, or user consultations. Since the population of AAC users is a heterogeneous one and variation is common in both performances in the use of technology, as well as in an individual's performance over time, the approach is a qualitative one and expected to be applied with flexibility.
The WWAAC project's Web Authoring Accessibility Guidelines encapsulate the practical experience gained from the trials in the WWAAC project. Discussions on a number of issues helped to form a basis for guideline development: whether to have one site for all or two alternative sites, the conflicting needs of users, simplicity of content, summaries of content, top loading, tagging images, navigation mechanisms, and search engines. These discussions, along with the project's user requirements and evaluation work, have led to 8 recommendations. These are proposed as success criteria, examples and strategies to be included in the W3C Web Accessibility Initiative's (WAI) draft Web Content Accessibility Guidelines (WCAG 2.0). In summary, the recommendations are as follows: Recommendation 1: Provide a clear representational image on the site's home page. Recommendation 2: Alt tags should provide prime information for the user, and should distinguish between salient (most prominent) and non-salient content. Recommendation 3: Provide simple page descriptions as metadata. Recommendation 4: Add clear in-page link such as 'Skip-to-content' near the top of the page (as some Web developers already do). Recommendation 5: Consider the number, location and focus of links on a page. Recommendation 6: Provide a progressive complexity for both site and page content, so that people with different abilities may be able to obtain information from the same Web site. Recommendation 7: Use static, rather than dynamic, content for critical parts of the Web site. Recommendation 8: Consider a change of priorities in the Web Content Accessibility Guidelines to reflect the findings of the UK's Disability Rights Commission report (2004).
This is the framework architecture for the concept coding functionality, both at the system level and the detailed syntactic level of the exchange of information at the concept level. It will provide the following high-level functionality for AAC users: - To access to information delivered via the WWW - To communicate synchronously and asynchronously with people via the Internet - To enable multimodal interaction between different AAC systems independently of the Internet. An important element of this framework is the architecture for providing the CCF engine to be incorporated in client software to enable access to services such as browsing, e-mailing and chatting.