Title:
State: OPEN CLOSED Pending review
Person: Unassigned Sina Bahram Aditya Bajaj Benjamin Beaudry Curt Bellew Zoë Bijl Shari Butler ANDREA CARDONA Dominic Cooney Michael Cooper James Craig Joanmarie Diggs Isaac Durazo Howard Edwards James Edwards Frank Elavsky Mayuri Faldu Steve Faulkner Reinaldo Ferraz Alexander Flenniken Bryan Garaventa Rashmi Garimella Matt Garrish Jaunita George Ariella Gilmore Michael Goddard Glen Gordon Shirisha Gubba Jon Gunderson Markku Hakkinen Sarah Higley Hans Hillen Isabel Holdsworth Stanley Hon Patrick Hung Matthew King Greta Krafsig Peter Krautzberger JaEun Jemma Ku Christopher Lane Charles LaPierre Gez Lemon Aaron Leventhal Laurence Lewis biao liu Brian Liu Xu David MacDonald Sazzad Mahamud Mark McCarthy Erika Miguel Daniel Montalvo Sheila Moussavi James Nurthen Scott O'Hara Adam Page Michael Pennisi Roberto Perez Janina Sajka Trisha Salas Stefan Schnabel Harris Schneiderman Boaz Sender Cynthia Shelly Tzviya Siegman Avneesh Singh Neil Soiffer Francis Storr Melanie Sumner Alexander Surkov James Teh Seth Thompson Jan Williams Benjamin Young Valerie Young Helen Zhou 骅 杨 Matthew King
Due Date: (accepts formats such as "2005-05-17", "+1 week", "14 August 2005" and "next Thursday")
Associated Issue: none ISSUE-1037 ISSUE-1057 ISSUE-1: button types ISSUE-2: rowspan and colspan ISSUE-3: full table support ISSUE-8 ISSUE-9: role extensibility ISSUE-10: autosubmit ISSUE-11: Best Practices ISSUE-12: mixed button state ISSUE-15: Prolog ISSUE-16: Source of change ISSUE-18: Input Tokenizer ISSUE-22: equivalent ISSUE-24: DTD ISSUE-25: separator ISSUE-28: User testing ISSUE-29: media ISSUE-30: property extensions ISSUE-31: undefined value ISSUE-32: readonly ISSUE-33: secret ISSUE-34: Accessible name ISSUE-36: conformance tech ISSUE-44: children presentational ISSUE-45: templateid ISSUE-46: descendants to disable ISSUE-49: datatype data type ISSUE-50: Screen shots of widgets ISSUE-51: Datatype and Formatters ISSUE-54: Inheritance conflicts ISSUE-55: Implicit roles ISSUE-57: application-req ISSUE-62: browser rqts ISSUE-63: Dropeffect Extensibility ISSUE-64: text in application ISSUE-65: WAI ARIA and User Agent Implementation Guide ISSUE-74: channel v. live ISSUE-83: aaronlev ISSUE-84: Remove 2.4 from Spec ISSUE-92: Rich text editing ISSUE-93: data type ISSUE-96: precedence for sort ISSUE-97: required states ISSUE-98: required child roles, parent roles ISSUE-103: aria-invalid values ISSUE-104: form autosubmissions ISSUE-108: Unique Accessibility API ID ISSUE-109: Role menuitemradio nesting ISSUE-116: Presentation uses ISSUE-118: Movable separators ISSUE-119: XBL for ARIA2 ISSUE-161: live region ISSUE-285: CURIE support in ARIA 2.0 ISSUE-331: Sync DOM Attributes ISSUE-334: Precedence of aria-label and aria-labelledby ISSUE-335: breadcrumbs ISSUE-337: column expansion ISSUE-338: xlink:title ISSUE-339: SVG implementation ISSUE-340: ScrollView or Scrollable Region Property ISSUE-341: Navigational landmarks ISSUE-342: Shadow trees ISSUE-343: Script disabled ISSUE-347: audio support ISSUE-349: actionable elements ISSUE-350: xlink ISSUE-351: Unbounded numerical values ISSUE-352: Device independent interaction ISSUE-355: heading algorithm ISSUE-356: custom widgets ISSUE-360: SVG tref ISSUE-361: Additional semantics ISSUE-364: Response to CSS ISSUE-366: Consistent level ISSUE-371: rowgroup types ISSUE-373: multiple roles ISSUE-381: cross-platform keyboard ISSUE-387: placeholder attribute ISSUE-388: clipboard operations ISSUE-389: aria-valuenow in HTML5 ISSUE-398: setsize/posinset on grids/treegrids/trees ISSUE-401: multiple contentinfo ISSUE-405: timeline role ISSUE-406: aria-hint ISSUE-409: New input types ISSUE-411: aria-description (string) ISSUE-425: css generated content ISSUE-431: Effective Keyboard Interface for Application Context ISSUE-434: interactive separators ISSUE-435: role text ISSUE-437 ISSUE-438 ISSUE-441 ISSUE-443: aria-required group ISSUE-445: Control Patterns ISSUE-456: abstract roles and patterns ISSUE-461: AT manipulate DOM ISSUE-463: aria-hidden ISSUE-465: implicit aria-haspopup on combo ISSUE-466: Inconsistencies in role overriding ISSUE-467: chosen role ISSUE-468: figure or interactive image ISSUE-469: Semantic Zoom Role ISSUE-470 ISSUE-476 ISSUE-478: Non-modal dialog keyboard guidance ISSUE-481: aria-live removal events ISSUE-487: List managed states ISSUE-489: Date picker keyboard interaction ISSUE-494: menu is a form control? ISSUE-501: grouping in menus ISSUE-503: inheritance rules ISSUE-505 ISSUE-506 ISSUE-507: expanded on rows ISSUE-509 ISSUE-511: input descendants ISSUE-512: related concepts outdated ISSUE-515: global? ISSUE-518: aria-level on landmarks ISSUE-519 ISSUE-520: readonly applicability ISSUE-521 ISSUE-522 ISSUE-524: sortability ISSUE-525: AT prescriptiveness ISSUE-530 ISSUE-536: aria-hidden="discoverable" ISSUE-537: aria-hidden ISSUE-539 ISSUE-540 ISSUE-541 ISSUE-542: TAC Generated Content ISSUE-555: Media player design pattern ISSUE-560 ISSUE-567: ARIA for CSS generated content ISSUE-568: aria-modal ISSUE-569 ISSUE-573 ISSUE-577 ISSUE-583 ISSUE-587: aria-selected on more elements ISSUE-593 ISSUE-594 ISSUE-603: aria-triggers? aria-initiates? ISSUE-609: empty string labels are technically valid ISSUE-610: ComboboxEnhancements ISSUE-611: pivotTables ISSUE-612: For treeitem, compute implicit aria-level based on aria-owns chain ISSUE-618: Selection event for MSAA mappings for single selection case ISSUE-619: whitelist aria-label in host lang conflict ISSUE-622: DOMStringMap Element.ariaset ISSUE-624: defaultButton ISSUE-626: clarifying text alt recursion ISSUE-627: ARIA and native semantics conflict. ISSUE-630 ISSUE-631: keyboard help ISSUE-634: video/audio roles ISSUE-635: UAIG rowgroup AAPI mappings. ISSUE-639 ISSUE-641: section (abstract) allows nameFrom content ISSUE-642: TAC root node of calc ISSUE-645 ISSUE-647 ISSUE-648 ISSUE-651: aria-invalid ISSUE-653: selector() ISSUE-654: Label and description change events ISSUE-655: annotation roles ISSUE-656: AT MUSTs ISSUE-659: Update AXAPI tests for aria-busy ISSUE-660: Implicit region label from heading ISSUE-661: UAIG1.1 mapping of presentation on table and list elements ISSUE-663 ISSUE-664 ISSUE-665 ISSUE-666 ISSUE-667: page title ISSUE-668 ISSUE-670 ISSUE-672 ISSUE-673: data table algorithm ISSUE-674 ISSUE-676: Degree of details in mappings ISSUE-677: ATK/AT-SPI mapping of role="presentation" ISSUE-678: Proper mapping of ARIA group role ISSUE-682: Clarify override of native host role with respect to roles of its required owned children ISSUE-685 ISSUE-686 ISSUE-687 ISSUE-690: UA reqs for describedat ISSUE-695: aria-spec-nits ISSUE-696 ISSUE-697 ISSUE-701 ISSUE-702: The word SHOULD for keyboard support is unclear in the Roles Model spec ISSUE-705: Harmonize mappings across MSAA, UIA, IA2 (and other platfroms?) ISSUE-706: AAPI managed states ISSUE-707 ISSUE-708: Section 5.1.2: Condition on including elements in the accessibility tree is ambiguous ISSUE-710: ARIA 1.1 automated testing ISSUE-714: Mappings for aria-roledescription ISSUE-717 ISSUE-718 ISSUE-719 ISSUE-720 ISSUE-721 ISSUE-722 ISSUE-723 ISSUE-730 ISSUE-735 ISSUE-737 ISSUE-738 ISSUE-739 ISSUE-742 ISSUE-743 ISSUE-744 ISSUE-745 ISSUE-746 ISSUE-747 ISSUE-748 ISSUE-749 ISSUE-750 ISSUE-751: tooltip ISSUE-752 ISSUE-753 ISSUE-754 ISSUE-1001 ISSUE-1002 ISSUE-1003 ISSUE-1004 ISSUE-1005 ISSUE-1006: children presentational = true not consistent ISSUE-1007 ISSUE-1008 ISSUE-1009 ISSUE-1010 ISSUE-1011: Role text overrides. ISSUE-1012 ISSUE-1013: Event for aria-errormessage ISSUE-1014 ISSUE-1015: uia-express ISSUE-1016 ISSUE-1017 ISSUE-1018 ISSUE-1019: accname 2E ISSUE-1020: accname 2F ISSUE-1021 ISSUE-1022 ISSUE-1023 ISSUE-1024 ISSUE-1025: Mappings for aria-haspopup ISSUE-1026: Drive mapping of aria-errormessage for AAPIs ISSUE-1027 ISSUE-1028: SeparatorNotWidget ISSUE-1029: Interactive vs. static separators ISSUE-1030: Role password mappings ISSUE-1031: Webdriver automated accessibility testing ISSUE-1032 ISSUE-1033 ISSUE-1034: Composite spinbutton ISSUE-1035: Complex lists and tree widgets ISSUE-1036 ISSUE-1038: Role "feed" mappings ISSUE-1039: Role "figure" mappings ISSUE-1040: Role "term" mappings ISSUE-1041: Properties colcount, colindex, colspan, rowcount, rowindex, and rowspan ISSUE-1042: Property aria-details ISSUE-1043 ISSUE-1044 ISSUE-1045 ISSUE-1046: HTML Role Parity ISSUE-1047: aria-roledescription restrictions ISSUE-1048: roledescription role limits ISSUE-1049: react to arrow keys ISSUE-1050 ISSUE-1051: aria-placeholder mappings for IA2 ISSUE-1052 ISSUE-1053 ISSUE-1054 ISSUE-1055 ISSUE-1056
Or Associated Product: none AccNam AAM 1.2 ARIA 1.0 ARIA 1.0 Authoring Practices ARIA 1.0 Implementation Guide ARIA 1.0 Primer ARIA 1.0 Test Plan ARIA 1.1 ARIA 1.1 Authoring Practices ARIA 1.1 Core Mapping Specification ARIA 1.1 Name Computation ARIA 1.1 Test Plan ARIA 1.2 ARIA 1.2 Core AAM specification ARIA 2.0 ARIA 2.0 Authoring Practices ARIA 2.0 Core AAM ARIA 2.0 Name Calculation ARIA HTML 5 Implementation Guide CSS AAM Digital Publishing AAM Digital Publishing Roles Module Miscellaneous SVG AAM Accessibility Mapping spec. WCAG 2 Techniques for ARIA
Add notes (no markup allowed, URIs get automatically hyperlinked):
Reassigned to Matt from JamesN in 19 Nov 2015 meeting
Proposal in mck-action1490 branch: http://rawgit.com/w3c/aria/mck-action1490/aria/aria.html Objectives: 1. Allow combobox to popup grid, tree, and dialog in addition to listbox. 2. Allow aria-controls so screen reader users can see a rendering of the popup in reading mode. 3. Remove ambiguities from the spec to improve understanding and simplify authoring. 4. Do it all without breaking any existing implementations. Note: browser and assistive technology impact is extremely small. The authoring changes proposed are already largely supported by both browsers and assistive technologies. The 3 minor exceptions are: 1. Screen readers will need to recognize the aria-controls relationship when focus is inside the popup in order to properly handle escape key processing. 2. Screen readers will need to recognize boolean values for aria-autocomplete in addition to the ARIA 1.0 token values. 3. When authors provide a boolean value for aria-autocomplete, browsers will need to allow the boolean values. The ARIA 1.0 tokens would also still be allowed. The changes in the mck-action1490 branch are: 1. Reword the combobox definition. 2. Added normative statement saying the popup must be one of listbox, tree, grid, or dialog. 3. Specify authors SHOULD use aria-controls but MAY use aria-owns to specify the relationship between the input and the popup. 4. Added normative author MUST for correct use of aria-expanded. 5. Reword and simplify the focus management language. 6. Remove all text about aria-autocomplete except an author SHOULD statement referring to the new boolean definition of aria-autocomplete. 7. Update the example code to match the new authoring requirements. 8. Add a reference to the APG. 9. Change the superclass to input. 10. Remove the required owned elements.
Based on today's lively discussion, I have revised my proposal for action 1490[1], which is in branch mck-action1490[2]. mck-action1490 branch: http://rawgit.com/w3c/aria/mck-action1490/aria/aria.html The revisions from today's discussion include: 1. Remove implicit value of aria-orientation for combobox. 2. Remove combobox note about XForms. 3. Change combobox aria-autocomplete authoring requirements to state that aria-autocomplete be set to either "both" if autocomplete is provided in the textbox or "list" if it is not. 4. Restored token values for aria-autocomplete and clarified their definitions. As previously described, the objectives of action 1490 are: 1. Allow combobox to popup grid, tree, and dialog in addition to listbox. 2. Allow aria-controls instead of aria-owns so the pop-up is not a child of the single line text input. This enables screen readers to include a rendering of the pop-up outside of the text input in their reading view or buffer. 3. Remove ambiguities from the spec to improve understanding and simplify authoring. 4. Do it all without breaking any existing implementations. Note: the changes included in action 1490 have little or no effect on browser implementations and require only minor adjustments in the logic of some screen readers to support the aria-controls relationship when processing the escape key. Now, the changes in the mck-action1490 branch are: 1. Reworded the combobox definition. 2. Added normative statement saying the popup must be one of listbox, tree, grid, or dialog. 3. Added normative MUST statement requiring authors to associate the input with the pop-up. 4. Specified that authors SHOULD use aria-controls but MAY use aria-owns to specify the relationship between the input and the popup. 5. Added normative author MUST statement requiring correct use of aria-expanded. 6. Reworded and simplify the focus management language. 7. Eliminated confusing language about aria-autocomplete and specified that authors SHOULD use either "both" if the text input provides suggestions or "list" if it does not. 8. Updated the example code to match the new authoring requirements. 9. Added a reference to the APG. 10. Changed the superclass to input. 11. Remove the required owned elements. 12. Clarified the value definitions for aria-autocomplete.
See this ARIA list post for another combobox coding pattern proposal: https://lists.w3.org/Archives/Public/public-aria/2016Feb/0294.html
Modified the definition of aria-activedescendant for special case comboboxes. Added the following paragraph: " A special use case is a combobox where its textbox has DOM focus, and that textbox employs an aria-activedescendant attribute to reference the currently active listbox option. The referenced listbox option is not in fact a descendant of the textbox itself, but of its parent combobox element. Even so, the aria-activedescendant property is treated by user agents as the active descendant of the combobox, and not the textbox. " In situ: http://rawgit.com/w3c/aria/mck-action1490-activedescendant/aria/aria.html#aria-activedescendant
------ Changes made as a result of March 10, 2016 meeting Note: The revised combobox proposal is now in branch action1490-combobox: http://rawgit.com/w3c/aria/action1490-combobox/aria/aria.html#combobox The branch includes the following changes as a result of the Mar 10 discussion. 1. Revised definition so that it does not imply that listbox and grid are classified as popups as opposed to elements that popup. 2. elivated the following normative aria-autocomplete statement from author SHOULD to author MUST: If the combobox provides autocompletion behavior for the text input as described in aria-autocomplete, authors MUST set aria-autocomplete on the textbox element to the value that corresponds to the provided behavior. 3. Added an author MUST statement that restricts the role of the popup element to listbox, tree, grid, or dialog. And, correspondingly added listbox, tree, grid, and dialog as required owned elements.
Please respond to Bryan's post: https://lists.w3.org/Archives/Public/public-aria/2016Mar/0200.html
Changes merged into master: https://github.com/w3c/aria/commit/a0a9166791 https://rawgit.com/w3c/aria/master/aria/aria.html#combobox Closing this action.