16:00:36 RRSAgent has joined #ag 16:00:36 logging to https://www.w3.org/2021/12/07-ag-irc 16:00:49 ToddL has joined #ag 16:00:55 GreggVan has joined #ag 16:01:07 present+ Laura_Carlson 16:01:08 bbailey has joined #ag 16:01:10 present+ 16:01:11 present+ 16:01:14 present+ 16:01:18 present+ 16:01:20 Nicaise has joined #ag 16:01:25 present+ 16:01:26 Chuck: We are working on technical issues and will start the 2nd minute after the hour 16:01:37 Present+ 16:01:41 Jen_G has joined #ag 16:01:41 present+ 16:01:49 Present+ 16:01:52 mbgower has joined #ag 16:01:54 Raf has joined #ag 16:01:54 present+ 16:02:01 GN015 has joined #ag 16:02:10 present+ 16:02:11 Chuck: Thank you for coming. We need a scribe for the 2nd hour. 16:02:17 Regina has joined #ag 16:02:20 present+ 16:02:22 present+ 16:02:28 JakeAbma has joined #ag 16:02:33 present+ 16:02:41 mbgower - like this? https://www.w3.org/WAI/GL/wiki/Scribing_Commands_and_Related_Info 16:02:52 Chuck: Anyone want to introduce themselves? 16:02:54 MelanieP has joined #ag 16:02:55 present+ 16:02:59 present+ 16:03:02 present+ 16:03:08 Chuck: Any new topics for future conversations? 16:03:17 zakim, take up item 1 16:03:17 agendum 1 -- Measurement Proposals -- taken up [from Chuck] 16:03:37 Chuck: Jeanne will start first. I did not send the links out to this 16:03:39 https://docs.google.com/document/d/10-1vKOYXBDKLJecfLmtz9tH3T1Y8PRW7pqG6HAcvaHU/ 16:03:40 AWK has joined #ag 16:03:50 +AWK 16:03:58 Chuck: These are scoring proposals we want the Accessibility Guidelines and Silver group to review, consider 16:04:06 JF has joined #ag 16:04:09 ...Next will be Alastair 16:04:12 Present+ 16:04:17 present+ 16:04:44 Jeanne: This was a consolidation of a number of discussions different groups have had about 16:04:53 ...ways to improve what was in the 1st public working draft. 16:05:07 ...I started with an attempt to make scoring consistent across guidelines 16:05:09 Wilco has joined #ag 16:05:19 Jeanne: many addressed this in content 16:05:32 ...To simplify the scoring to make it easier 16:05:40 ...We will be counting errors 16:05:47 ...And it removes the wholistic tests. 16:05:57 ...It was a really good ideas, but it has raised a lot of questions. 16:06:04 ...I don't think we have a lot of answers for them 16:06:20 ...Personally the idea raised by John Folio is better than the wholistic test idea. 16:06:36 ...I want to propose we remove the holistic tests in Section 4 16:06:57 ...In the testing section we would simplify the types of tests, so it only includes the atomic tests 16:07:02 ...We could rename it test 16:07:15 present+ 16:07:15 present+ 16:07:28 ...In section 4: atomic could change to unit tests 16:07:37 q? 16:08:04 ...In section 5: testing could be by view instead of 16:08:09 ...We were doing it by element in 5.1 16:08:14 https://www.w3.org/2017/08/telecon-info_ag 16:08:21 ...Instead of by element, recommend chaning it to view 16:08:32 ...It could be used beyond web if appropriate 16:08:48 ...Instead of a different scoring system for each guideline, we would go to a percentage score 16:09:00 ...Guidelines that are true/false could be 100% 16:09:13 ...100% minus failures 16:09:20 Jason_Rutgers_ has joined #ag 16:09:24 ...All guidelines with a failure rate less than 5% would pass 16:09:30 ...No fractional percentages 16:09:43 ...Anything .5 or higher would round up - this responds to one of the github issues 16:09:57 ...Any guidelines with a quality measurement will have specific criteria defining each band 16:10:05 ...So it can be compared with different guidelines 16:10:18 ...I am recommending we remove sections 5.2, 5.3, and 5.4 16:10:26 ...This will simplify a lot of the scoring 16:10:43 ...Critical errors would remain, but they automatically fail when encountered 16:10:53 q+ to ask about percentages and critical errors 16:10:55 ...Testing could stop if encountering a critical error 16:11:11 jon_avila has joined #ag 16:11:15 q+ 16:11:15 present+jon_avila 16:11:23 Chuck: If there is a critical failure you can stop testing. But, if one isn't encountered, you are generating a percentage 16:11:32 ...I know that others had expressed concerns about counting the failures 16:11:35 Q+ 16:11:46 Q+ 16:11:51 ...To me it appears that in order to get the percentage, you still are counting the number of failures 16:12:04 ...With a critical failure you can stop - the percentage is not meaningful 16:12:24 ...Is there value in having the percentage if one is encountered, or is it just a zero? 16:12:33 Jeanne: I think that would be up to the tester and what they are reporting 16:12:41 ack Ch 16:12:41 Chuck, you wanted to ask about percentages and critical errors 16:12:42 ...The accessibility consultancy I have worked for will continue to test 16:12:50 ...They want to give a report to the client of all issues 16:12:58 q- 16:12:59 ...But for conformance reports, they would not need to 16:13:20 ...I will finish the examples, then can go through the questions 16:13:39 please do go ahead with examples 16:13:44 Jeanne: I know there is a group working on critical errors, and I wrote this back in October 16:13:44 q? 16:13:59 ...since then we have done a lot more work on dividing up the issues 16:14:05 ...I am happy to go with that group's proposal 16:14:25 ...In regards to counting the passes - I am trying to set it up so that is not needed 16:14:37 ...You can have tools that count the instances, but not as the tester 16:14:49 ...Critical error would give a score of zero percent 16:15:01 ...Without one, (reads from the document) 16:15:12 ...This does require tool makers to count the elements 16:15:19 ...Otherwise the test remains the same as today 16:15:22 ...First example 16:15:30 q? 16:15:43 ...If the view has no critical errors, it would pass 16:15:47 q+ 16:15:50 ...Second example 16:15:56 ...(reads from the document) 16:16:06 ...This would fail 16:16:21 ...I would like to point out I did not work with any subgroups about this 16:16:22 q+ 16:16:25 ...These were my examples 16:16:36 q+ to say is there a definition of "functional image" 16:16:44 ...Clear words (reads from document) 16:16:55 ...I made this up, the subgroup may have a very different idea 16:17:05 ...I looked at Silverwriter 16:17:18 ...(reads the calculation from the document) 16:17:35 ...I gave an example in the document 16:17:57 ...I did the same thing with a video without captions and an accessible transcript 16:18:11 ...The 1st example (reads from the document) 16:18:21 q+ to say that counting by tool relies on automated tests, while many Accessibility tests are manual 16:18:24 ...The 2nd example (reads from the document) 16:18:30 qv? 16:18:34 ack Greg 16:18:36 q+ to say that the percentage should be whatever it is, and if there is a critical error it fails. Gives better information to teams doing fixes. 16:18:36 GreggVan: Very interesting. 16:18:49 ...View: you said you are going to view vs page 16:19:00 ...WCAG2ICT we tried to make view work, and we never could 16:19:07 ...You have a view, you click on something and it expands 16:19:13 ...1 page could have 10,000 views 16:19:19 ...We were applying it to software 16:19:31 ...That is a great idea, but we couldn't figure out how to make it work 16:19:48 ...Percent score: you are talking about the percent of failures - which could be gamed 16:19:57 +1 to Gregg 16:19:59 ...You can put a lot of images at the bottom with alt text 16:20:07 ...The content no longer needs alt text 16:20:14 "...there is a possibility that the system may be gamed in order to make a conformance claim. For example, a site with many additional spacer images with appropriate null alt will more easily meet higher threshold values for the ratings.“ (Adobe - https://github.com/w3c/silver/issues/400) 16:20:26 ...When you talk about percent: 95% of the building is accessible. Is that good enough? 16:20:37 ...Or 95% of a cafeteria is accessible - is that enough? 16:20:45 ...The critical errors might help with this 16:20:53 q? 16:21:12 ...You did talk about a critical error being any functional image, and later you said meaningful images 16:21:23 ...A chart or diagram is not functional, so that is something to think about 16:21:37 ...For the caption example, that would need to be a critical error 16:21:49 Chuck: I am assuming you will mark these questions down for later 16:22:03 ack JF 16:22:15 JF: I have a couple of concerns. Greg called out the counting concern 16:22:33 ...We have heard from multiple people (including a DHS tester and Adobe) that this will be problematic because it can be gamed 16:22:49 ...I was concerned about the tool vendors requirement for counting - this assumes everyone will have a tool 16:22:55 ...Will there be a free and open source tool? 16:23:00 ...We have not created tools before 16:23:10 ...If this is part of a scoring mechanism, we should provide one 16:23:18 ...I am concerned about the functional image testing 16:23:29 ...I can have alt equals button - how useful this is... 16:23:44 ...The whole section around clear words, I have concerns about the list of common words 16:23:47 q? 16:23:55 ...Who creates the list? Impact on internationalization 16:24:00 ...I appreciate the effort here 16:24:08 ack Wil 16:24:09 Fazio has joined #Ag 16:24:11 ...I am concern that lots will prove to be difficult to impelement 16:24:30 Wilco: Tools currently really don't agree on what is an image, what is on the screen, what is off screen... 16:24:47 ...Doing this in a consistent way requires a new category of tools that do not exist today - a big ask 16:24:48 +1 to Wilco 16:24:48 Judy has joined #ag 16:24:52 ...We have nothing like this today 16:24:56 +1 to Wilco 16:25:01 ...This makes me uncomfortable 16:25:03 ack jon 16:25:17 JonA: In terms of an image - what is an image? 16:25:25 ...An SVG? Icon? 16:25:37 Chuck: Jon is on mute 16:25:46 ack mb 16:25:46 mbgower, you wanted to say is there a definition of "functional image" 16:25:47 +1 to JF. Same holds true for quality of not only alt text but quality of captioning. 16:25:50 ...If you have more to say, please put yourself back on cue 16:26:00 mgower: Images are maybe their own outlier 16:26:07 ...Is there a definition of functional image? 16:26:20 ...Also, the automated tool is relatively possible to detect images 16:26:31 Trace has created or commissioned 3 free tools to allow provisions in WCAG. Agree with JF but I would not think we should not do the right thing for lack of a free tool. That doesn't mean we know how to create these tools - but we should think about free versions of tools - before tossing out a good idea. That said - we should not solve problems with imaginary tools as JA said. 16:26:32 ...understanding when the image serves a purpose is different 16:27:10 ...I think that we can marry what can be automatically tested with consistency 16:27:30 ack GN 16:27:30 GN, you wanted to say that counting by tool relies on automated tests, while many Accessibility tests are manual 16:27:33 ...I determined by doing this...my protocol was this... 16:27:41 GN: I am also struggling with the coutning 16:27:49 ...Counting images with a tool could be possible 16:27:56 q+ to mention JF's efforts on protocols 16:28:01 ...For several requirements we have automatic tests 16:28:02 Did my conversation come through? 16:28:06 Francis_Storr has joined #ag 16:28:10 ...Color contrast on visual indicators 16:28:12 present+ 16:28:15 ...1st one has to judge which lines need contrast 16:28:17 @jon - just the first sentence 16:28:20 ...This needs to be decided by a human 16:28:33 ...It has to be counted manually: error prone, huge burden 16:28:42 ...I would rather not count, and just go through the severity 16:28:52 q? 16:28:54 ...blocker? hurdle with a work around? kind of an inconvenience 16:29:01 +1, number of issues + severity 16:29:09 "...as a certified trusted tester in the DHS Accessibility Test Process for Web, using the measure of "a percentage of overall instances" to obtain this data will be problematic. It would be burdensome to expect a manual test process to "count" all the instances where a test condition applies.“ 16:29:19 Chuck: AWK may be muted 16:29:30 (Ann Marie Davis - https://github.com/w3c/silver/issues/275) 16:29:40 ...We are meeting regularly 16:29:51 ...reach out to JF and myself regarding the protocols call 16:29:56 q? 16:30:04 ack Ch 16:30:04 Chuck, you wanted to mention JF's efforts on protocols 16:30:14 We need to have scoring around what is a functionally required or not - as this could move score from 0 to 95. 16:30:31 Chuck: The value in the comments will help the chairs decide how to have a more broad conversation 16:30:37 ...Thank you Jeanne, and all commentors 16:30:41 "Any single "critical error" results in a score of "very poor" for that outcome and also results in an inability to reach bronze level as an overall score. This seems unreasonable for large-scale websites and applications and negates all of the work that may have been done to meet the outcome." (IBM - https://github.com/w3c/silver/issues/477) 16:30:47 ack AWK 16:30:47 AWK, you wanted to say that the percentage should be whatever it is, and if there is a critical error it fails. Gives better information to teams doing fixes. 16:30:56 Thanks for the comments. :) 16:30:59 People today don't agree on what is a functional image and what would actually cause a critical error or not. 16:31:01 Chuck: We are moving on to Alastair G 16:31:06 https://docs.google.com/document/d/1IVCPcfyfnjm2RJRvgV5pbcQLwzxXKHw66V7R-OW3wiE/edit 16:31:11 ...He has a proposal specific to measuring alt text 16:31:36 Agarrison: I will run through the information 16:31:39 Counting images is a challenge as we don't have a consistent mechanism to determine what are images - svgs, canvas, role img, img, poster images, video, etc. 16:32:18 Agarrison: (displaying the Measuring Alt Text Quality document) 16:32:27 ...I put together a short paper in response to the call out a few weeks ago 16:32:30 +1 Jon - on a personal level I think counting is a rabbit hole that we should try to avoid 16:32:35 ...I will read through it 16:32:36 david-macdonald has joined #ag 16:32:40 ...(reads through the document) 16:32:42 present+ 16:33:09 ...We have just heard that color contrast will not be achieved 16:33:29 ...People used to think flying machines would not be possible, but this was achieved in a few years from the statement 16:33:43 ...I always try to keep a question mark as to what capabilities will be available 16:34:00 ...Measuring alt text is not a 1 size fits all approach 16:34:15 ...Images need to be categorized 16:34:25 ...I have split the W3C decision tree 16:34:52 ...Images of text, complex images, informative images, decorative images (and a few others he read) 16:35:08 ...Machine learning - categorization confidence 16:35:36 ...Functional images can have image recognition, optical character recognition (continues reading from document) 16:36:06 ...Informative images showing images: (reads from document) 16:36:22 ...Decorative - I do not have any. Just like the W3C decision tree, this is a catch all mechanism 16:36:26 ...These are just suggestions 16:36:32 ...There will be others used over time 16:36:42 ...The process 16:36:54 ...Needs to be done in a sequence - use a discrimination tree 16:37:01 ...then you stop using the rest of the decision tree 16:37:17 ...Look at each category in order 16:37:22 ...With decorative being looked at last 16:37:45 ...I do suggest that the W3C start to amalgamate more 16:37:53 ...If there are central data sets - 16:37:56 note that the WHATWG HTML spec now also includes a concept of an "ancillary image": https://html.spec.whatwg.org/multipage/images.html#ancillary-images 16:38:00 ...Training against the same dataset 16:38:14 ...Then others may also throw their images into that dataset 16:38:18 ...This could reduce bias 16:38:29 ...Looking at functional images 16:38:37 ...You ask the W3C to collect thousands of images 16:38:50 Jemma has joined #ag 16:39:04 ...You can group these images in a big dataset with labels 16:39:17 ...using a standardized label for all images that represent a printer 16:39:22 present+ 16:39:29 ...You do this because if you have a standardized set of labels 16:39:32 Q+ to ask about context 16:39:46 ...You will be able to easily decide if they have an appropriate alt text 16:40:02 ...Characterization would determine if they are functional and what the associated label should be 16:40:13 ...Informative images showing a single famous object 16:40:18 agenda? 16:40:22 ...You could thousands of images for these 16:40:26 ...like a Google search 16:40:29 q+ to say the alt text should resemble the semantics, not the visual, e.g. a search button vs a magnifier icon 16:40:37 ...If using a picture of the Mona Lisa 16:40:53 ...(2nd paragraph) 16:41:27 ...You determine if this is an image of the famous image or not 16:41:37 ...Then you assess if the text alternative is representative 16:41:41 ...Complex images 16:41:48 ...W3C collect thousands of images 16:42:02 ...These are not just for machines, but could train an army of humans to do the same job 16:42:16 ...the categorization would be to determine if it is a chart or graph 16:42:22 ...Is the data correctly represented 16:42:36 ...This is a Draconion move, but it makes it much more automatically testable 16:42:50 @shadi Thx 16:42:51 ...If it is linked to a data table, that is half of a good test 16:43:04 ...There is a whole lot of work being done on data extraction from charts 16:43:11 ...In the future you would be able to automate this 16:43:21 ...For images of text, each requires a different mechanism 16:43:36 ...All complex images containing text should already be removed 16:43:57 ...(reads from the doc the W3C decision tree quote) 16:44:08 ...There are two types of text detection 16:44:20 ...Both work in a different way 16:44:36 ...EAST is for text not presented in a typical manner 16:44:59 ...EAST is designed to pull out text from billboards, or text on a book in the image 16:45:11 ...Optical Character Recognition is just for typical text to be extracted 16:45:33 ...If you run both against images you are able to tell the text within the image in both the typical format and the atypical format 16:46:13 ...We are only looking for typical text 16:46:27 Fazio has joined #ag 16:46:32 ...This van has lots of words written all over it 16:46:35 ...This is not a text image 16:46:46 ...Using these two methods we can isolate which to categorize as a text image 16:46:53 ...Informative images of objects 16:47:00 ...W3C should find general objects 16:47:12 ...There are existing datasets for this 16:47:30 ...This area is where a metric called SPICE comes in 16:47:38 ...Tests how good the generation of alt text is 16:47:51 ... I have reformulated this for informative images 16:47:56 ...(reads from the document) 16:48:09 From the document: "If a context specific alt text description is provided it becomes useless when viewed out of context; however if a non-context specific alt text description is provided it remains equally useful in both contexts." I challenge that assertion 16:48:19 ...Wilco asked me some questions about context and other pieces 16:48:24 ...In terms of context 16:48:37 ...The context the image sits within I think should be not considered 16:48:52 ...Article it sits within is the intended context 16:49:01 laura has joined #ag 16:49:01 ...When the image is searched is the unintended context 16:49:20 ...Alt text that works in both contexts would be helpful 16:49:26 ...(reads from the document) 16:50:05 ...(reads information related to image of 2 dogs running after a ball) 16:50:23 ...The other question was why not include adjectives or names? 16:50:32 ...They don't form the backbone of the scene 16:50:45 ...The big picture summarization is where? What objects? What are they doing? 16:51:22 ...Looking at the dogs - if you called people on the phone and asked them to draw this photo from the alt text 16:51:23 ...they could 16:51:28 ...They can make inferences 16:51:42 ...If instead the description focuses on names, like Bob and Jack 16:51:57 ...This provides a different image for the person hearing that description 16:52:18 ...More adjectives would provide some aspects of the images, but not others 16:52:43 ...Categorization of such an image: does it contain recognizable objects? 16:52:52 ...You try to analyze the relationship between the objects 16:52:58 ...You then label them 16:53:05 ...example dog 1, dog 2 16:53:12 ...Then you have a ball 16:53:23 ...(reads from document) 16:53:39 ...You can then formulate what you expect your alt text to have 16:53:46 ...(reads from document) 16:53:50 ...You can then measure your alt text 16:54:13 ...Look at the list we generated - we can determine which pieces of the alt text existed in our list 16:54:26 ...It is missing a number of things we said should be included 16:54:35 ...It is missing 4 vital pieces of information 16:54:47 ...So the alt score can be measured 16:55:06 ...Once you have gone through the list, and if you determine it is decorative 16:55:18 ...I have included a revamped version of the W3C's alt decision tree 16:55:26 ...into a simple decision tree format 16:55:31 ...You can run through this manually 16:55:39 ...to assess and measure your alternative text for an image 16:55:46 ...Caveat: this is not the only way to do this 16:55:52 q? 16:56:01 ack JF 16:56:01 JF, you wanted to ask about context 16:56:07 JF: Thank you for this Alastair 16:56:11 ...Lots of good thinking here 16:56:17 q+ to say this is an interesting jumping off point for evaluating quality of some of the more subjective content 16:56:19 ...I agree, machine learning will improve over time 16:56:27 ...I don't think we are near where we need to be today 16:56:32 ...for conformance measuring 16:56:40 ...Under complex images you reference a dataset of charts and graphs 16:56:48 ...Another type would be infographics 16:56:54 ...This is usually a large graphic file 16:57:01 ...This requires a long description 16:57:06 ...I am concerned about this 16:57:12 ...The context piece bothers me 16:57:35 q+ 16:58:02 q+ to change scribes 16:58:02 ...Specificity of age of shoes may be esssential in certain use cases - I don't think articial intelligence will be able to determine when to include this 16:58:29 ...In context the most important elements in other images can be that it is a selfie, not the object the person is in front of 16:58:47 ...Artificial intelligence will get us a long way, but I think that context will be an issue 16:59:05 ...I am also concerned about the datasets - who will compile them? Host them? It is a lot to ask the W3C to do 16:59:18 Agarrison: this is designed as a manual process that is meant to be machine learned 16:59:42 ...I agree that infographics is not included in the complex graphics - we could include that somewhere along the line 16:59:58 ...For the selfie example: this would be under the secondary informative image 17:00:07 ...This would be the focus of the alt text 17:00:15 ack Ch 17:00:15 Chuck, you wanted to change scribes 17:01:07 zakim, pick a victim 17:01:07 Not knowing who is chairing or who scribed recently, I propose ! 17:01:08 Azlan has joined #ag 17:01:22 zakim, pick a victim 17:01:22 Not knowing who is chairing or who scribed recently, I propose MarcJohlic 17:01:42 I can try never done before 17:01:57 scribe Regina 17:01:59 scribe: Regina 17:02:04 Scribe cheat sheet https://www.w3.org/WAI/GL/wiki/Scribing_Commands_and_Related_Info 17:02:25 jaunita_george has joined #ag 17:02:27 +1 17:02:30 present+ 17:02:34 Present+ 17:02:44 q+ to ask about text alternatives that serve equivalent purpose versus grading alt text 17:02:45 Jonh Eiffell towel primary focus in the image 17:02:50 Sorry, I have to drop 17:02:53 q- 17:03:07 ack Rach 17:03:07 Rachael, you wanted to say this is an interesting jumping off point for evaluating quality of some of the more subjective content 17:03:08 ... it's not the primary meaning in the screen 17:03:20 Great work, Alistair! 17:03:23 s/Jonh Eiffell towel /John: Eiffell tower 17:04:00 q? 17:04:04 Rachel sugg content recognizing the value 17:04:08 ack kirkwood 17:04:09 +1 to Rachel 17:04:10 +1 to Rachael, very helpful write-up! 17:04:26 s/+1 to Rachel/+1 to Rachael 17:04:33 bbailey great example 17:04:45 +1 to John K 17:04:47 ... that would be the most important thing 17:04:55 s/Rachel sugg/Rachael: sugg 17:05:08 ...context be careful on the idea and subjectivity 17:05:10 q? 17:05:15 s/bbailey great /kirkwood great 17:05:22 ack bbai 17:05:22 bbailey, you wanted to ask about text alternatives that serve equivalent purpose versus grading alt text 17:05:34 q+ 17:05:54 q+ to say that an SC on captioning important images may be warranted 17:07:02 alaistairc with many images impossible to add information 17:07:08 ack Wilco 17:07:13 this presentation was eye opening for me. thanks for great presentation, Aistair!! 17:07:14 but... if accuracy of alt text is only 80%, what is the impact of that on persons with COGA issues? 17:07:33 Wilco looks solutions in user agents 17:07:49 ... potential of some development and testing 17:08:08 ...implement new technologies 17:08:35 +1 to JF. I was thinking about how to consider the importance of weighting the scoring to describe relationships of elements rather than just the specific elements. 17:08:46 s/eye opening/giving me alternative perspective to think about alt text I never imanged/ 17:08:46 alastairc not necessary testing to hundred of images 17:08:48 ack mb 17:08:48 mbgower, you wanted to say that an SC on captioning important images may be warranted 17:09:23 mbgower required of captions programatically 17:09:35 ...providing ALT text automatically 17:09:42 ... provide captions to images 17:09:44 zakim, take up next item 17:09:44 agendum 2 -- Review Writing Testable WCAG 3.0 Outcomes Survey -- taken up [from Chuck] 17:09:59 https://www.w3.org/2002/09/wbs/35422/testable-outcomes-2021-12-2/results 17:10:55 chuck describing the agenda and survey results 17:11:17 ... Mary longer agree statements regarding editorial changes 17:11:38 wilco some putuation suggestions 17:11:45 q+ 17:12:08 chuck agree in some of the comments 17:12:26 ...pages to be tested 17:12:31 ... just a sample 17:12:49 ...become more complicated 17:13:33 q? 17:13:40 chuck reading comments from survey 17:13:42 ack Wilco 17:14:29 wilco add a list of standards of terms 17:14:39 proposed RESOLUTION: AGWG approves amended Writing Testable WCAG 3.0 Outcomes for internal use 17:14:59 +1 17:15:01 I agree with Chuck's approach 17:15:14 chuck proposing the resolution 17:15:18 +1 17:15:19 +1 17:15:19 +1 17:15:20 +1 17:15:21 +1 17:15:23 +1 17:15:23 +1 17:15:25 +1 17:15:26 +1 17:15:44 +1 17:16:06 not sure where to find it 17:16:15 proposed RESOLUTION: AGWG approves amended Writing Testable WCAG 3.0 Outcomes for internal use 17:16:35 RESOLUTION: AGWG approves amended Writing Testable WCAG 3.0 Outcomes for internal use 17:16:42 zakim, take up next item 17:16:42 agendum 3 -- ACT New Rules (30 min) https://www.w3.org/2002/09/wbs/35422/act_nov_10/ -- taken up [from Chuck] 17:17:12 https://www.w3.org/2002/09/wbs/35422/act_nov_10/results 17:17:19 TOPIC: Question 1 - Form field has non-empty accessible name 17:17:26 Chuck has changed the topic to: Question 1 - Form field has non-empty accessible name 17:18:00 chuck reading questions Form field has non-empty accessible name 17:18:26 ... 7 approved, 2 with comments, 1 not approve 17:18:53 ...reading Oliver Comment from documents 17:19:29 ... reading Gundula Nieman's comment about not backdoors rules 17:19:53 q? 17:20:12 chuck reading Wilco comments 17:20:32 q+ 17:20:43 ack th 17:21:19 thbrunet something is disable it will be a fail when shows 17:21:56 proposed RESOLUTION: Accept publishing "Form field has non-empty accessible name" 17:22:06 +1 17:22:08 +1 17:22:09 +1 17:22:10 +1 17:22:10 +1 17:22:11 +1 17:22:14 +1 17:22:15 +1 17:22:20 +1 17:22:20 +1 17:22:20 +1 17:22:22 +1 17:22:23 +1 17:22:29 +1 17:22:30 +1 17:22:33 proposed RESOLUTION: Accept publishing "Form field has non-empty accessible name" 17:22:34 +1 17:22:43 RESOLUTION: Accept publishing "Form field has non-empty accessible name" 17:22:44 +1 17:22:57 TOPIC: Question 2 - Attribute has valid value 17:23:04 Chuck has changed the topic to: Question 2 - Attribute has valid value 17:23:20 chuck attribute has valid value 17:23:22 Q+ 17:23:28 ...7 people agree 17:23:47 s/chuck attribute has valid value/chuck: attribute has valid value 17:23:51 ...Wilco responding to Rochelle 17:24:10 q+ 17:24:27 ...Oliver said samples will fail 17:24:34 ack JF 17:25:07 JF question about autocomplete 17:25:20 stevelee has joined #ag 17:25:23 ack Wil 17:25:33 ...modify this rule to include the attribute 17:25:55 wilco I don't think we are going to use it 17:26:09 ...About Rochelle comment 17:26:35 ...we are not doing it anymore it's not applicable 17:26:48 q? 17:26:54 proposed RESOLUTION: Accept "Attribute has valid value" 17:26:56 ...rule is the same 17:26:56 Fair enough, as stated, I will not object to the exisiting langauge 17:27:13 ...it's not failure 17:27:28 +1 17:27:30 +1 17:27:30 +1 17:27:30 +1 17:27:31 +1 17:27:32 +1 17:27:34 q+ 17:27:34 +1 17:27:35 +1 17:27:36 +1 17:27:37 +1 17:27:40 +1 17:27:42 +1 17:27:43 +1 17:27:46 +0 17:27:48 +1 17:27:54 RESOLUTION: Accept "Attribute has valid value" 17:27:56 q? 17:28:02 ack jon 17:28:05 +1 17:28:39 jon_avila it's not a field requiere use to autocomplete 17:28:59 Q+ 17:28:59 q+ 17:29:05 ack JF 17:29:14 ...because the whole is predictable 17:29:18 +1 to Jon - he's right 17:29:23 JF values do somehting 17:29:40 ... if you put the autocomplete value it will autofill 17:29:55 q+ Jon's right on this 17:30:01 q+ to say Jon's right on this 17:30:02 ...wrong value autofill the wrong information 17:30:12 ack Wilco 17:30:27 wilco first assumption 17:30:38 q- 17:30:49 ...if autocomplete color 17:31:03 + to ask if there is a companion rule for misuse? 17:31:16 Q+ 17:31:19 q+ to ask if JA objects to the rule? 17:31:23 ...role attribute is used 17:31:23 ack JF 17:31:41 q+ to ask if that can result in false fails? 17:31:50 I don't think that would be a fail 17:32:04 JF a lot of rules in place 17:32:09 ack Chuck 17:32:09 Chuck, you wanted to ask if JA objects to the rule? 17:32:11 https://github.com/act-rules/act-rules.github.io/issues 17:32:19 q- 17:32:27 chuck asking objecting to the rule? 17:32:36 q+ to ask if this rule is fully automated? 17:32:44 proposed RESOLUTION: Accept "Attribute has valid value" 17:32:52 ack AWK 17:32:52 AWK, you wanted to ask if this rule is fully automated? 17:33:06 awk automate rule or manual review? 17:33:16 wilco this is fully automated 17:33:31 awk about the user 17:33:41 q+ 17:33:47 wilco this make more difficult automate it 17:34:32 awk there is extra cases would represent problems when filling a form 17:34:41 ... for autocomplete values 17:34:56 it's also an author failure 17:35:02 q+ 17:35:02 q? 17:35:05 ack Chuck 17:35:08 ...it's a usability issue not a failure but a discovered thing 17:35:16 chuck still provide value 17:35:24 q+ 17:35:31 ... provide meaningful information 17:35:34 ack Jon 17:35:59 Jon create a false positive 17:36:06 +1, it could bring up false-fails without scoping to the user-info. 17:36:36 proposed RESOLUTION: Accept "Attribute has valid value" 17:36:38 q? 17:36:39 chuck some hesitation with this rule 17:36:41 ack Wil 17:37:04 +1 17:37:11 wilco every rule has tested 17:37:25 ...bu looking people reporting false positives 17:37:38 ...we consider not a big deal 17:37:47 ...false positive are reported 17:37:51 q? 17:38:09 proposed RESOLUTION: Accept "Attribute has valid value" 17:38:16 +0 17:38:19 chuck interesting conversation to review 17:38:20 +1 17:38:22 +1 It is informative content so I believe we can update if needed 17:38:22 +0 17:38:24 +1 17:38:29 + 17:38:31 +1 17:38:31 @Wilco - issue #1768 17:38:34 +.5 17:38:36 +1 17:38:36 +.5 17:38:38 +1, but would like to know where to report false positive cases... 17:38:40 +1 17:38:49 +.5 17:39:01 RESOLUTION: Accept "Attribute has valid value" 17:39:02 +.5 17:39:10 q+ 17:39:12 @awk, you can report them to ACT-R, or to any of the implementors if you're using any tool / methodology using ACT. 17:39:17 ack Ra 17:39:20 TOPIC: Question 3 - Element marked as decorative is not exposed 17:39:25 https://github.com/act-rules/act-rules.github.io/issues 17:39:27 Chuck has changed the topic to: Question 3 - Element marked as decorative is not exposed 17:39:48 chuck third question 17:40:00 ... 6 people approved 17:40:51 q? 17:40:52 ... reading comments about image and attributes 17:40:56 q+ 17:41:16 q+ 17:41:17 ack AWK 17:42:09 awk concerns about about image presentation 17:42:14 q? 17:42:17 ack wilco 17:42:25 wilco you can fail this 17:42:35 ...elements can have role attributes 17:42:46 ...nad have it not being applied 17:43:13 ...there are scenarios where it could be ignored 17:43:24 q? 17:43:36 q+ 17:43:40 ... could have role none and be ignored and considerated a failure 17:43:59 q- 17:44:13 ...this rule may fail in some scenarios 17:44:18 proposed RESOLUTION: Accept amended "Element marked as decorative is not exposed" 17:44:28 +1 17:44:32 +1 17:44:35 +1 17:44:38 +1 17:44:39 +1 17:44:41 +1 17:44:42 +1 17:44:43 +1 17:44:45 +0 17:44:49 +1 17:44:49 +1 17:45:24 awk there is not conflict putting in a row 17:45:54 chuck Andrew are you objecting? 17:46:17 AWK this rule about element decorative in some way but not being exposed, 17:46:23 +1, some of those fails are indicative of some nouanced accessibility tree points, not bothered by the obvious passes. 17:46:41 ...things marked decorative are exposed 17:46:55 img[alt=""] is listed as role 'img' by Chrome. Pass 4 indicates it's 'none'. Is Chrome wrong? 17:46:55 Q+ 17:47:05 ack JF 17:47:08 wilco aria label and ALT empty 17:47:34 q+ 17:47:57 JF about the relationship between attributes aria label and ALT 17:48:07 ack thbrunet 17:48:27 thbrunet in chrome images 17:48:30 s/JF about the relationship between attributes aria label and ALT/JF: about the relationship between attributes aria label and ALT 17:48:42 https://www.w3.org/TR/html-aria/#el-img-empty-alt 17:48:51 wilco it's about html 17:49:09 ... how html is done 17:49:23 proposed RESOLUTION: Accept amended "Element marked as decorative is not exposed" 17:49:34 RESOLUTION: Accept amended "Element marked as decorative is not exposed" 17:49:44 TOPIC: Question 4 - Letter spacing in style attributes is not important 17:49:50 Chuck has changed the topic to: Question 4 - Letter spacing in style attributes is not important 17:50:08 chuck reading from document 17:50:13 ...5 people agreed 17:50:20 proposed RESOLUTION: Accept "Letter spacing in style attributes is not important" 17:50:28 +1 17:50:29 +1 17:50:32 +1 17:50:33 +1 17:50:34 +1 17:50:37 +1 17:50:39 +1 17:50:39 +1 17:50:44 +1 17:50:47 +1 17:50:57 RESOLUTION: Accept "Letter spacing in style attributes is not important" 17:51:16 TOPIC: Question 5 - Word spacing in style attributes is not important 17:51:23 Chuck has changed the topic to: Question 5 - Word spacing in style attributes is not important 17:51:36 chuck no objections 17:51:39 proposed RESOLUTION: Accept "Word spacing in style attributes is not important" 17:51:41 +1 17:51:42 +1 17:51:43 +1 17:51:45 +1 17:51:45 +1 17:51:47 +1 17:51:49 +1 17:51:52 +1 17:51:57 +! 17:51:58 +1 17:51:59 +1 17:51:59 +1 even 17:52:07 +1 17:52:14 RESOLUTION: Accept "Word spacing in style attributes is not important" 17:52:20 zakim, take up next item 17:52:20 agendum 4 -- Focus appearance https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-enhanced2/ -- taken up [from Chuck] 17:52:41 TOPIC: Question 1 - Focus Appearance complexity #1842 17:52:47 Chuck has changed the topic to: Question 1 - Focus Appearance complexity #1842 17:52:49 q+ 17:52:57 ack ala 17:53:23 chuck going to questions 17:53:27 q+ 17:54:08 ack ala 17:54:44 TOPIC: Focus appearance & Visual examples #2071 17:55:02 https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-enhanced2/results#xq26 17:55:10 q? 17:56:04 proposed RESOLUTION: Accept amended response to address issue 2071 17:56:32 +1 17:56:34 +1 17:56:35 +1 17:56:36 +1 17:56:39 +1 17:56:42 +1 17:56:51 +1 17:56:54 +1 17:57:04 +1 17:57:49 Regina_ has joined #ag 17:58:40 sorry I was kick out of the site 17:59:19 bye all 17:59:23 thanks! 17:59:33 Bye all 17:59:36 rrsagent, make minutes 17:59:36 I have made the request to generate https://www.w3.org/2021/12/07-ag-minutes.html alastairc 17:59:45 /me thanks everyone for all the great discusison. 17:59:53 rrsagent, make minutes 17:59:53 I have made the request to generate https://www.w3.org/2021/12/07-ag-minutes.html Regina_ 18:00:06 ToddL has left #ag 18:00:12 rrsagent, make logs public 18:00:25 rrsagent, make minutes 18:00:25 I have made the request to generate https://www.w3.org/2021/12/07-ag-minutes.html alastairc