• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
W4a11 accessibility at early stages insights from the designer perspective-martin-cechich-rossi
 

W4a11 accessibility at early stages insights from the designer perspective-martin-cechich-rossi

on

  • 415 views

 

Statistics

Views

Total Views
415
Views on SlideShare
415
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    W4a11 accessibility at early stages insights from the designer perspective-martin-cechich-rossi W4a11 accessibility at early stages insights from the designer perspective-martin-cechich-rossi Presentation Transcript

    • Accessibility at Early Stages: Insights from the Designer Perspective Adriana Martín, Alejandra Cechich and Gustavo Rossi
    • Summary1. Motivation and Objective2. Overview of Our Proposal 2.1 Background Issues 2.2 An Aspect-Oriented Approach through a case study3. Outline of the Experience Gathered on the Field4. Conclusions and Future Work 2
    • Motivation and Objective Accessibility is considered as a programming issue Which are the drawbacks related to this kind of treatment?Accessibility requirements “crosscutting” the same Accessibility requirements software + artefactAccessibility requirementsAccessibility which propitiate the right position of a label element for each textrequirements field element “crosscut” the Web Page more than once 3
    • Motivation and Objective Aspect-Orientation is the right way to treat properly the Accessibility natureAccessibility requirements “crosscutting” the same Accessibility requirements software + artefactAccessibility requirementsAccessibility Clearly, this type of behaviour is the motivationrequirements for AOSD principles 3
    • Motivation and Objective Accessibility is a major concern to the success of a Web applicationREQUIREMENTS CODIFICATION IMPLEMENTATION WEB APPLICATIONS DEVELOPMENT PROCESS Accessibility should not be considered as a programming issuea factor to deal with when the application is already fully developed outside the project’s scope and budget 4
    • Motivation and Objective Accessibility must be considered systematically and from requirementsREQUIREMENTS CODIFICATION IMPLEMENTATION WEB APPLICATIONS DEVELOPMENT PROCESS Accessibility should not be considered as a programming issuea factor to deal with when the application is already fully developed outside the project’s scope and budget 4
    • Motivation and Objective Aiming to bring Accessibility concerns and Web developers closer We introduce our Aspect-Oriented Approach to handle Accessibility concerns using a case study. We outline some Experiences gathered during working onAccessibility and particularly on Accessibility design at early stages. 5
    • Overview of Our Proposal Background Issues Our Approach basically relies on three toolsWeb Content Accessibility Guidelines(WCAG 1.0 // 2.0, 1999-2008) 6
    • Overview of Our Proposal Background Issues Our Approach basically relies on three tools User Interaction Diagram (UID) with Integration PointsUID we have defined two “Integration Points” <1.1> and <1.2> to highlight the Accessibility requirements for the logo’s image and the ID fields respectively 7
    • Overview of Our Proposal Background Issues Our Approach basically relies on three tools Softgoal Interdependency Graph (SIG) Template for AccessibilitySIG we specify “Operationalizing Softgoals” for each Integration Point defined in the User Interaction Diagram (UID) 8
    • Overview of Our Proposal Background Issues User Interaction Diagram (UID)1 with Integration Points Softgoal Interdependency Graph (SIG)2 Template for Accessibility1 UID (Vilain et al., 2000) for modelling User-System Interactions2 SIG (Chung et al., 2000-2004) for modelling Non-Functional Requirements (NFRs) 9
    • Overview of Our Proposal An Aspect-Oriented Approach through a case study FIRST STAGE manages the application’s requirements, looking for those which involve ACCESSIBILITY NEEDS to make access to the essential functionality of the application easier to everyone. SUPPORTING TOOL 10
    • Overview of Our Proposal An Aspect-Oriented Approach through a case study SECOND STAGE applies our CONCEPTUAL TOOLS to develop diagrams which support the ACCESSIBILITY CONCRETE CONCERNS for the requirements identified at the first stage. SUPPORTING TOOL 10
    • Overview of Our Proposal An Aspect-Oriented Approach through a case study THIRD STAGE DISCOVERS CROSSCUTTING CONCERNS and APPLIES ASPECTS to solve these symptoms using the Accessibility SUPPORTING TOOL knowledge from diagrams, which were delivered at the second stage. 10
    • Overview of Our Proposal An Aspect-Oriented Approach through a case study FOURTH STAGE SUPPORTING TOOL concretes a well-formed HTML document taking into account the ACCESSIBILITY CONCERNS from the design at previous stages. 10
    • Overview of Our Proposal An Aspect-Oriented Approach through a case study In order to clarify this briefly introduction ofour proposal, let’s look at part of a case study and some of the ideas behind the tool’s architecture SUPPORTING TOOL SUPPORTING TOOL we provide a tool to support part of the development process 10
    • Overview of Our Proposal An Aspect-Oriented Approach through a case study ROOT ACCESSIBILITY SOFTGOAL User-UID Interaction (U-UI) to propitiate an accessible Login < 1 > HTML University Home Page BRANCHES UID INTEGRATION POINTS and their refinement User-UID Interaction Component (U-UIc) User-UID Interaction Component (U-UIc) process through the tree < 1.1 > HTML Image < 1.2 > HTML Form User Layout support User Technology support User Layout supportCONTRIBUTIONSSATISFYING DEGREE of the LEAVESOPERATIONALIZING OPERATIONALIZING SOFTGOALS SOFTGOALS to Technology Independence Technology Dependence to be Satisfied Accessibility ( WCAG 1.0 checkpoints ) + + + ++ ++ + +- +- +- 1.1 2.1 2.2 10.2 10.4 9.4 9.5 12.3 12.4 UID 11
    • Overview of Our Proposal An Aspect-Oriented Approach through a case study TECHNOLOGY AND LAYOUT ASPECTS are defined to avoid these SYMPTOMS when providing ACCESSIBILITY SUPPORT ASPECTS HTMLTextField HTMLLabel HTMLForm I. TSTEXTFIELD 9.5 accessKeyLabel ( ) 9.4 tabbingControls( ) 10.2 promptPosition( ) 10.4 defaultText( ) II. LSTEXTFIELD 12.4 explicitAssociation( ) 12.3 groupInLogicalUnits( )“scattering”“tangling” 12
    • Overview of Our Proposal An Aspect-Oriented Approach through a case study 13
    • Overview of Our Proposal An Aspect-Oriented Approach through a case study showing a view with information about the SIG DIAGRAM which is built transparently when the developer saves the user’s abstract interface. 13
    • Outline of the Experience Gathered on the Field1. Accessibility is a hot-spot to the future of the WWW. Our approach shows a high degree of commitment by providing specific conceptual techniques to handle the Accessibility concerns as first-class citizens from the beginning in the Web development process.2. The term “concern” from the AOSD paradigm describes properly theAccessibility nature. Our proposal applies Aspect-Orientation to deal with the non-functional, generic and crosscutting features of Accessibility early since requirement elicitation are weaved together using specialized techniques. 14
    • Outline of the Experience Gathered on the Field3. The implications of having strong foundations and a supportingtool for a design approach. The background underlying our approach is based on recognized world-wide Accessibility guidelines and mature works concerned with WE and traditional software designs. Our supporting tool aims to assist developers in the implementation of cases, and in the creation of their corresponding models by using reusable components. 14
    • Outline of the Experience Gathered on the Field “Unified” model-driven approaches Having full documentation and automatic application generation versus Including some bureaucracy into the development processThese issues demand time/cost consuming and learning effort… Project team and development environment should include prior knowledge of WCAG and our proposal should be used to design and documentation as an standard discipline 15
    • Outline of the Experience Gathered on the Field Investing in design particularly in design to propitiate Accessibility returns quality benefits and contribute to managethe volatility and complexity of current Web applicationsthese benefits must be shown to developers to discourage ad-hoc practices 15
    • Conclusions and Future Work( 1 ) There are two major barriers to make real the slogan "A Web for All” The lack of awareness from informatics people and organizations The gap between software developers and Accessibility specialists( 2 ) The contributions of our work Introduces an Aspect-Oriented Approach Shows the advantages of applying AOSD principles to handle Accessibility at early stages Provides some insights from the Designer Perspective( 3 ) Looking at the future Complete the migration to WCAG 2.0 Extend the tool’s functionality to propitiate industry adoption Further validation 16
    • Conclusions and Future Work THANK YOU ADRIANA MARTINadrianaelba.martin@gmail.com 16