Re: [EXT] [Protocols] Agenda for April 8th, 2022 and Proposed Plan

Hi Jaunita,
Thanks for the clarification.
I’m a wee bit concerned because we have protocols out there in the world. Do we want to suggest that someone could document their own protocol and use that as the basis for evaluating the subjective accessibility of an output? That’s a new thing to consider. I suppose it’s a possibility.
As a group, we previously voted and agreed on protocols to use to assess a site, and learn from that, but we never did that. Could we complete that activity, then take that learning towards this new proposal? What does the rest of the protocols crew think?
Kindly,
Jennifer

From: Jaunita George <jaunita_george@navyfederal.org>
Date: Wednesday, April 6, 2022 at 4:17 PM
To: Jennifer Strickland <jstrickland@mitre.org>, "public-silver@w3.org" <public-silver@w3.org>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Cc: Benjamin Feigel <Benjamin_Feigel@navyfederal.org>
Subject: RE: [EXT] [Protocols] Agenda for April 8th, 2022 and Proposed Plan
Resent-From: <public-silver@w3.org>
Resent-Date: Wednesday, April 6, 2022 at 4:17 PM

Hi Jennifer,

Thanks so much for those excellent points.

I just wanted to explain #2 in the proposed plan a little bit more. We would write a protocol as an exercise to help us think about what a protocol should contain, better define it and answer some of the lingering questions we have. Applying it to a discrete scenario will help us understand how we can use a protocol (similar to the direction we were going), what we would want to see as an outcome and how it will help organizations improve their processes or adherence to the standards. That may help us select examples of good protocols organizations can use and may help us gain consensus on a clear definition. 😊

There’s been a bit of back and forth about what a protocol is and how it should be used, and maybe tackling those issues first will help us gain some consensus and a defined direction before we move on to selecting protocols that meet that definition and would beneficial for how we’re intending to use it.

What do you think?

Jaunita George, JD, PMP, WAS (she/her)
QA-ADA Analyst III, Product Engineering & Delivery Services (ISD)
DHS Certified Trusted Tester (TTV5)
[IAAP WAS circular badge and horizontal name logo for International Association of Accessibility Professionals (IAAP) Web Accessibility Specialist (WAS) credential. To the left is a dark blue circle with three lines of centered white text that read: IAAP Certified WAS. There is a smaller light blue circle that surrounds the dark blue inner circle that designates the WAS credential color scheme. To the right, two lines of dark blue text. Top text reads Web Accessibility Specialist, second line reads International Association of Accessibility Professionals.]<https://www.accessibilityassociation.org/s/wascertification>
Navy Federal Credit Union, 820 Follin Lane, Vienna VA 22180
W: 571-391-0356 | C: 206-778-1882

[Navy Federal Credit Union. Our members are the mission.] [Digital A11ies -- Working Together for All]

From: Jennifer Strickland <jstrickland@mitre.org>
Sent: Wednesday, April 6, 2022 4:06 PM
To: Jaunita George <jaunita_george@navyfederal.org>; public-silver@w3.org; w3c-wai-gl@w3.org
Cc: Benjamin Feigel <Benjamin_Feigel@navyfederal.org>
Subject: [External] Re: [EXT] [Protocols] Agenda for April 8th, 2022 and Proposed Plan

Hi Jaunita and all,
Thanks for communicating an agenda ahead of time. I think this can be very helpful and avoid using the meeting time to agree.
Regarding #2, “Selecting and writing one protocol from scratch as an exercise,” I don’t think we would write a protocol. We could document how one might document using a protocol.
Previously we said we agreed to use PlainLanguage.gov as the protocol and then ended up evaluating what the US Department of Labor documented for their efforts to meet, as I read it, the Plain Writing Act, which is related but a law rather than a protocol. Now there’s a proposal to test “Protocol for how to perform testing against a user process,” using screen reader testing as a user process — but do we have a protocol to use?
Can we agree upon a protocol and site to test, go through the process of how a person might do that, as we previously agreed to do?
Thanks,
Jennifer

