23209 2013-09-11 09:07:25 +0000 fix status section 2013-09-18 10:04:14 +0000 1 1 1 Unclassified HTML WG HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) unspecified PC Windows NT RESOLVED FIXED P3 normal --- 1 faulkner.steve jason faulkner.steve jason mike public-html-admin public-html-bugzilla public-html-wg-issue-tracking robin sideshowbarker+html-a11y-api oldest_to_newest 93233 0 faulkner.steve 2013-09-11 09:07:25 +0000 the status section of the spec needs to be updated to reflect that the doc is jointly published by the html wg and the PF wg overseen by the HTML a11y taskforce. something along the lines of: "This document is developed through the HTML Accessibility Taskforce, with approval by the Protocols and Formats Working Group, and published by the HTML Working Group." 93277 1 jason 2013-09-12 00:23:25 +0000 What's the best way to address this, given that the SoTD section is generated by ReSpec? Do we just replace and hardcode that whole section instead of relying on ReSpec for it? 93288 2 robin 2013-09-12 13:06:07 +0000 (In reply to Jason Kiss from comment #1) > What's the best way to address this, given that the SoTD section is > generated by ReSpec? Do we just replace and hardcode that whole section > instead of relying on ReSpec for it? This is a fairly common situation. First, look at the the special "sotd" section at: http://www.w3.org/respec/ref.html#special-sections Second, the wg* configurations accept arrays: http://www.w3.org/respec/ref.html#wg 93306 3 jason 2013-09-12 19:33:13 +0000 Thanks, Robin. 93392 4 jason 2013-09-15 02:12:21 +0000 Steve, see https://github.com/w3c/html-api-map/commit/050ef558980dea9073dc95a8433d604571b23efe Does this resolve the bug? 93516 5 jason 2013-09-18 10:04:14 +0000 Resolving for now. Will revisit if necessary.