[garysieling]

Do you think this is caused by selling directly to institutions, rather than the consumers of the application?

I know there are a few products oriented around specific accessibility features that would be sold directly to the people who need them (e.g. tty devices), but it seems the only progress I've seen in this area in software projects was for §508 compliance.

[gnicholas]

This was a product that is sold largely to institutions, so that could be the issue. Big companies go after big markets, and they tend to view accessibility as niche (and therefore not worth their time). While a particular need might be niche (blindness = .1% of children), when you add up all accessibility needs, it's actually a large chunk of the student population (at least 20%) that gets left out.

I think some edtech companies improperly equate accessibility with special education and write it off as a separate (smaller) market. But the point of accommodations, in many cases, is that many kids can be taught alongside their peers in general ed classes—if they get the right accommodations.

For example, a kid with bad eyesight has an accessibility need (glasses, or if he can't afford them large text). He is not someone who needs to go to a separate special education class. Unfortunately, the lack of accessibility in popular edtech solutions means that kids like this are not able to be served in a gen-ed classroom. This leads to stigmatization and lower achievement.