From: Jaunita George <jaunita_george@navyfederal.org<mailto:jaunita_george@navyfederal.org>>
Date: Wednesday, April 6, 2022 at 3:38 PM
To: "public-silver@w3.org<mailto:public-silver@w3.org>" <public-silver@w3.org<mailto:public-silver@w3.org>>, "w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>" <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Cc: Benjamin Feigel <Benjamin_Feigel@navyfederal.org<mailto:Benjamin_Feigel@navyfederal.org>>
Subject: [EXT] [Protocols] Agenda for April 8th, 2022 and Proposed Plan
Resent-From: <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Resent-Date: Wednesday, April 6, 2022 at 3:37 PM

Hi All,

At the last meeting the team mentioned that I’ll be stepping in as a co-lead for the Protocols sub-group. I’m really excited to be working with you all in this capacity and to do what I can to further this discussion. I’m new to this, so please don’t hesitate to reach out if I make a mistake or forget something – I’m always available by email and am happy to also set aside time to meet and discuss any questions or comments you have. I really look forward to talking to you all on Friday. 😊

New meeting time:

Last meeting, we agreed to move our regular Friday meeting to 8:00am instead of 9:00am EST. This means that the Protocols Subgroup will be meet this Friday, April 8th at 8:00 AM Boston Time (1400 UTC). I sent out an invite, but please let me know if you didn’t receive it.

Plan for the next few meetings:

To help us answer some of these excellent questions we’ve tackling, I thought we could focus our efforts in the next few meetings to:


  1.  Achieving consensus on how we can use a protocol.



After we’ve achieved consensus on that question, we can move on to:

  1.  Selecting and writing one protocol from scratch as an exercise.

This may help us structure our discussions and help us continue moving forward on all of the wonderful work everyone’s doing – but let me know if you think we should change course at any time. This is only a proposal. 😊

With this idea in mind, here’s an agenda that outlines three examples that show how a protocol could *in theory* be used. We can discuss each of these and maybe propose different or additional examples and add to the list. The idea will be to select one example and write a specific protocol that could be used for that example as an exercise.

*** Agenda for Friday’s meeting ***

agenda+ Protocol for a standard where test results vary so you can't create a test case. We'll be discussing clear language as an example.
agenda+ Protocol for how to perform testing against a user process. We'll discuss screen reader testing as an example. **(Definition: User Process - Series of user actions, and the distinct interactive views that support the actions, where each action is required in order to complete an activity).**
agenda+ Protocol for how an organization can do user testing

Meeting info:

The Zoom teleconference data is provided at this link: https://www.w3.org/events/meetings/bfc72cd9-fdfc-4847-826a-01afb9e3f5e7/20211105T090000


We will be on IRC using the W3C server at https://irc.w3.org<https://secure-web.cisco.com/1bbHg1R0NpE7wu_f231-AnlS80Y-y5vJTvdOEWJENhb8A72iXd8LCnf3ggBw4-smyidfgNxC8x8umv7E05ehkUF2bZBz2YRztLLv4RKaBjPX52PKUDxmvfMGEBjoozskkcieYlkp03z0RNZpT4OYcOd4hVzq8R7ZxdOFKZWkBKST8tH_692bct2eWCZGqxEH2CqP3AYWJvaQCFfDc0IutM6Rj-U09KIPjPRnc7FV26Wdj10BaRhnKyirh5JjBQBiUijZJ9qa0yX2qAvF17eId_iMnLYZJUiOJFMccNsS6Lx1I4XZzBbvOxVip14Ng8wGLJfXvx15u76cOB7dAeH7XvgpoWs6R_tsGa3dqAcv4R_28w7gc_bd-NL4b_nyhs9ocwFRphYixX3lTUlkEH0Nokh_o6hHppEenQieUgyV9aZx_s1E0SmDtT5e5jzWNn35PIXxCXehg937DHDABmN_O-g/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Firc.w3.org%2F__%3B%21%21ACWV5N9M2RV99hQ%21ZvVx1wh89EAXhBiorHpgvdpQRlEtQPxaEsJbJ7_Q3MrxtnQGs5lwbIC34ybOl3ZsYw%24>, in channel #silver-protocols

