Hacker News new | past | comments | ask | show | jobs | submit login

So did you fully read the lengthy Medium TOS when reading the article?

Because it sounds like this accessibility document is also a fairly similar piece of boilerplate.




If I was reading Medium as part of my employment then yes, I would have read the ToS.

If you're saying that Berkeley was paying lip-service to accessibility by having boiler-plate that faculty didn't really need to comply with, well, that makes the situation worse, not better.

"We tried but we didn't account for human factors so we failed" is much better than "we didn't really try, we just pretended, because we wanted to give a good impression without actually making any changes".


Fair enough, I do read every license for any code I use at work.

However, I would certainly think that "we wanted to give a good impression without actually making any changes" is probably closer to the truth. I doubt Berkeley as an institution really cares about accessibility; it sounded like a good thing and policies were enacted without a lot of thought given to the ramifications. If multiple professors signed off that their courses were accessible, then it certainly strikes me that this was a low priority that was largely ignored.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: