10447 2010-08-26 10:13:00 +0000 <output> should not have a status role by default after all 2010-12-15 14:37:09 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED FIXED a11y, aria P1 major --- 10066 1 mjs faulkner.steve faulkner.steve ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37916 0 mjs 2010-08-26 10:13:00 +0000 <output> should have no role by default instead of the "status" role. Although this is not clearly stated in the ARIA spec, the "status" role is intended to be used for status bars, and maps to a "status bar" type role in platform accessibility APIs. I reported this issue an ARIA to PFWG: http://lists.w3.org/Archives/Public/public-pfwg-comments/2010JulSep/0024.html 37957 1 ian 2010-08-26 19:32:18 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Assumed reporter was correct. 37958 2 contributor 2010-08-26 19:33:02 +0000 Checked in as WHATWG revision r5365. Check-in comment: apparently role=status means something else http://html5.org/tools/web-apps-tracker?from=5364&to=5365 38105 3 faulkner.steve 2010-08-28 12:18:51 +0000 After further discussion, it has been concluded that while current implementations of aria status map to the status bar role in most accessibility APIs , the aria status role itself has a broader definition so could well be a default role for <output> 38139 4 mjs 2010-08-29 01:07:53 +0000 Updating title to reflect the new conclusions. Sorry for jumping the gun on this bug originally. 38497 5 ian 2010-09-07 08:18:18 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Same as before. 38498 6 contributor 2010-09-07 08:21:17 +0000 Checked in as WHATWG revision r5418. Check-in comment: revert earlier change here based on updated information http://html5.org/tools/web-apps-tracker?from=5417&to=5418 43379 7 cooper 2010-12-15 14:37:09 +0000 Big triage sub-team thinks the ARIA mapping team should review and update this bug as the mappings are prepared, but no need for entire HTML A11Y TF to review. Assigning to Steve Faulkner to track.