ARIA 2.0 Issue Triage

This is a triage of ARIA 2 Issues, initially as of 22 September 2016 and possibly updated. Note issues that survive the triage will likely be moved to GitHub.

This first pass simply groups the open issues for easier processing.

• Provide new capabilities for the ARIA technology
  • Handle multiple role values (ISSUE-373)
  • Allow properties to be accessed as DOM properties (ISSUE-438, ISSUE-622)
  • Support selectors (ISSUE-653)
  • Get computed role or name (ISSUE-689)
  • Role extensibility (ISSUE-9)
  • State and property extensibility (ISSUE-30, ISSUE-356)
  • assign ARIA semantics and event handlers (ISSUE-119)
  • support CURIE (ISSUE-285)
  • handle disabled script situation (ISSUE-343)
  • control patterns (ISSUE-445)
  • forward compatibility (ISSUE-456)
• Work better with host languages
  • host language default mappings (ISSUE-55) (being addressed by AAMs?)
  • sync similar attributes from host language and ARIA (ISSUE-331)
  • tell author what is host language role (ISSUE-467)
  • Explicitly harmonize with HTML
    • aria-hidden (ISSUE-537)
    • full xlink behavior in link role (ISSUE-350)
    • input types (ISSUE-409)
  • SVG
    • provide SVG implementation guide (ISSUE-339) (now under way)
    • navigational landmark labeling (ISSUE-341)
    • shadow trees (ISSUE-342)
• Enable assistive technologies
  • Allow AT to modify DOM (ISSUE-461)
  • Semantic zoom (ISSUE-469)
  • Refine AT requirement (ISSUE-525)
  • Provide error handling guidance (ISSUE-1032)
  • create AT conformance requirements (ISSUE-656)
  • more accurate pronunciation (ISSUE-1045)
  • Address AAPI mapping inconsistencies
    • aria-activedescendant (ISSUE-560)
    • implicit aria-level in treeitem (ISSUE-612)
• Add or modify features (complex requests)
  • Support user input
    • Datatypes and formatters (ISSUE-51)
    • Input hints (ISSUE-406)
    • Allow standard keyboard interfaces (ISSUE-431)
    • button types (ISSUE-1)
    • Default button (ISSUE-624)
    • Keyboard help (ISSUE-631)
    • rich text editing (ISSUE-92)
    • communicate form autosubmit to user (ISSUE-104)
    • keyboard support across platforms (ISSUE-381)
    • Automatic key events on elements with click handlers (ISSUE-639)
    • actionable elements (ISSUE-349)
  • Improve sorting
    • Column sort indication (ISSUE-569)
    • multi-sort (ISSUE-96)
    • indicate sortability (ISSUE-524)
  • Audio and video
    • Triggers for audio, video (ISSUE-603)
    • Video and audio roles (ISSUE-634 and ISSUE-347)
  • table / grid enhancements
    • remove aria-level from grid (ISSUE-519)
    • expandable columns, not just rows (ISSUE-337)
    • thead, tfoot, tbody (ISSUE-371)
    • pivottable (ISSUE-611)
  • ranges
    • child content for sliders, separators, scrollbars (ISSUE-593)
    • unbounded ranges (ISSUE-351, ISSUE-718)
    • define value step (ISSUE-539 and ISSUE-1027)
  • Text alternatives
    • More fully support extended descriptions (still needed?) (ISSUE-411)
    • text alternative computation in HTML 5 (ISSUE-437) (being addressed by accname-aam and html-aam?)
    • text alternatives for SVG (ISSUE-360)
  • Support content editing
    • caret role (ISSUE-470)
• Other new features
  • Image groups (ISSUE-468)
  • Annotations (ISSUE-655)
  • resource definitions for localized state information (ISSUE-685)
  • Address device independent interaction (ISSUE-352)
  • link destination context (ISSUE-742)
  • media types (ISSUE-29)
  • identify movable objects, like split pane separator (ISSUE-118, ISSUE-434, ISSUE-1036)
  • breadcrumbs role (ISSUE-335)
  • scrollable regions (ISSUE-340)
  • text style roles (ISSUE-361)
  • timeline role (ISSUE-405)
  • css name computation (ISSUE-425)
  • allow hidden but discoverable content (ISSUE-536)
  • ARIA for generated content (ISSUE-567)
  • implicit labels from region headings (ISSUE-660)
  • page title (ISSUE-667)
  • remote annotation (ISSUE-670)
  • password role with information about masking (ISSUE-1022)
  • interactive lists and trees with complex items (ISSUE-1035)
• Clarify things from earlier versions
  • Define how to handle hidden content (ISSUE-463)
  • Clarify whether some roles should override native semantics (ISSUE-466)
  • Menu a form control? (ISSUE-494)
  • What things should inherit to owned roles (ISSUE-503)
  • aria-expanded on row (ISSUE-507)
  • relatedconcepts (ISSUE-512, ISSUE-509)
  • what should be a global property (ISSUE-515)
  • address conflicting inheritance through taxonomy (ISSUE-54) (still an issue?)
  • xlink:title in name computation (ISSUE-338) (for accname-aam now, not spec?)
• Refine or correct things from earlier versions
  • When aria-live removal events happen (ISSUE-481)
  • Group menus (ISSUE-501)
  • Taxonomy of input role (ISSUE-511)
  • aria-level on landmarks (ISSUE-518)
  • what can be readonly (ISSUE-520)
  • harmonize required owned elements between similar roles (ISSUE-530)
  • namefrom on section (ISSUE-641)
  • Keyboard support for interactive widgets (ISSUE-702)
  • harmonize text and presentation roles (ISSUE-1011) (OBE wrt text role?)
  • additional values for aria-invalid (ISSUE-103)
  • refine live regions (ISSUE-161, ISSUE-16)
  • aria-level on leaf vs containers (ISSUE-366)
  • support multiple contentinfo (ISSUE-401)
  • aria-required on group (ISSUE-443)
  • aria-haspopup=true by default on combobox (ISSUE-465)
  • accessible name required for progressbar (ISSUE-506)
  • new values for aria-relevant (ISSUE-521)
  • autocomplete comboboxes (ISSUE-577)
  • deprecate presentation (ISSUE-720)
  • new values for aria-level (ISSUE-721)
  • state and property description (ISSUE-743)
  • make spinbutton composite (ISSUE-1034)
  • drag and drop (ISSUE-719, ISSUE-388)
• Use ARIA more effectively in specs (ISSUE-668)