- From: Paul Cotton <Paul.Cotton@microsoft.com>
- Date: Mon, 4 Aug 2014 11:42:51 +0000
- To: "jason@accessibleculture.org" <jason@accessibleculture.org>, "Michael Cooper" <cooper@w3.org>
- CC: PFWG <w3c-wai-pf@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
> Some of the bugs under that component will still apply to the HTML-AAM, while those bugs that were specific to the old HTML-API-MAP document can presumably be closed? Why would the unresolved bugs on the old HTML-API-MAP document just be closed? If the material they are pertinent has been removed or has been moved to the Core API mapping document then surely the bugs should somehow be transferred to the Core API mapping document. > What about renaming the current "HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly)" to "HTML Accessibility API Mappings"? I recommend that we create a new component and leave the old component as is. /paulc Paul Cotton, Microsoft Canada 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 Tel: (425) 705-9596 Fax: (425) 936-7329 -----Original Message----- From: jason@accessibleculture.org [mailto:jason@accessibleculture.org] Sent: Sunday, August 03, 2014 6:48 PM To: Michael Cooper Cc: PFWG; HTML Accessibility Task Force Subject: bug component for HTML-AAM? Should there be a bug component under the "HTML WG" product in bugzilla for the HTML-AAM? What about renaming the current "HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly)" to "HTML Accessibility API Mappings"? Some of the bugs under that component will still apply to the HTML-AAM, while those bugs that were specific to the old HTML-API-MAP document can presumably be closed? Jason Kiss
Received on Monday, 4 August 2014 11:43:33 UTC