Should the APG include a wizard design pattern? #92
Labels
question
Issue asking a question
Comments
mcking65
added a commit
that referenced
this issue
Aug 14, 2016
In addition to the below, This commit also moves the landmark section after the example section. Moved each of the following sections from aria-practices.html to aria-practices-DeletedSectionsArchive.html and created associated issues for drafting new versions. 1. Section "General Steps for Building an Accessible Widget with WAI-ARIA" and created issue #73. 2. Section "Other Widget Authoring Practices"., primarily about aria-valuenow, there is no specific need to raise an issue for this section. 3. Section "Relationships" and raised issues #74, #75, #76, and #77. 4. Section "Managing Dynamic Changes" and created issue #78. 5. Section "Presentation Role" and created issue #79. 6. Section "Form Properties" and created issue #80. 7. Section "Drag-and-Drop Support" and created issue #81 8. Section "Math" and created issue #82. 9. Section "Reusable Component Libraries" and created issue #83. 10. The following 4 Appendix sections related to background on ARIA and created issue #84 A. Background on WAI-ARIA B. Filling the Gaps for Content Delivered to Desktop Browsers c. Building Accessible Applications with WAI-ARIA D. Reasons for Adopting WAI-ARIA 11. The following design patterns: A. Accordion and updated issue #53. B. Autocomplete and updated issue #31. C. Combobox and updated issue #31. D. Datepicker and updated issue #57 E. Dialog (Non-Modal) and updated issue 59. F. Dialog (Tooltip) and added issue #85. G. Landmarks and added issue #86. H. Popup Help (aka Bubble Help) and added issue #87. I. Rich Text Editor and added issue #88. j. Site Navigator - General and added issue #89. K. Site Navigator - Tree and added it to issue #89. L. Site Navigator - Tabbed Style and added it to issue #89. M. Tree Grid and added issue #91. N. Wizard and added issue #92.
tatermelon
pushed a commit
to tatermelon/aria-practices
that referenced
this issue
Aug 19, 2016
In addition to the below, This commit also moves the landmark section after the example section. Moved each of the following sections from aria-practices.html to aria-practices-DeletedSectionsArchive.html and created associated issues for drafting new versions. 1. Section "General Steps for Building an Accessible Widget with WAI-ARIA" and created issue w3c#73. 2. Section "Other Widget Authoring Practices"., primarily about aria-valuenow, there is no specific need to raise an issue for this section. 3. Section "Relationships" and raised issues w3c#74, w3c#75, w3c#76, and w3c#77. 4. Section "Managing Dynamic Changes" and created issue w3c#78. 5. Section "Presentation Role" and created issue w3c#79. 6. Section "Form Properties" and created issue w3c#80. 7. Section "Drag-and-Drop Support" and created issue w3c#81 8. Section "Math" and created issue w3c#82. 9. Section "Reusable Component Libraries" and created issue w3c#83. 10. The following 4 Appendix sections related to background on ARIA and created issue w3c#84 A. Background on WAI-ARIA B. Filling the Gaps for Content Delivered to Desktop Browsers c. Building Accessible Applications with WAI-ARIA D. Reasons for Adopting WAI-ARIA 11. The following design patterns: A. Accordion and updated issue w3c#53. B. Autocomplete and updated issue w3c#31. C. Combobox and updated issue w3c#31. D. Datepicker and updated issue w3c#57 E. Dialog (Non-Modal) and updated issue 59. F. Dialog (Tooltip) and added issue w3c#85. G. Landmarks and added issue w3c#86. H. Popup Help (aka Bubble Help) and added issue w3c#87. I. Rich Text Editor and added issue w3c#88. j. Site Navigator - General and added issue w3c#89. K. Site Navigator - Tree and added it to issue w3c#89. L. Site Navigator - Tabbed Style and added it to issue w3c#89. M. Tree Grid and added issue w3c#91. N. Wizard and added issue w3c#92.
mcking65
changed the title
|
Will be excellent if APG explain wizard pattern. Despite the wizard pattern is somewhat similar to carousel and tabs, carousel/tabs has a predefined set of items to show. Wizard will append new item to the list as needed and may remove if the user goes back. Commonly, click on next/submit on the wizard page may send data to the server (e.g. verifying if shipping address is correctly filled). It will be great if the pattern discuss how the wizard page handle asynchronous rendering (e.g. next button will take some time to load next wizard page). And how live region should be used while the page is being loaded. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The APG 1.0 draft included a design pattern for wizards.
Should the APG 1.1 have a wizard design pattern?
When working on this issue, there is some old content that may be useful in the file aria-practices-DeletedSectionsArchive.html.
The relevant section can be seen here:
https://rawgit.com/w3c/aria-practices/master/aria-practices-DeletedSectionsArchive.html#wizard
The text was updated successfully, but these errors were encountered: