6,620 research outputs found

    Exploring Accessibility Features and Plug-ins for Digital Prototyping Tools

    Get PDF
    Many digital systems are found to be inaccessible and a large part of the issue is that accessibility is not considered early enough in the design process. Digital prototyping tools are a powerful resource for designers to quickly explore both low and high fidelity design mockups during initial stages of product design and development. We evaluated 10 popular prototyping tools to understand their built-in and third-party accessibility features. We found that accessible design support is largely from third-party plug-ins rather than prototyping tools\u27 built-in features, and the availability of accessibility support varies from tool to tool. There is potential to improve accessible design by increasing the potential for accessibility to be consider earlier in the design process

    Web-based multimodal graphs for visually impaired people

    Get PDF
    This paper describes the development and evaluation of Web-based multimodal graphs designed for visually impaired and blind people. The information in the graphs is conveyed to visually impaired people through haptic and audio channels. The motivation of this work is to address problems faced by visually impaired people in accessing graphical information on the Internet, particularly the common types of graphs for data visualization. In our work, line graphs, bar charts and pie charts are accessible through a force feedback device, the Logitech WingMan Force Feedback Mouse. Pre-recorded sound files are used to represent graph contents to users. In order to test the usability of the developed Web graphs, an evaluation was conducted with bar charts as the experimental platform. The results showed that the participants could successfully use the haptic and audio features to extract information from the Web graphs

    A framework for developing engineering design ontologies within the aerospace industry

    Get PDF
    This paper presents a framework for developing engineering design ontologies within the aerospace industry. The aim of this approach is to strengthen the modularity and reuse of engineering design ontologies to support knowledge management initiatives within the aerospace industry. Successful development and effective utilisation of engineering ontologies strongly depends on the method/framework used to develop them. Ensuring modularity in ontology design is essential for engineering design activities due to the complexity of knowledge that is required to be brought together to support the product design decision-making process. The proposed approach adopts best practices from previous ontology development methods, but focuses on encouraging modular architectural ontology design. The framework is comprised of three phases namely: (1) Ontology design and development; (2) Ontology validation and (3) Implementation of ontology structure. A qualitative research methodology is employed which is composed of four phases. The first phase defines the capture of knowledge required for the framework development, followed by the ontology framework development, iterative refinement of engineering ontologies and ontology validation through case studies and experts’ opinion. The ontology-based framework is applied in the combustor and casing aerospace engineering domain. The modular ontologies developed as a result of applying the framework and are used in a case study to restructure and improve the accessibility of information on a product design information-sharing platform. Additionally, domain experts within the aerospace industry validated the strengths, benefits and limitations of the framework. Due to the modular nature of the developed ontologies, they were also employed to support other project initiatives within the case study company such as role-based computing (RBC), IT modernisation activity and knowledge management implementation across the sponsoring organisation. The major benefit of this approach is in the reduction of man-hours required for maintaining engineering design ontologies. Furthermore, this approach strengthens reuse of ontology knowledge and encourages modularity in the design and development of engineering ontologies

    Assessing the Accuracy of Vendor-Supplied Accessibility Documentation

    Get PDF
    Purpose – In an effort to ensure vendor compliance with Section 508, some libraries have begun requesting Voluntary Product Accessibility Templates (VPATs) or other documentation of accessibility compliance. The purpose of this paper is to assess the accuracy of vendor-supplied compliance documentation, and to identify common accessibility issues highlighted by the VPATs. A detailed discussion of vendor responses to each Section 508 checkpoint is provided in the Appendix. Design/methodology/approach – Researchers compared 17 VPATs with the results of an automated accessibility scan to identify inconsistencies and common problems. Findings – Vendors reported being fully compliant with 64 percent of the applicable VPAT items, and partially compliant with a further 24 percent. However, in 16 of 17 cases, there were discrepancies between the information on the VPAT and the results of the scan. Of the total 189 VPAT checkpoints the author scanned, 19.6 percent had errors (meaning the information on the VPAT was inaccurate 19.6 percent of the time). Research limitations/implications – Several VPAT checkpoints could not be automatically verified by the scan. Instead they require manual/visual verification, which the author did not do. Because the author only scanned three pages of each resource, the author was not able to check all content. Practical implications – Vendor-supplied accessibility documentation should not be taken at face value, but requires verification and follow up to ensure its accuracy. This study also identified some of the most common accessibility issues, which will help both librarians and vendors improve their products and services. Originality/value – Other studies have analyzed the accessibility of library resources and specifically vendor databases, but none have assessed the accuracy of vendor-supplied Section 508 compliance documentation

    Accessibility barriers for users of screen readers in the Moodle learning content management system

    Get PDF
    In recent decades, the use of the Internet has spread rapidly into diverse social spheres including that of education. Currently, most educational centers make use of e-learning environments created through authoring tool applications like learning content management systems (LCMSs). However, most of these applications currently present accessibility barriers that make the creation of accessible e-learning environments difficult for teachers and administrators. In this paper, the accessibility of the Moodle authoring tool, one of the most frequently used LCMSs worldwide, is evaluated. More specifically, the evaluation is carried out from the perspective of two visually impaired users accessing content through screen readers, as well as a heuristic evaluation considering the World Wide Web Consortium's Authoring Tool Accessibility Guidelines. The evaluation results demonstrate that Moodle presents barriers for screen reader users, limiting their ability to access the tool. One example of accessibility problems for visually impaired users is the frequent inability to publish learning contents without assistance. In light of these results, the paper offers recommendations that can be followed to reduce or eliminate these accessibility barriers.This study has been partially funded by the MA2VICMR (S2009/TIC-1542) research project.Publicad

    Evaluating educational Web sites

    Full text link
    A rubric was created to compare and contrast Web sites based on four criteria: (a) technical aspect, (b) types of content available, (c) authority and, (d) accessibility. The rubric was designed to compare sites to one another. The sites were also grouped into categories: (a) higher education sites, (b) content sites, (c) commercial sites, (d) school districts. The categories were also compared to each other; To compare the sites to each other, a percentage score was given for each of the four criteria. A total percentage score was also given to each site. The score for all of the sites evaluated for each criterion was averaged and used as a category score to compare the categories
    • …
    corecore