ACCESSIBLE project concept and achievements


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

ACCESSIBLE project concept and achievements

  1. 1. Project Presentation and Achievements Dimitrios Tzovaras CERTH/ITI
  2. 2. The ACCESSIBLE Project Objetives Objectives Main Objective 1 (MO1) - To research and develop an Assessment Simulation module to support the overall analysis and verification accessibility procedure of Web applications and services, mobile applications as well as description languages Main Objective 2 (MO2) – To research and develop for the first time a Harmonized Accessibility Methodological framework (HAM ) Secondary Objective 1 (SO1) - Development of a developer/designer-aid module for the design and development of Java applications <ul><li>Development of a multilayer ontology based knowledge Resource for incorporating the ACCESSIBLE harmonised methodology (MO2)) </li></ul><ul><li>Development of an EARL based Reporting module in order to export results in a form, helpful to potential receivers of test results </li></ul>
  3. 3. ACCESSIBLE: Consortium partners <ul><li>Industries (1) </li></ul><ul><ul><li>Sun Microsystems (PRAGUE) </li></ul></ul><ul><li>Research Institutes (3) </li></ul><ul><ul><li>CERTH/ITI (GREECE) </li></ul></ul><ul><ul><li>CERTH/HIT (GREECE) </li></ul></ul><ul><ul><li>FORTH-ICS (GREECE) </li></ul></ul><ul><li>Universities (2) </li></ul><ul><ul><li>USTUTT (GERMANY) </li></ul></ul><ul><ul><li>FFCUL (PORTUGAL) </li></ul></ul><ul><li>SMEs (4) </li></ul><ul><ul><li>SOFTECO (ITALY) </li></ul></ul><ul><ul><li>SOLINET (GERMANY) </li></ul></ul><ul><ul><li>MCA (BULGARIA) </li></ul></ul><ul><ul><li>NETSCOUTS (GERMANY) </li></ul></ul><ul><li>Strong consortium </li></ul><ul><li>Scientific expertise : accessibility, HCI, simulation, ontologies, semantic web and inference engines </li></ul><ul><li>Industrial and SMEs expertise : software providers, accessible software design and development, info mobility services </li></ul><ul><li>End Users (people with disabilities): MCA, NETSCOUTS </li></ul>
  4. 4. ACCESSIBLE t arget user groups <ul><li>Software Developers and designers that will use ACCESSIBLE in order to support them for the development and testing of accessible software applications </li></ul><ul><li>Groups and public bodies involved in policy making and providing basis for policy making - public bodies and SMEs dealing with e-accessibility, International Organisations for disabled persons, etc </li></ul><ul><li>Service providers and software SMEs - public and private enterprises and organisations responsible for the development of software applications </li></ul><ul><li>Users who benefit from enhanced accessibility - User groups with various disabilities (e.g. wheelchair users, blind, deaf, elderly, etc.). </li></ul>
  5. 5. Barriers to e-Accessibility & ACCESSIBLE Innovation <ul><li>Main Barriers </li></ul><ul><li>Assessment methodologies exist only for Web applications </li></ul><ul><li>The implemented standards and best practices around accessibility are somewhat confusing and incomplete </li></ul><ul><li>Lack of a conceptual simulation framework for the design and development of Java applications </li></ul><ul><li>Lack of methodologies dealing with more than one disability </li></ul><ul><li>Innovation </li></ul><ul><li>ACCESSIBLE will develop a novel assessment methodology for a broad set of application environments (web applications, web services, standard description languages (e.g. SDL), mobile applications </li></ul><ul><li>ACCESSIBLE will implement a Harmonized Accessibility Methodological framework (HAM) </li></ul><ul><li>ACCESSIBLE, will provide a holistic accessibility simulation approach, by developing a common assessment simulation module in order to provide designers / developers / testers with appropriate accessibility assessment tools for testing the accessibility of their software applications </li></ul><ul><li>ACCESSIBLE will introduce for the first time a complete ontological framework (Multilayer ontology based knowledge Resource), for assessing new multi-domain applications in terms of accessibility </li></ul><ul><li>An open source developer-designer aid module for the design and development of Java applications </li></ul><ul><li>Support the assessment based on combination of disabilities, standards, devices, and applications </li></ul>
  6. 6. The ACCESSIBLE Architecture ACCESSIBLE User Interface EARL Reporting Tool Developer & designer aid Module Ontology based Knowledge Resource and Inference engine Assessment Simulation Module
  7. 7. <ul><li>ACCESSIBLE proposes four innovative pilots evaluating the accessibility of the implemented prototypes. At least one application per each pilot domain will be tested within the ACCESSIBLE environment. </li></ul><ul><ul><li>Mobile Web applications assessment – ( FFCUL , SUN) </li></ul></ul><ul><ul><li>Web services assessment - infomobility and ASK-IT compliant web services - ( SOFTECO & CERTH/ITI) </li></ul></ul><ul><ul><li>Web applications assessment – e.g. Web based ecommerce application for goods & Web based ecommerce application for office supplies - ( NETSCOUTS) </li></ul></ul><ul><ul><li>Description languages (e.g. SDL) assessment - e.g. Next generation telecommunication services - ( SOLINET) </li></ul></ul>ACCESSIBLE Application Scenarios
  8. 8. Web Applications Assessment <ul><li>Extendable in order to support more standards/guidelines </li></ul><ul><ul><li>New standard support: new guidelines, checkpoints, maybe rules added in the ontology. </li></ul></ul><ul><ul><li>New standard using similar approaches (primitive tests) with the already supported standards, not even a single line of source code has to be changed! </li></ul></ul><ul><li>Updates to new versions straightforward </li></ul><ul><ul><li>Ontology update (new instances, rules, properties)  no need for source code change. </li></ul></ul><ul><li>The accessibility score of the examined web page(s) is being calculated </li></ul><ul><ul><li>A normalized version of the WAB (Web Accessibility Barrier) metric is being used that takes into account the priority of the checkpoints. </li></ul></ul><ul><li>The Web Assessibility Assessment tool supports many additional tests providing warnings ( possible errors ) and extra information (ex. total number of the tables, images, etc., Tips) concerning the structure of the web application. </li></ul><ul><li>I nnovation compar ed to Hera, BenToWeb, WALIDATOR, WAVE, TAW, etc. : support of various standards / guidelines / disabilities / assistive technologies via a unique framework ( ACCESSIBLE H AM). </li></ul><ul><li>Adaptive/Semi-automatic selection of tests </li></ul><ul><ul><li>Manual selection (using checkboxes) </li></ul></ul><ul><ul><li>Using the knowledge stored in the ACCESSIBLE ontology </li></ul></ul><ul><ul><ul><li>Choose the tests that correspond to one (or more) specific Standard / Personas/ Impairment / Disability / Functional Limitation / Assistive technology (devices) </li></ul></ul></ul>
  9. 9. Accessibility of Web Services <ul><li>Introducing the notion of Accessibility in Web Services towards their effective utilization </li></ul><ul><li>Why? </li></ul><ul><ul><li>To ensure that HCI through applications </li></ul></ul><ul><ul><li>utilizing Web Services is Accessible </li></ul></ul><ul><li>How? </li></ul><ul><ul><li>By assessing </li></ul></ul><ul><ul><ul><li>The capability of Web Services to provide content which is accessible to the end users (diabled) of the client applications </li></ul></ul></ul><ul><ul><ul><li>The capability of Web Services to interact well with the client applications utilizing their functionality </li></ul></ul></ul><ul><li>Result: </li></ul><ul><ul><li>Enhancing the interaction between client applications and Web Services with WS Accessibility features </li></ul></ul><ul><ul><li>Ensuring that the client app – WS interaction part of the WS utilization chain allows for accessible HCI at the user – client app Level </li></ul></ul><ul><li>Accessible defines an Accessibility Framework ensuring that Web Services </li></ul><ul><ul><li>Are well-defined, well-working and easy to integrate within client applications </li></ul></ul><ul><ul><ul><li>Introducing Accessibility at the Service’s Operational Level </li></ul></ul></ul><ul><ul><li>Provide content which is accessible to impaired users </li></ul></ul><ul><ul><ul><li>Introducing Accessibility at the Service’s delivered content Presentation Level </li></ul></ul></ul><ul><ul><li>Provide information actually helpful to impaired users, adapted to their needs </li></ul></ul><ul><ul><ul><li>Introducing Accessibility at the Service’s delivered content Information Level </li></ul></ul></ul>
  10. 10. Mobile Assessment Module <ul><li>Foreseen added value </li></ul><ul><ul><li>A set of assessment practices to aid designers and developers evaluate Accessibility of Web sites for mobile devices </li></ul></ul><ul><ul><li>Focus on similarities/differences between Mobile Web and Accessibility, to decrease the burden of improving adequacy to people with disabilities in mobile scenarios </li></ul></ul><ul><ul><li>Starting point for Mobile Accessibility for different technologies </li></ul></ul><ul><li>Innovation </li></ul><ul><li>Mobile Accessibility is just starting to be researched (hot topic!) </li></ul><ul><li>Bridged Mobile Web Best Practices (MobileOK subset) and Web Content Accessibility Guidelines (WCAG) to come with a superset of assessments towards Mobile Accessibility </li></ul><ul><li>Application of WCAG in non-desktop scenarios (e.g., tailored mobile content) </li></ul>
  11. 11. Description Languages Assessment <ul><li>The problem </li></ul><ul><ul><li>System design requires checking for accessibility in order to provide accessible applications </li></ul></ul><ul><ul><li>Lack of standards and guidelines for accessibility </li></ul></ul><ul><li>The challenge </li></ul><ul><ul><li>Accessibility checking at system design level in order to tackle accessibility issues of applications at an early development stage </li></ul></ul><ul><ul><li>Allow developers to early accessibility checking at system design level </li></ul></ul><ul><li>The ACCESSIBLE innovation </li></ul><ul><ul><li>Define accessibility guidelines and associated techniques for description languages focused on GUI designs </li></ul></ul><ul><ul><li>Develop the description languages accessibility assessment tool by implementing the assessment techniques and provide implementation guidelines to the developers </li></ul></ul>
  12. 12. Developer-designer aid (simulator) module <ul><li>Innovation </li></ul><ul><ul><li>An open source tool for the simulation of disabilities (visual and upper limp impairments) for JAVA implementations (to help users to understand how capability loss affects the ability to interact with software applications and services) </li></ul></ul><ul><ul><li>A plug-in version for the NetBeans IDE in addition to the standalone (developers often don't want to use applications that are excluded from the main IDE software packages they prefer to use) </li></ul></ul><ul><ul><li>Integration of the module with the Java Accessibility API </li></ul></ul><ul><li>The problem </li></ul><ul><ul><li>Existing development tools and packaged solutions give little out-of-the-box assistance to users for the accessibility design of ICT Java solutions </li></ul></ul><ul><ul><li>There is a obvious shortage of simulators for Java Swing applications </li></ul></ul><ul><ul><li>Most of existing vision impairment simulators are independent applications and not offered through common Integrated Development Environments </li></ul></ul>
  13. 13. ACCESSIBLE Public Results <ul><li>Public Deliverables </li></ul><ul><li>ACCESSIBLE ontology </li></ul><ul><li>Tools Downloading </li></ul><ul><li>Publications </li></ul>
  14. 14. Thank you for your attention! <ul><li>Questions, comments </li></ul>