FodnessMemo08


 * **Catalysts** || **Types / Groups of People** || **Corrosions** ||
 * Need to work with the software || Visually Impaired || Marginalized group ||
 * Need to work with the software || Hearing Impaired || Marginalized group ||
 * Fight on behalf of a marginalized group || Disability Advocates || Are not very prominent as activists, little influence ||
 * Responsible for instructing students on how to create software, including programming for accessibility || IT Educators || Are often not aware of standards for accessibility and/or can't motivate students to care ||
 * Responsible for programming the software to be accessible || Software Designers || Either don't know about programming for accessibility, or don't care, or are instructed not to by bosses ||
 * Responsible for creating software usable by a wide audience, and have the ability to make accessible software unburdensome || Software Companies || Are concerned with the bottom line, and therefore tend to avoid programming for accessibility, or push the burden onto programmers down the line ||
 * Responsible for the well-being of disabled individuals by protecting them from exclusion via legislation and enforcing existing regulations || Government Regulators || Unable to keep up with advances in technology, and not able to exercise significant leverage to amend existing laws or pass new ones ||
 * Responsible for creating internet standards for HTML, CSS, AJAX, etc, which include components for accessibility || W3C || Nobody listens to them ||
 * Advocate adherence to published W3C standards, which makes accessibility automatic or easier to implement || Standards Compliance Advocates || Nobody listens to them ||
 * Capable of writing software that automatically integrates accessibility, such as YouTube being able to use speech recognition to automatically subtitle all videos for the deaf || Innovative Service Providers (e.g. YouTube) || They don't usually design for accessibility, or push off accessibility tasks further down the chain ||