Presenters: Colin Clark, Antranig Basman, Philip Tchernavskij
The session will engage you in a conversation about what sort of accessibility attributes we can document in this early design phase. We will work with sample wireframes and develop a common language to use to pass along to developers so that accessibility remains at the forefront of design and implementation.
more than 80% of the cost of software development is devoted to maintenance
mainly due to the need to evolve in the face of changing requirements
Change is hard for designers
change has been treated as something that needs to avoid, minimize, control, or managed
Requirements management methods that focus on getting things right from the start see change as risk
In agile development teams have autonomy to respond to change. However it's inward looking and a choice that can only be wielded by expert designers and developers. It doesn't extend beyond the circle of trust.
Change is intolerable for users
for users software tends to be "take it or leave it"
designers/developers of the software have the power to change it without notice
Ownership of software
users don't own it, they just pay to access it
real ownership should give them power to change
The failure of models
people are continually changing, models don't take this into account
a persona at best is a blur, at worst its a stereotype