Access Toolkit for Education

Wald, Mike; Draffan, E.A.; Newman, Russell; Skuse, Sebastian; Phethean, Chris

doi:10.1007/978-3-642-31522-0_8

Cited by 3 publications

(3 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…They did not know how to zoom in or zoom out text. It complies with UK website development criteria [19] and W3C website development criteria that everyone can access [15]. Therefore, the researcher has specified this problem in the criteria 14.…”

Section: Interview Resultsmentioning

confidence: 99%

“…Simply translating the original English Web Accessibility them doesn't necessarily solve localisation problems of Thailand context and language and. WebThai2access builds on a previous approach by the 2 nd Author [19] and was developed with a holistic view [20]. This research is the first experimental study to examine the ease of use or reliability of the method of using 15 criteria with accompanying techniques in a web-based tool.…”

Section: Webthai2accessmentioning

confidence: 99%

See 1 more Smart Citation

Development and testing of a thai website accessibility evaluation tool

Angkananon

Wald

Ploadaksorn

2020

IJECE

Self Cite

View full text Add to dashboard Cite

This paper deals with the important problem that there is no help with the accessibility evaluations of Thailand’s web by developing and evaluating a new method and tool online, WebThai2Access, with experts, developers, and users with disabilities. This tool was evaluated by 30 developers, 30 hearing impaired people, 30 visually impaired people, and 30 elderly people. The developers evaluated the websites whereas experimental tasks were given to each disabled group based on the problems they had accessing web information. The developers found WebThai2Access very usable and the 15 test criteria were reliable for evaluating websites. The lower and upper 95% limits for confidence ratings of developers were minus or plus 10% for YouTube and Pantip websites and minus or plus 3% with the blind association website. The 95% lower and upper limits of confidence were minus or plus 5% for hearing impaired users, minus or plus 2% for elderly users and minus or plus 0% for visually impaired users. The results therefore showed WebThai2Access was reliable and accessible for developers whose evaluations reasonably well predicted website accessibility for users with disabilities.

show abstract

Section: Interview Resultsmentioning

confidence: 99%

Section: Webthai2accessmentioning

confidence: 99%

Development and testing of a thai website accessibility evaluation tool

Angkananon

Wald

Ploadaksorn

2020

IJECE

Self Cite

View full text Add to dashboard Cite

show abstract

“…A similar tool has been developed by the University of Southampton, called ATbar [6,8]. It is a cross-browser plugin that, once installed on the user's browser, adds a toolbar to any Web page.…”

Section: Atbarmentioning

confidence: 99%

Towards Deep Adaptivity – A Framework for the Development of Fully Context-Sensitive User Interfaces

Zimmermann

Vanderheiden

Strobbe

2014

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Adaptive systems can change various adaptation aspects at runtime, based on an actual context of use (the user, the platform, and the environment). For adaptable systems, the user controls the adaptation aspects. Both adaptivity and adaptability are pre-requisites for context-sensitive user interfaces that accommodate the needs and preferences of persons with disabilities. In this paper, we provide an overview of the various adaptation aspects and describe a general framework consisting of six steps for the process of user interface adaptation. Based on the framework, we describe our vision of combining the GPII and URC technologies to achieve fully context-sensitive user interfaces.Keywords: Adaptive user interface, adaptable user interface, user interface adaptation, user interface adaptation aspect, context-sensitive user interface, abstract user interface, Universal Remote Console (URC), Global Public Inclusive Infrastructure (GPII), Cloud4all. IntroductionSystems that adapt their user interfaces in one or more aspects (e.g. font size, navigation structure, closed captions) have been around for a while. However, existing systems tend to focus on selected aspects of adaptations, addressing only the needs of a particular user group. For fully context-sensitive user interfaces it is important to cover the full range of adaptations that is required to address the wide range of needs and preferences of all users, including those that are ageing and those with disabilities. The remainder of this paper is structured as follows: Section 2 introduces basic concepts of user interface adaptation and a 3-layer model of user interface adaptation aspects. Section 3 looks at selected previous work with varying coverage of user interface adaptation (based on the 3 layers of user interface adaptation aspects). The main contribution of this paper is presented in section 4, where we describe a six-step framework for the development of fully context-sensitive user interfaces. Section 5 describes how a combination of the Global Public Inclusive Infrastructure (GPII) and the Universal Remote Console (URC) framework can produce fully context-sensitive user interfaces with all six steps involved. Finally, section 6 provides a conclusion. 300 G. Zimmermann, G.C. Vanderheiden, and C. Strobbe User Interface Adaptation Terms and ConceptsIn this section, we define basic terms and concepts that are necessary for a common understanding on the topic of this paper. User Interface AdaptationWe define user interface adaptation as a process spanning development time (i.e. when the application is developed and its user interface is designed) and runtime (i.e. when the user interface is shown to the user and the user interacts through it with the application). The activities in this process serve the purpose of preparing and instantiating a user interface in which at least some aspects are tailored (adapted) to the specific context of use at runtime. We will come back to the question what these user interface aspects are in section 2.5....

show abstract