Where to find more information:

These and additional details of our work, including minutes, current, and archived draft documents are available on our subgroup wiki page here: https://github.com/w3c/silver/wiki/Protocols<https://secure-web.cisco.com/1O3VrQQ04mfiETDUKCZHSfOZKceiXtIIUdcEUxqhgdsgo9abpVdc4fvbCkZhqpCfHDonIZg-fBZhET82AHyBdOAAkyc1CdDBoBzxBqn0m36b2nv8YPoX9RSqkA9oaWRVz_9uVjwCIe_RimJy2OukOd6NVRLvjhBUclVlbHBnDG0GrSM9waKV22Dpg6hpMYEJ_WJ3ML8l7GRsC8Wiy0qWECnTQOKx8kOl8B5wfW50_sFgCwte03lKCjuvfmDTWbSMIN2-X1pzshYCRn8Cgzka_Kb_d3qwlCwDEYTeqb_fO9ZbG_bkQCQtdCKJHDBljp-FgnHe3tJUY-nAfyzemjmEYJZ6IRzJ8U-pvw0FId95ZKICe92BvUfhb23-H-VunfDClvOT-0iVdENgn_R0KOUomBPAAY1umi9ATs_n4KlBgqUJ-7rVVkwy1ScSb6YvocWBR0wPJ1lTzWWR6HL4Ru7JWVA/https%3A%2F%2Fgithub.com%2Fw3c%2Fsilver%2Fwiki%2FProtocols>


Jaunita George, JD, PMP, WAS (she/her)
QA-ADA Analyst III, Product Engineering & Delivery Services (ISD)
DHS Certified Trusted Tester (TTV5)
[IAAP WAS circular badge and horizontal name logo for International Association of Accessibility Professionals (IAAP) Web Accessibility Specialist (WAS) credential. To the left is a dark blue circle with three lines of centered white text that read: IAAP Certified WAS. There is a smaller light blue circle that surrounds the dark blue inner circle that designates the WAS credential color scheme. To the right, two lines of dark blue text. Top text reads Web Accessibility Specialist, second line reads International Association of Accessibility Professionals.]<https://secure-web.cisco.com/1TureYSgTTtpSb9eCnmLJsvP09P3eXGZdEaNPsJsKT0A2XPT1jaU00RsAjN8NX52wfOkEO50vjCvGSJCprGfVNO1wXxVlGd9Q9KqXAukNUhaBHsuNZjdxPhPm9WZ4WDe8Lb4EySWcpYMBG97_g_Rohb8Q0YsiKg25W3Nlu1fbaaEXtzsAqVtb2pq5CcjC69AL44Zon9Is24WYCN8Aq8lfh5e5Uaa7sM04coF_8M2JFFGMamDcSLC7UoL8mD-1ayPIXpPzO_tPIWBJ73g_JGyCcOHeCcOP_jLvKrlohTXOFxy3zc1Pvt9j9lXCefrPsLkNNUFjmGQaa_qGzqV3VUAnu2tRgkEmssWI9lb3VvtU0p-MDFEIaNfS7XGSzD-SCJN9Y-uW9n5uZ93mTEhmnNKIDkYeS6AKm6Tlt_RHg1nS7okvXNKZAOU9g21kWQVW1lqhDE3NAcv5z1gMYPMF6mrVvw/https%3A%2F%2Fwww.accessibilityassociation.org%2Fs%2Fwascertification>
Navy Federal Credit Union, 820 Follin Lane, Vienna VA 22180
W: 571-391-0356 | C: 206-778-1882

[Navy Federal Credit Union. Our members are the mission.] [Digital A11ies -- Working Together for All]