W4a11 accessibility at early stages insights from the designer perspective-martin-cechich-rossi
1. Accessibility at Early Stages: Insights
from the Designer Perspective
Adriana Martín, Alejandra Cechich and Gustavo Rossi
2. Summary
1. Motivation and Objective
2. Overview of Our Proposal
2.1 Background Issues
2.2 An Aspect-Oriented Approach through a case study
3. Outline of the Experience Gathered on the Field
4. Conclusions and Future Work
2
3. 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
+ artefact
Accessibility requirements
Accessibility which propitiate the right position of a label element for each text
requirements
field element “crosscut” the Web Page more than once
3
4. Motivation and Objective
Aspect-Orientation is the right way
to treat properly the Accessibility nature
Accessibility requirements
“crosscutting”
the same
Accessibility requirements
software
+ artefact
Accessibility requirements
Accessibility Clearly, this type of behaviour is the motivation
requirements
for AOSD principles
3
5. Motivation and Objective
Accessibility is a major concern to the
success of a Web application
REQUIREMENTS CODIFICATION IMPLEMENTATION
WEB APPLICATIONS DEVELOPMENT PROCESS
Accessibility should not be considered
as a programming issue
a factor to deal with when the application is already fully developed
outside the project’s scope and budget 4
6. Motivation and Objective
Accessibility must be considered
systematically and from requirements
REQUIREMENTS CODIFICATION IMPLEMENTATION
WEB APPLICATIONS DEVELOPMENT PROCESS
Accessibility should not be considered
as a programming issue
a factor to deal with when the application is already fully developed
outside the project’s scope and budget 4
7. 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 on
Accessibility and particularly on Accessibility design at early stages.
5
8. Overview of Our Proposal Background Issues
Our Approach basically relies on three tools
Web Content Accessibility Guidelines
(WCAG 1.0 // 2.0, 1999-2008)
6
9. Overview of Our Proposal Background Issues
Our Approach basically relies on three tools
User Interaction Diagram (UID) with Integration Points
UID
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
10. Overview of Our Proposal Background Issues
Our Approach basically relies on three tools
Softgoal Interdependency Graph (SIG) Template for Accessibility
SIG
we specify “Operationalizing Softgoals” for each Integration Point defined
in the User Interaction Diagram (UID)
8
11. Overview of Our Proposal Background Issues
User Interaction Diagram (UID)1 with Integration Points
Softgoal Interdependency Graph (SIG)2 Template for Accessibility
1 UID (Vilain et al., 2000) for modelling User-System Interactions
2 SIG (Chung et al., 2000-2004) for modelling Non-Functional Requirements (NFRs)
9
12. 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
13. 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
14. 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
15. 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
16. Overview of Our Proposal An Aspect-Oriented Approach through a case study
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 TOOL
SUPPORTING TOOL
we provide a tool to
support part of the
development process
10
17. 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 support
CONTRIBUTIONS
SATISFYING DEGREE
of the LEAVES
OPERATIONALIZING 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
18. 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
19. Overview of Our Proposal An Aspect-Oriented Approach through a case study
13
20. 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
21. 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
22. 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
23. 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 process
These 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
24. Outline of the Experience Gathered on the Field
Investing in design
particularly in design to propitiate Accessibility
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
15
25. 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
