- From: Joanmarie Diggs <jdiggs@igalia.com>
- Date: Tue, 28 Nov 2017 11:17:17 -0500
- To: ARIA Working Group <public-aria@w3.org>
Hey all. We've gotten three responses on this so far (all +1s). And I'm itching to pull the trigger. :) Michael doesn't think this change requires a CfC, but hearing from a few more Working Group members would be helpful if for no other reason than it being confirmation that it's been seen and won't be a surprise. Thanks! --joanie -------- Forwarded Message -------- Subject: Proposal: Remove the mapping table from AccName "AAM" Resent-Date: Thu, 16 Nov 2017 20:17:28 +0000 Resent-From: public-aria@w3.org Date: Thu, 16 Nov 2017 15:16:50 -0500 From: Joanmarie Diggs <jdiggs@igalia.com> To: ARIA Working Group <public-aria@w3.org> Hey all. As was discussed during today's call, I would like to remove the mapping table from AccName "AAM" because: 1. That information is largely already in Core AAM. I see no good reason to have duplicate information. 2. It would simplify testing of AccName (which hasn't yet entered CR), both in terms of tests we'd need to write and get results for and in terms of exit criteria. If you all agree, then I'd also want to tweak the name of the spec so that it no longer contains the "AAM" since the "M" stands for "Mappings" and those would have been removed. Since we need to write tests, get results, and define exit criteria essentially now, having your thoughts on this matter soonish would be great. Thanks in advance! --joanie
Received on Tuesday, 28 November 2017 16:17:57 UTC