Wilco: This came from the CG
<Wilco> https://github.com/act-rules/act-rules.github.io/issues/1531#issuecomment-760287519
Wilco: They had a conversation about how to better organize the "Background" section. A couple of suggestions that were discussed there.
... Proposal is that within the background there are two subsections, bibliography and related rules (if any).
Trevor: Fine with me.
Daniel: I like this approach
Shadi: We could even consider an editor draft of the rules format so that there is something to lean on
Wilco: I like that, there is a couple of other things I would include in that draft.
Shadi: An we could in these sections refer back to open issues.
MaryJom: Process question - Is it in our work scope to update the spec? Is it possible?
Shadi: Maybe starting a new branch or having clear reference will help clarify. Specifying that these are editorials mainly.
... When we've figured out we have enough then we could go back to the group
Wilco: Will communicate back to the CG that we like these changes. Shall I open up an issue about how we are going to create that draft?
Shadi: Let's take this ofline
Kathy: Not sure about the word "bibliography" Could be "Technical references"?
Wilco: WCAG Technique Technical Reference?
Trevor: At first they split it up into WCAG Techniques and Specs, and then they condensed using Bibliography
Levon: I like the conciseness
Wilco: Related resources? Other resources?
Daniel: I need we could specify under Background.
Wilco: What about other resources?
Kathy: OK.
Wilco: Should rules be above other resources?
RESOLUTION: Change "Bibliography" to "Other Resources" and flip the order of the headings
Wilco: This one is open until Feb 11, that is the week after
<Wilco> https://act-rules.github.io/rules/2ee8b8/changelog
Wilco: Only very minor editorial change.
... Only the magnifying glass change. I don't think the rest needs to be addressed. Does anythin need to happen here?
<trevor> https://www.w3.org/2002/09/wbs/93339/ACTVisibleLabel2/results
Wilco: We spent most of the time discussing the icon font (if that should be applicable), and the others should not be implemented, as there was a misunderstanding of "label from content"
Trevor: There might be some open issues about broadening the scope, but these can be addressed later on
... I don't think another survey is needed just for that change.
Wilco: Are we good to put it on CFC?
<trevor> +1
<kathyeng> +1
<maryjom> +1
<Levon> +1
<Wilco> +1
<Daniel> +1
Wilco: Put it on CFC
Trevor: Can we open another survey? For the following two weeks we have just one.
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/1534/files
Wilco: The "autocomplete has valid value" has come back. Not substantially, but it has changed.
... I would prefer this to go into CFC as well.
... Two open issues
... Rule fails autocomplete="off", which should not.
... Second, there are some exceptions to the rule
... I take this back, I think this is not ready for survey
... The exceptions I'm suggesting are around input type="tel". Devs use this for pretty much anything which is a number
... since in some mobile platforms this opens up the number keypad
... and this is not allowed in the spec
Trevor: Maybe we should label this in the accessibility support section
... I agree with autocomplete="|"off" one, have to think about the other
Daniel: Maybe just the first one.
Wilco: I am leaning to ask for both to be solved.
RESOLUTION: Put the visible label rule into CFC and close survey
... Not open a survey on the autocomplete rule and ask the CG to resolve the open issues first
MaryJom: New one unassigned about the headers attribute
Wilco: Levon to take this one, edit made in table
MaryJom: Could we have resolution in wiki so that they are visible and easier to identify if they've actually been taken care of?
Wilco: Somebody will remember to do it. Do we want to live edit this table?
MaryJom: Could we move this to a spreadsheet?
Wilco: Good suggestions, will make things a lot easier
RESOLUTION: Try to move tracking table to spreadsheet
Wilco: We will start tracking implementations of the ACT-rules. I think it is time for us to start working on these. Are we all clear on what an implementation is and what it means?
... Based on the test cases you can figure out if the tool or methodology is consistent with the rule
... Passes should never fail, and fails should never pass
<Wilco> https://act-rules.github.io/pages/implementations/overview/
Wilco: The CG has been doing this for a while now
<Wilco> https://act-rules.github.io/implementation/rgaa-3.0
Wilco: In the third column of this example they list their prodecude, how they get to the outcomes they are showing in the other columns.
... The CG has been using these data to figure out if the rule is ready for publishing
... The ideas of having an implementation tracker is we want orgs to use ACT-Rules
... What are possible use cases?
Shadi: all good. This is going to be more of a technical idea how we want to implement this.
... For the end users, that they can rely on rules and methodologies to be more consistent. What do they really implement, specific test cases that they do and do not cover
... Try to get rules and methodologies to address more and more the gaps and trying to be more and more consistent. One system could do things manually, another system could have more automated support, another ones may have heuristics or AI to complement testing
Trevor: Is this intended as a consumer resource? How these metrics apply? How do you summarize for user not to get into the very detailed report?
... I see some designers saying "We use this component a lot", so let's make sure this component actually passes.
Shadi: This framework was picked by ARIA-AT
... We tried to build and accessibility support database.
... We had the test cases and the SCs, and we listed how many were met
... For our example these could be the test rules
... Our implementation doesn't need to look like this specific example, but maybe we can take some ideas from it
... Actually trying to add more value to the figures themselves
<shadi> https://www.w3.org/WAI/accessibility-support/
<maryjom> https://docs.google.com/spreadsheets/d/1pOZxRBd5sJTZtvz02jgbO53JaCgmJTOFgb9uzCHDd1o/edit?usp=sharing