A quote not mentioned in this article that really worries me:

The second thing is we need to throw out our rule book and just talk about when doing that is appropriate. We, for often very good reasons, do things like say WordPress is WCAG compliant and no new code should come in that is not. That’s a tradeoff, and that’s a tradeoff that we’ve enshrined. We should readdress it if we think that that tradeoff, whether for a particular feature, a particular user experience, or a particular benefit, is worth it.

(The transcript is misspelled "WCAT".) The suggestion that this should be ignored is really scary. I'd really like to hear Matt provide some examples of WCAG standards he things could be ignored without locking real people out from new features.

A lot of people fought really hard to get WCAG 2.0 Level AA adopted as a standard, and I think following those guidelines is quite reasonable.