w4a11 accessibility at early stages insights from the designer perspective-martin-cechich-rossi
TRANSCRIPT
Adriana Martín, Alejandra Cechich and Gustavo Rossi
Accessibility at Early Stages: Insights from the Designer Perspective
Summary
1. Motivation and Objective
2. Overview of Our Proposal2.1 Background Issues2.2 An Aspect-Oriented Approach through a case study
3. Outline of the Experience Gathered on the Field
4. Conclusions and Future Work
2
Motivation and Objective
3
“crosscutting”the same software artefact
Accessibility requirements
Accessibility requirements
Accessibility requirements
Accessibility is considered as a programming issueWhich are the drawbacks related to this kind of treatment?
which propitiate the right position of a label element for each text field element “crosscut” the Web Page more than once
Accessibility requirements
+
Accessibility requirements
Motivation and Objective
3
“crosscutting”the same software artefact
Accessibility requirements
Accessibility requirements
Accessibility requirements
+
Accessibility requirements
Aspect-Orientation is the right way to treat properly the Accessibility nature
Accessibility requirements
Clearly, this type of behaviour is the motivation for AOSD principles
Motivation and Objective
4
IMPLEMENTATIONCODIFICATIONREQUIREMENTS
Accessibility should not be considered as a programming issue
a factor to deal with when the application is already fully developedoutside the project’s scope and budget
WEB APPLICATIONS DEVELOPMENT PROCESS
Accessibility is a major concern to the success of a Web application
Motivation and Objective
4
IMPLEMENTATIONCODIFICATIONREQUIREMENTS
Accessibility should not be considered as a programming issue
a factor to deal with when the application is already fully developedoutside the project’s scope and budget
Accessibility must be considered systematically and from requirements
WEB APPLICATIONS DEVELOPMENT PROCESS
Motivation and Objective
We introduce our Aspect-Oriented Approach to handle Accessibility concerns using a case study.
We outline some Experiences gathered during working on Accessibility and particularly on Accessibility design at early stages.
5
Aiming to bring Accessibility concerns and Web developers closer
Overview of Our Proposal Background Issues
Web Content Accessibility Guidelines(WCAG 1.0 // 2.0, 1999-2008)
6
Our Approach basically relies on three tools
User Interaction Diagram (UID) with Integration Points
Overview of Our Proposal Background Issues
7
Our Approach basically relies on three tools
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
UID
Softgoal Interdependency Graph (SIG) Template for Accessibility
Overview of Our Proposal Background Issues
8
we specify “Operationalizing Softgoals” for each Integration Point defined in the User Interaction Diagram (UID)
SIG
Our Approach basically relies on three tools
User Interaction Diagram (UID)1 with Integration Points
Softgoal Interdependency Graph (SIG)2 Template for Accessibility
Overview of Our Proposal Background Issues
1 UID (Vilain et al., 2000) for modelling User-System Interactions2 SIG (Chung et al., 2000-2004) for modelling Non-Functional Requirements (NFRs)
9
SUPPORTING TOOL
Overview of Our Proposal An Aspect-Oriented Approach through a case study
10
FIRST STAGEmanages 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
Overview of Our Proposal An Aspect-Oriented Approach through a case study
10
SECOND STAGEapplies our
CONCEPTUAL TOOLSto develop diagrams which
support the ACCESSIBILITYCONCRETE CONCERNS for the requirements identified
at the first stage.
SUPPORTING TOOL
Overview of Our Proposal An Aspect-Oriented Approach through a case study
10
THIRD STAGEDISCOVERS
CROSSCUTTINGCONCERNS
and APPLIES ASPECTS
to solve these symptoms using the Accessibility
knowledge from diagrams, which were delivered at the
second stage.
SUPPORTING TOOL
Overview of Our Proposal An Aspect-Oriented Approach through a case study
10
FOURTH STAGEconcretes a well-formed
HTML document taking into account the ACCESSIBILITYCONCERNS from the design
at previous stages.
SUPPORTING TOOL
Overview of Our Proposal An Aspect-Oriented Approach through a case study
10
In order to clarify this briefly introduction of our proposal, let’s look at part of a case study and
some of the ideas behind the tool’s architecture
SUPPORTING TOOLwe provide a tool to support part of the
development process
Overview of Our Proposal An Aspect-Oriented Approach through a case study
11
User Technology support User Layout support
Technology Dependence Technology Independence
+
12.410.4 9.5
User-UID Interaction (U-UI)< 1 > HTML University Home Page
User-UID Interaction Component (U-UIc) < 1.2 > HTML Form
User-UID Interaction Component (U-UIc)< 1.1 > HTML Image
10.2
User Layout support
9.4
+ + -+ -+ -
+
2.2
++
2.1
++
1.1
+
12.3
ROOTACCESSIBILITY SOFTGOAL
to propitiate an accessible Login
BRANCHESUID INTEGRATION POINTS
and their refinement process through the tree
LEAVESOPERATIONALIZING SOFTGOALS
to be Satisfied ( WCAG 1.0 checkpoints )
CONTRIBUTIONSSATISFYING DEGREE
of the OPERATIONALIZING
SOFTGOALS to Accessibility
UID
Overview of Our Proposal An Aspect-Oriented Approach through a case study
12
HTMLLabel HTMLTextField HTMLFormASPECTS
II. LSTEXTFIELD 12.4 explicitAssociation( ) 12.3 groupInLogicalUnits( )
I. TSTEXTFIELD 9.5 accessKeyLabel ( ) 9.4 tabbingControls( )10.2 promptPosition( ) 10.4 defaultText( )
“scattering”“tangling”
TECHNOLOGY AND LAYOUTASPECTS
are defined to avoid these SYMPTOMS when providing ACCESSIBILITY SUPPORT
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
13
showing a view with information about the SIG DIAGRAM which is built transparently when the developer
saves the user’s abstract interface.
Outline of the Experience Gathered on the Field
1. 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 the Accessibility 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 Field
3. The implications of having strong foundations and a supporting tool 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
Project team and development environmentshould include prior knowledge of WCAG and our proposalshould be used to design and documentation as an standard discipline
15
These issues demand time/cost consuming and learning effort…
“Unified” model-driven approaches Having full documentation and automatic application generation
versusIncluding some bureaucracy into the development process
Outline of the Experience Gathered on the Field
15
returns quality benefits and contribute to manage the volatility and complexity of current Web applications
these benefits must be shown to developers to discourage ad-hoc practices
Investing in designparticularly in design to propitiate Accessibility
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 organizationsThe gap between software developers and Accessibility specialists
( 2 ) The contributions of our work Introduces an Aspect-Oriented ApproachShows the advantages of applying AOSD principles to handle Accessibility at
early stages Provides some insights from the Designer Perspective
( 3 ) Looking at the futureComplete the migration to WCAG 2.0Extend the tool’s functionality to propitiate industry adoption Further validation
16
