Web, as stated by the World Wide Web Consortium
(W3C). The “Web for All” design principle
stipulates: “The social value of the Web is that it
enables human communication, commerce, and
opportunities to share knowledge. One of W3C's
primary goals is to make these benefits available to
all people, whatever their hardware, software,
network infrastructure, native language, culture,
geographical location, or physical or mental ability”
(W3C, 2012a). W3C pursues this goal via the Web
Accessibility Initiative (WAI), that develops the
Web Content Accessibility Guidelines (WCAG)
(W3C, 2012b).
The “legal argument” (Rosmaita, 2006; Wang,
2012) invokes legal requirements for Internet
accessibility; for example, in the United States these
derive from the Section 508 of the Rehabilitation
Act. Rising numbers of impaired students bring to
the forefront the issue of legally mandated equal
access in education (Cohen et al., 2005). In countries
where such legal requirements exist, skills for
accessibility design contribute to employability and
can thus be shown to be useful for students’ future
careers (Ludi, 2002; Cohen et al., 2005).
The market argument stresses the fact that
impaired users represent a significant proportion of
citizens and customers, which are lost through
inaccessible design (Ludi, 2002); this argument also
capitalizes on utility, this time from a business
perspective, complementing the increased
employability.
The “march of technology” argument (Rosmaita,
2006) points to the fact that accessibility does not
refer to impaired users only, but also to all users in
restricted contexts that become increasingly
common as technology permeates more areas of life:
“Automobile drivers—who otherwise have normal
vision—are blind with respect to the web while they
are driving. Likewise, a person surfing the web on a
small mobile handheld device is, for all intents and
purposes, a low-vision person accessing the web”
(ibid., p. 271).
The argument of direct benefits for all users adds
that we-as-able-users are likely to become closely
involved with impaired users, as we, our parents,
and significant others age (Ludi, 2002): “Visually
impaired computer users are a minority, but it’s a
growing minority, and it is growing faster as baby
boomers near retirement age. Further, it’s a minority
that will eventually include us all” (Rosmaita, 2006,
p. 274). This argument lends further support to the
market-related considerations.
The “technical reason” (Wang, 2012) indicates
that designing for accessibility increases
interoperability and standard compliance (also
pointed out by Rosmaita, 2006), thus serving the
general public and increasing designers’ skills and
employability (Waller, Hanson, & Sloan, 2009).
Overall, these arguments capitalize on
accessibility as a matter of a) morality – addressing
disabled people’s needs and rights, b) abiding the
law – and c) a matter of interest – for developer
employees, for businesses, and for the government.
In a nutshell, “the audience is growing, the law
requires it, and the industry trend is toward it”
(Harrison, 2005, p. 23).
Authors also address potential counter-
arguments. The issue of cost appears as the most
prominent expected hurdle: “I think that all would
agree that when faced with an inaccessible website
and an accessible website with the same
functionality, the accessible website is better. The
debate is really over who pays to implement
accessibility, and why they should have to bear that
cost” (Rosmaita, 2006, p. 274). How do authors
address the issue of cost? There are two main
answers. On the one hand, accessibility is deemed
“lightweight to introduce” (Cohen et al., 2005) – that
is, costs are not high, when introduced skillfully and
early. On the other hand, retrofitting accessibility is
significantly more costly, therefore it is better to
design directly for accessibility (Cohen et al., 2005;
Rosmaita, 2006).
Another expected counter-argument, introduced
by Waller et al. (2009), is that designing for
accessibility might “stifle” creativity (rather than
“spark” it), and it might lead into tradeoffs with
other important considerations such as “design
goals, technological limitations, customer objectives
and software objectives” (p. 157). There are no
explicit answers advanced for this concern.
Both types of counter-arguments raise the
following question: how can students approach
accessibility so that they would continue to engage it
outside of the classroom, when facing such counter-
arguments from team members or leaders (or even
from within themselves)? Each project has to
navigate a plethora of competing requirements and
considerations: how can accessibility stand a chance
against issues of beautiful design, or the use of
innovative-but-inaccessible technologies to entice
large numbers of mostly-able users? Since, for any
argument, there is a counter-argument, providing
students a set of good justifications for accessible
design seems to be necessary, but not sufficient for
successful confrontations ‘in the field’.
CSEDU2014-6thInternationalConferenceonComputerSupportedEducation
22