WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: What to tell developers about accessibility?

for

From: Elle
Date: Apr 17, 2012 2:37PM

All of these suggestions are excellent, and mine are not new to the list.
The ones that I use when making the case with development teams about what
accessible code does for a project are:


1. Standards = Valid code streamlines development costs, reduces
cross-browser issues, optimizes for device independence, future proofs code

2. .NET = If .NET guys, I'd talk about MVC (ASP.NET MVC4, for example)
and how it integrates with existing frameworks, creating a clean separation
between presentation and behavior

3. Keyboard access = A fundamental way to improve accessibility for a
site. This might be helpful to tie to mobile user experiences, too.

4. Semantic Markup = Accessibility can be woven into much of this
discussion, especially if you include role, state, behavior of elements.

5. Empathy Awareness = I am using a disabled veteran friend in my next
talk (perhaps pre-recorded) to demonstrate the need for keyboard access
with a real life example.


Cheers,
Elle