Review April Tasks and assign tasks
Sarah reviews Basecamp tasks for April
Task 1: Heartbeat Publication - need content update collaborating with Jeanne for deadlines and sharing with group for edits
Task 2: Review updated WCAG3 writing guidance
Task 3: Work on exceptions so that when we have an outcome such as 'provide an error notification when user receives an error', review the minutes doc and write an exception
Task 4: Review Github templates so that we can understand procedures for having a repo and creating PRs as needed
Task 5: Work on error prevention tests (will come back to this)
Task 6: Revisit "all-use" functional needs. Shannon is looking into this one. Details in Basecamp comments.
Task 7: Map tests to user needs in guidelines outlines
Task 8: Map notification and contingencies tests to user needs
Sarah has been working thru Tasks 7 & 8
Stacey will take lead on Task 1, Task 4, and Task 5 with Dean's help on Tasks 4 & 5.
Todd is working on monitoring Github issues but has not heard back from Jeanne. Issue still exists. Todd will continue to monitor the Github issues.
Todd was added to the regular participant list on the Wiki page.
Stacey was added to the regular participant list on the Wiki page.
Review progress on Error Prevention tests (Dean)
Error Prevention tests, Dean and Sarah describe the 'Error User Needs Worksheet' spreadsheet
Referring to the Template for Content Creation Process document
Worksheet has outcomes and user needs defined, this is our data source in terms of insight and progress
<sarahhorton> Process document: https://
<sarahhorton> Develop tests: https://
Use the documents provided above to write tests
Sarah is working on mapping the tests.
Need to take these tests and turn them into tests specific for WCAG 3 (refer to WCAG 3 FPWD, 7.4, Method, Tests) Documentation
<sarahhorton> Example of tests: https://
What format do we use now as we write the tests?
<sarahhorton> Errors Guidelines Outline: https://
Add tests to the document linked above.
(Sarah)There's a lot of guidance. We write the tests and update the scoring rubric to share with Silver.
Focus on Prevention tests tab in the spreadsheet.
Example - with Instructions persist, test could be if the placeholder text is present but disappears on focus; that would be a failure of the criteria
Work on live example: In Errors Guidelines Outline, Instructions Persist: Test case: For each form input that has instructions, ensure that instructions are visible at all times. Test case: For any form input that includes placeholder text, ensure the instructions are also provided in a format that is visible at all times.
We can add backend solutions to methods, where applicable as well.
If anyone wants to 'take a stab' at writing the tests up, the more the merrier.
Discuss “all use” functional needs; review progress assigning to individual functional needs on Error User Needs Worksheet
<sarahhorton> Github issue: https://
Skipping agenda item 3 today.
Reviewing Email: Feedback on wcag 3.0 (How-To Design) from jspellman on Basecamp
Todd: without seeing the visible examples referenced in the email, it seems... that this is a usability issue for the editors
Sarah: It has been sent to us to help out for a response since we are working on content now.
Sarah: We will pick this up next week on the call and collectively work on it.
Todd and Sarah will ask Jeanne S. for the screenshots again.
Discuss reinstating working meetings
Sarah: Do we want to start having working sessions again? Two hours, Zoom, come and go as available
Working sessions will resume on Fridays from 10am-11:30am EST beginning 4/23/21.
<sarahhorton> Errors wiki: https://