Fresh off the virtual press, I've written a piece for Knowbility, a nonprofit in Austin, Texas and frequent webinar event partner with TechSoup. It's called Why Accessibility?, and it's for nonprofits, NGOs, charities, government agencies and others that are trying to make the case for accessible web design at their own agencies, or who are trying to understand accessibility issues themselves. This isn't about HOW to make a site accessible, but WHY.
This is from the nonprofit section of the OpenAIR web site. This is an annual event by Knowbility and you can read more about OpenAIR here.
Also, FYI, on Twitter, #a11y is used by many organizations to tag news, resources and discussions about accessible web design. It's a tag worth following.
-=-=-=-=-=- Jayne Cravens Author, The LAST Virtual Volunteering Guidebook
And on a related note is this article which answers this question: does accessible design slow down the web development process?
"If you integrate accessibility into the development process, it becomes a coding routine. Development time won’t increase so much if developers in your team already know what to do."
Close this window