14:58:08 RRSAgent has joined #wcag2ict 14:58:12 logging to https://www.w3.org/2024/02/22-wcag2ict-irc 14:58:12 RRSAgent, make logs Public 14:58:13 Meeting: WCAG2ICT Task Force Teleconference 14:58:15 zakim, clear agenda 14:58:15 agenda cleared 14:58:23 chair: Mary Jo Mueller 14:58:28 meeting: WCAG2ICT Task Force Teleconference 14:58:35 Zakim, please time speakers at 2 minutes 14:58:35 ok, maryjom 14:58:41 Regrets: Mike Pluke, Daniel Montalvo 14:58:47 Agenda+ Announcements 14:58:57 Agenda+ Survey results - Review of 4.1.3 Status Messages proposal 14:59:06 Agenda+ Survey results - Question 5 of the Review of proposed responses to public comments - group 1 14:59:14 Agenda+ Survey results - Review of proposed responses to public comments survey results 14:59:55 PhilDay has joined #wcag2ict 15:00:00 present+ 15:00:16 Chuck has joined #wcag2ict 15:00:48 loicmn has joined #wcag2ict 15:01:37 present+ 15:01:52 present+ 15:03:34 present+ 15:03:36 LauraBMiller has joined #WCAG2ICT 15:03:36 Devanshu has joined #wcag2ict 15:03:42 present+ 15:03:44 present+ 15:03:46 Present+ 15:03:57 present+ 15:04:21 Scribe+LauraBMiller 15:04:31 Scribe+ LauraBMiller 15:04:38 FernandaBonnin has joined #WCAG2ICT 15:05:47 present+ 15:05:53 Zakim, take up item 1 15:05:53 agendum 1 -- Announcements -- taken up [from maryjom] 15:06:03 Sam has joined #wcag2ict 15:06:17 https://github.com/w3c/wcag2ict/wiki/Work-left-for-second-public-draft 15:06:33 present+ 15:06:54 Maryjom - for announcements we are working through and all content is in the editors draft. Document is up to date. We finished everything in the first table 15:07:19 Maryjom, starting to move the completed items to the bottom of the table. 15:07:49 Bryan_Trogdon has joined #WCAG2ICT 15:07:57 present+ 15:08:39 Maryjom: hoping to have few changes when it goes out for review. As soon as you can, take up an item or get your item done and let me know when it is ready to be discussed. 15:09:20 Maryjom - there may or may not be a survey this week. We have a few SCs to work on tomorrow. Text spacing and reflow. 15:09:42 Zakim, next item 15:09:42 agendum 2 -- Survey results - Review of 4.1.3 Status Messages proposal -- taken up [from maryjom] 15:10:04 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Status-Messages-update/results 15:10:22 Topic: SC 4.1.3: Word substitution language 15:10:35 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Status-Messages-update/results 15:11:22 Option 1 – 4.1.3 taken literally: https://docs.google.com/document/d/1ejuKX3cq06b3MY48h2wJPHJXfFYJLIjI0rUNf3PfoJQ/edit?usp=sharing 15:11:37 Option 2 – 4.1.3 Contextualized: https://docs.google.com/document/d/1ejuKX3cq06b3MY48h2wJPHJXfFYJLIjI0rUNf3PfoJQ/edit#heading=h.71h05lkcix1x 15:11:43 Two options for the main guidance we are reviewing. Option 1. 4.1.3 taken literally. Option 2 was a contextualized version 15:11:51 Split vote. 15:12:47 q+ to ask why people liked option 2 15:12:54 ack bruce_bailey 15:12:54 bruce_bailey, you wanted to ask why people liked option 2 15:13:02 q+ 15:13:18 ack loicmn 15:13:34 mitch11 has joined #wcag2ict 15:13:37 present+ 15:14:03 Poll: Which option do you prefer? 1) Option 1, 2) Option 2, 3) Something else 15:14:11 1, but also accept 2 15:14:17 1, also accept 2 15:14:21 2, but also accept 1 15:14:25 1, either is fine 15:14:27 1, but also accept 2 15:14:28 1 but also accept 2 15:14:38 Either is fine 15:15:11 Maryjom: looks like we are settling on option 1. Incorporate the word substitution as is in option 1 15:15:29 DRAFT RESOLUTION: Incorporate the word substitution Option 1 as-is for SC 4.1.3. 15:15:34 +1 15:15:37 Applying SC 4.1.3 Status Messages to Non-Web Documents and Software This applies directly as written, and as described in Intent from Understanding Success Criterion 4.1.3 (also provided below) without word substitution. 15:15:41 +1 15:15:42 +1 15:15:46 +1 15:15:52 -1 15:15:52 +1 15:15:53 q+ 15:15:56 q+ to ask about adding note 15:16:02 ack mitch 15:16:16 good catch mitch ! 15:16:18 +1 15:16:21 Option 1: Applying SC 4.1.3 Status Messages to Non-Web Documents and Software This applies directly as written, and as described in Intent from Understanding Success Criterion 4.1.3 (also provided below) without word substitution. 15:17:07 RESOLUTION: Incorporate the word substitution (which is really no word substitution) as as shown in Option 1 as-is for SC 4.1.3. 15:17:38 Ack Bruce_bailey 15:17:38 bruce_bailey, you wanted to ask about adding note 15:18:47 Bruce_bailey - Loic raises a good point with regard to providing context and we could do that with a note. 15:19:21 Maryjom - move this to the Friday meeting 15:19:26 regrets for tomorrow 15:19:26 Loïc raised a concern about a note to provide more context - will discuss at a Friday meeting. 15:19:56 Philday added note to google doc 15:19:57 q+ 15:20:05 Ack Mitch11 15:20:10 ack mitch 15:20:37 i agree -- i just don't want to loose the thread 15:20:56 Mitch11 - we consensed on the content without a note. 15:21:24 Topic: SC 4.1.3: Notes 1 and 2 15:21:38 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Status-Messages-update/results#xq5 15:22:01 DRAFT RESOLUTION: Incorporate Notes 1 and 2 as proposed in the survey. 15:22:05 +1 15:22:09 +1 15:22:12 +1 15:22:34 +1 15:22:43 NOTE 1: For non-web documents and software where status messages are not implemented using markup languages, there is still a user need to have status messages be programmatically exposed so that they can be presented to the user by assistive technologies without receiving focus. This is typically enabled through the use of accessibility services of the user agent or platform software. NOTE 2: See also the discussion on Closed Functionality. 15:22:48 +1 15:23:01 +1 15:23:04 +1 15:23:04 RESOLUTION: Incorporate Notes 1 and 2 for SC 4.1.3 as proposed in the survey. 15:23:04 +1 15:23:05 +1 15:23:23 Topic: SC 4.1.3: content for SC problematic for closed functionality 15:23:35 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Status-Messages-update/results#xq6 15:24:05 +1 option 2 15:24:14 DRAFT RESOLUTION: Incorporate into the proposed SC problematic for closed functionality, the proposed content for SC 3.3.8 as-is. 15:24:17 Option 2: Proposed change to to the content for 4.1.3: 4.1.3 Status Messages—Requires information in a programmatic determinable form. NOTE Non-web software with closed functionality would need equivalent facilitation to provide access to status messages. 15:24:19 +1 15:24:19 +1 15:24:25 +1 15:24:36 +1 15:24:39 +1 15:24:51 +1 15:25:02 +q 15:25:05 +1 15:25:11 +1 15:25:22 q- 15:25:24 RESOLUTION: Incorporate into the proposed SC problematic for closed functionality, the proposed content for SC 3.3.8 as-is. 15:25:46 Zakim, next item 15:25:46 agendum 3 -- Survey results - Question 5 of the Review of proposed responses to public comments - group 1 -- taken up [from maryjom] 15:26:13 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Jan-public-responses/results#xq7 15:28:06 Phil's comments: https://github.com/w3c/wcag2ict/issues/308#issuecomment-1929191313 15:29:27 q+ 15:29:34 ack mitch 15:31:48 Proposed answer that is being discussed: https://github.com/w3c/wcag2ict/issues/308#issuecomment-1912719285 15:32:00 q+ 15:32:07 ack PhilDay 15:32:28 Mitch11: I would have deleted that first paragraph. (Confirming that we are talking about bypass blocks paragraph) 15:33:20 q+ to ask if we have parking lot ? 15:33:46 ack bruce_bailey 15:33:46 bruce_bailey, you wanted to ask if we have parking lot ? 15:34:12 Bruce_bailey: agree that taking away that paragraph is the better choice. Do we have a parking lot for these things (to find a better home for that paragraph later) 15:35:01 Proposal from mitch11 is to delete the following paragraph: 15:35:03 Bypass Blocks is one where (if applied) non-web software would likely automatically satisfy the requirement. Web content has the problem that one cannot quickly navigate to the main part of the content - you have to tab past every menu and navigation link whenever there is a left or top navigation on a website. For a native desktop application, one simply uses a keystroke to toggle between the menu and the main part of the application. For mo[CUT] 15:35:03 q+ 15:35:10 q? 15:35:15 Ack Sam 15:35:15 For mobile applications, a user simply taps where they want to start interacting. If navigating sequentially using a screen reader, mobile applications also have much smaller top level menus, meaning the burden of getting past them to get to the main part of the application is minimal - especially when they employ the use of the hamburger menu. 15:35:16 ack sam 15:35:43 q+ 15:35:44 Sam: this is also true for mobile and mobile apps. Such as alt. There are other/different ways in non desktop environments 15:35:46 q+ to suggest polling the deletion of para 2 15:35:50 ack mitch 15:36:11 i kind of wish we had an Understand doc for WCAG2ICT for these sort of examples which will become out of date 15:36:32 Mitch11: my concern is that commenters who are active in WCAG have expressed that there are times that bypass block is needed. 15:36:50 Can we avoid that debate? 15:37:21 Maryjom: Bypass blocks is limited and isn’t being applied to non web software. 15:38:02 q? 15:38:31 q+ 15:38:34 Maryjom: it’s not being applied anywhere in the standard. Why are we worrying about this SC if there are no standards that apply it to your softawre? 15:38:35 ack PhilDay 15:38:35 PhilDay, you wanted to suggest polling the deletion of para 2 15:38:52 q- 15:39:09 Poll: Should we delete the paragraph starting with "Bypass Blocks is one where..."? 15:39:20 +1 15:39:22 +1 15:39:24 +1 15:39:25 +1 15:39:26 +1 15:39:26 +1 15:39:28 +1 15:39:28 +1 15:41:15 +1 15:41:19 +1 15:41:22 Poll: Remove the “Task Force is unaware…” paragraph? 15:41:27 +1 15:41:32 +1 15:41:36 +1 15:41:41 +1 15:41:42 +1 15:41:42 +1 15:41:50 +1, can accept either way 15:42:12 Further comment from issue opener: https://github.com/w3c/wcag2ict/issues/308#issuecomment-1936466560 15:44:13 q+ 15:44:19 ack mitch 15:44:33 q+ 15:44:47 https://w3c.github.io/wcag2ict/#software 15:44:55 Mitch11: This last comment, I’m not sure what it is asking. I think he is asking to repeat the note in the definitions. 15:45:00 https://w3c.github.io/wcag2ict/#set-of-documents 15:45:06 https://w3c.github.io/wcag2ict/#set-of-software-programs 15:45:12 ack PhilDay 15:45:34 PhilDay - I thought the same, it was asking for an additional note. I don’t think it’s necessary. 15:46:15 q+ to agree , but want to mention... 15:46:15 ack bruce_bailey 15:46:15 bruce_bailey, you wanted to agree , but want to mention... 15:46:15 > That SC is currently not even being applied by 508 or the EN 301 549 to native applications. 15:46:19 Bruce_Bailey - I don’t agree with removing it. 15:47:45 Maryjom: we are not changing the document. The commenter should look to the standards. 15:48:09 q+ 15:48:15 ack PhilDay 15:48:16 Ack PhilDay 15:48:43 USAB dropped "sets of non-web document" for 508 just because "set of non-web software" was so confusing to people. 15:49:27 PhilDay - native application should be considered as software. 15:49:33 That should be our response. 15:49:52 The 508 preamble discusses the issue. 15:49:59 https://w3c.github.io/wcag2ict/#software 15:50:01 PhilDay - maybe we can add the link 15:51:32 DRAFT RESOLUTION: Finalize the proposed answer to Issue 308 with the changes proposed by Mitch (removing the two paragraphs polled above) and adding a link in the first sentence to the key term "software". 15:51:40 +1 15:51:49 +1 15:51:52 +1 15:52:00 +1 15:52:02 +1 15:52:04 +1 15:52:28 RESOLUTION: Finalize the proposed answer to Issue 308 with the changes proposed by Mitch (removing the two paragraphs polled above) and adding a link in the first sentence to the key term "software". 15:52:34 q+ 15:52:40 +1 15:52:52 ack mitch 15:53:05 +1 to Mitch's sentiment - careful writing is appreciated 15:53:07 +1 to mitch 15:53:31 Zakim, next item 15:53:31 agendum 4 -- Survey results - Review of proposed responses to public comments survey results -- taken up [from maryjom] 15:53:46 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comment-group2/results 15:54:30 Topic: Issue 77 - Making content usable 15:54:37 https://github.com/w3c/wcag2ict/issues/77 15:54:39 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comment-group2/results#xq1 15:54:55 Proposed changes in https://github.com/w3c/wcag2ict/pull/309/files 15:55:40 DRAFT RESOLUTION: Accept the changes and issue answer for Issue 77 as proposed in the survey. 15:55:44 +1 15:55:45 +1 15:55:45 +1 15:55:45 +1 15:55:48 +1 15:55:48 +1 15:55:49 +1 15:55:52 +1 15:56:01 RESOLUTION: Accept the changes and issue answer for Issue 77 as proposed in the survey. 15:56:05 Proposed addition from survey: Further adjustments have been made to the language and location of documents that are referred to by WCAG2ICT, including "Making Content Usable..." that will hopefully address your concerns in the additional comments (above) in this issue. Note that the WCAG2ICT Task Force needs to remain mindful that this document is not meant to provide techniques for meeting or going beyond WCAG. 15:56:11 Its content is limited to interpreting WCAG criteria in a non-web context. Any guidance beyond that should instead be included in or referenced by other documents specifically focused on implementing accessibility requirements in non-web technologies. We will continue to mention this resource, but in the context we feel is appropriate for our scope of work. 15:56:43 Topic: Issue 145 - Add info/content on the WCAG exemptions in regulatory work 15:56:46 https://github.com/w3c/wcag2ict/issues/145 15:56:53 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comment-group2/results#xq2 15:58:33 q+ 15:59:37 ack Sam 15:59:41 q+ 16:00:13 ack Chuck 16:00:29 q+ to suggest we just make fact-based statements 16:00:53 ack bruce_bailey 16:00:53 bruce_bailey, you wanted to suggest we just make fact-based statements 16:01:24 I must depart. 16:01:36 yes, just make fact based-statements 16:30:12 maryjom has joined #wcag2ict 16:30:18 zakim, end meeting 16:30:18 As of this point the attendees have been PhilDay, bruce_bailey, loicmn, olivia, Chuck, Devanshu, LauraBMiller, maryjom, FernandaBonnin, Sam, Bryan_Trogdon, mitch 16:30:21 RRSAgent, please draft minutes v2 16:30:22 I have made the request to generate https://www.w3.org/2024/02/22-wcag2ict-minutes.html Zakim 16:30:29 I am happy to have been of service, maryjom; please remember to excuse RRSAgent. Goodbye 16:30:29 Zakim has left #wcag2ict 16:38:57 rrsagent, bye 16:38:57 I see no action items