A final clarification: On Fri, Jul 27, 2018 at 4:36 PM, Tantek Çelik <tan...@cs.stanford.edu> wrote:
> Even if we (Mozilla) are delayed with implementation, we can > still champion this stuff. We can still nominate someone to > participate in the WG with subject matter expertise to help guide what > we think will be more implementable features. > 1. Superficially (I haven't dug into it in detail), I don't believe anything proposed in ARIA 1.1 or 1.2 is likely to be "not implementable" or even "costly to implement" for browser vendors. It's more that the Mozilla accessibility team currently doesn't have anyone who can devote time to working on new spec things. To put it melodramatically, with current resourcing, it's likely to take us months to even get to reading the spec or implement the simplest of spec additions. I really hope this does not remain the case for too long, but that's how it is right now. 2. For the same reason, we also don't have anyone with subject matter expertise that's able (due to tie constraints) to participate meaningfully in the WG. Jamie _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
