Silver Conformance Options Subgroup

23 June 2022


Azlan, DarrylLehmann, GreggVan, janina, maryjom, SusanaPallero, Wilco
Jeanne_Spellman, Shadi_Abou-Zahra, Todd_Libby

Meeting minutes

<janina> Date 23 Jun 2022

Agenda Review & Administrative Items

janina: thoughts on our presentation last week, taking a look at the timeout success criteria.

janina: interesting ways to apply our groups thinking when looking at wider Silver group considerations; policy, conformance, guidance

janina: question to the group. proposing skipping next thursday (the 30th of june)

janina: moving forward in july we can get back to GreggVan edits

Wilco: editors are looking to update the process, speaking about this on upcoming tuesday call.

Wilco: potentially having more Task Force group looking at tasks in 8 week timelines and reports back the findings

Wilco: this group should begin refocusing on third party

janina: would like to discuss with the higher tier group holding on the refocus on third party to complete the current working document

GreggVan: third party is in the groups purview, but we need to move more quickly into the new Task Force model

janina: if we can wrap up in July we'll be in a good space.

Wilco: look to have a proposal before TPAC

janina: Third party will be perhaps more complicated than we expect.

GreggVan: Chairs talked about moving into Task Forces to enable more forward progress

GreggVan: the need to space out the Task Forces to provide breathing room for the members

MichaelC: Sub groups are different to Task Forces, the key being longer duration for the task forces and a more temporary basis for sub-groups.

RESOLUTION: this group will not meet on June 30th, 2022

GreggVan: during the meeting presentation there was some editting happening real-time

Presentation Followup Discussion

GreggVan: A number of anonymous editor's were noticed during the screen share. Judy noted that here suggestions were already picked up, but the edits were happening during the presentation time

janina: finding in discussions that groups using tools are not perfect, but is part of the process.

GreggVan: all of the edits were tracked in the document and we can go forward accepting the changes.

janina: we should be trying to go modal with our suggestions moving forward.

janina: do we consider adding a scenario about an aquisition causing a backward path, loosing accessibilty conformance.

janina: what are the group thoughts on tuesday's presentation?

GreggVan: felt like it was well recieved.

janina: from the presentation notes, what might end up in a tech standard versus a policy suggestion. Splitting up use cases into its own github as this set is very useful for the various subgroup/task forces

janina: we've been asked to talk about impact. Bringing proposals to TPAC as best we can in July.

janina: notion that conforming to every requirement to be accessible may not be possible. Some of our situations illustrate where this may be a challenge

janina: request from the AGWG chair to come back with a response about what the impact will be.

janina: heres an impact to consider? If the requirement remains, and lawyers start picking off organizations with limited capacity, how do we prevent policy from over-riding those requirements.

janina: the word "exception" didn't come up.

GreggVan: if we make no change to the technical document, it's a policy concern. The distinction has helped avoid the exception trap, if the matter is important to handle we can offer a technical change.

GreggVan: somehow we need to find a way to solve for each scenario

maryjom_: we will need to tread very lightly on our recommendations.

GreggVan: we should be very Jeffersonian to find the right words so the material is self evident.

GreggVan: we layout like a report, what needs to happen, what can be affect.

awk GreggVan

Case in Point: SC 2.2.6 Timeouts https://www.w3.org/WAI/WCAG22/Understanding/timeouts

GreggVan: What if a user is working on a form and has to leave for support and can never complete there transaction, this focused on cognitive.

GreggVan: how much time is required to complete this form? less than 24 hours

janina: Important to consider the timeout issue, but this is more than a accessibility consideration but a more broad question on the web

janina: this is a mainstream issue for a lot of people

janina: Apple, Microsoft, Google all looking at password-less authentication. Perhaps a way to piggy back on this building profiles for how your using the web to support users.

janina: APA with privacy liason offering interoperability to this user profile.

janina: a means to provide better service while keeping privacy anonymous.

janina: What mechanism to facilitate the timeout, what mechanic to save and return, what the update timing should be to manage cognitive load.

janina: the outcomes will be generic, but the implementation could be specific

janina: potential methods and technological solutions to this are present.

Summary of resolutions

  1. this group will not meet on June 30th, 2022
Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).


Maybe present: maryjom_, MichaelC