-
Notifications
You must be signed in to change notification settings - Fork 355
May 7, 2019 Meeting
Setup and review agenda -- 3 minutes.
Start at 11:03 - 10 minutes
- Issue 971: Collect feedback on auto-rotating image carousel example introduced in APG 1.1 Release 3 (January 2019)
- We have Jon's PR 1018 for Issue 1007: Image Carousel Example: Use button elements for slide controls and make rotation control always visible
- Are there other issues that need to be filed based on feedback in issue 971?
From Siri:
The content over the image, and previous/next button are difficult to see due to the busyness of the image behind it. Add a background color to the buttons and insert CSS color block between the text and the image so that they can be visible even when the background image is busy.
From James:
I love the Microsoft carousel. Can we use that as inspiration?
Start at 11:13 - 10 minutes
Update from Jon and Mark on pattern and combobox example:
- Draft of date picker pattern - Mark and Jon
- Issue 57: Draft Date Picker design pattern
- Draft date picker combobox example
- Issue 34: Develop example of date picker design pattern using a combobox that opens a dialog
Start at 11:23 - 7 minutes
Review description of issue 1028 - Add site navigation example that uses disclosure buttons that show lists of links.
Start at 11:30 - 10 minutes
- Discuss which sections need task force feedback.
- Discuss any open issues or questions blocking progress.
Start at 11:40 - 10 minutes
- Discuss review objectives: What do we want to ensure every example review covers? Possibilities:
- Code review: from engineering perspective, what do we want to ensure?
- Functional testing: without assistive technology, do examples perform as expected in target browsers?
- Assistive technology interoperability: Is the ARIA markup correct? That is, if an AT supported ARIA correctly, would it be able to function as expected?
- Editorial: Does documentation follow editorial guidelines?
- To make reviews more efficient for individuals, should we have specific people assigned to specific types of review?
- Would people be able to better manage time commitment if they had a specific scope of responsibility for their review work?
- Unless actively making pull requests, can each task force member commit to an average of 1 review per week?
If ahead of schedule, triage unlabeled issues with remaining time until 10:57.
- Triage open issues missing labels
- Triaged issues have:
- One of the labels that indicates type of issue: bug, enhancement, editorial, documentation, maintenance
- One of the labels that indicates part of APG: code example, pattern, guidance
- A milestone indicating target resolution date
- If related to a pattern or code example, it is assigned to a project.
- Unlabeled issues needing triage
Start at 11:57 -- 3 minutes.
- Next meeting: May 14, 2019
- Other business for future agendas?
- Home
- About the APG TF Work
- Contributing
- Meetings
- Management and Operations Documentation
- Publication Change Logs