<shadi> https://github.com/w3c/wcag-act/issues/446
shadi: this is building on 353 issue, we had suggested 5 points
... a new page for each rule, a page listing all rules,
... first rule HTML page title example - we already have a template, rules on ACT Overview page. when more rules they will have their own page
... wcag page are being redesigned, all techniques and understanding will look different
... add Understanding ACT Rules for wcag sc, that matches Understanding Techniques
... H25 and F25 would like to HTML Page has title ACT rule
trevor: this is sensible
charu: 3 understanding documents
wilco: should we call these ACT Rules or just Rules?
maryjo: generic test rules?
wilco: does it matter that these are ACT rules for general visitor
shadi: would help propogate ACT brand
... and require that they rules go through ACT rigor
trevor: if they don't have ACT, people may wonder where they came from
shadi: point 3 ACT Rules - text is from existing paragraph that describes techniques and links to Understanding techniques. ACT would also link to an explanation of ACT Rules.
... page to be written
wilco: slight preference for not having ACT in heading and in understanding doc. There won't be other rules
<maryjom> +1
<trevor> +1
wilco: vote +1 keep "ACT", -1 take "ACT" out
+1
<shadi> +/- 0
maryjo: Rules repository is called ACT, keep nomenclature
<cpandhi> 0
wilco: vote tally is to keep "ACT"
wilco: because this isn't a wcag rule, don't spend too much time. 5 responses received but only 4 answers to last question ready to publish
... can be published as is
... closes in a few hours
... I will process results
charu: what does it map to?
trevor: specified in rule
<Wilco> https://www.w3.org/2002/09/wbs/93339/RuleImageFilename/results
wilco: 6 responses
... from me, assumption confusing
... from kathy, assumption language of page?
... if a text alternative is in a different language from the page, then it's not sufficient. if the alternative text is in a diff lang, then lang of parts 3.1.2, not 1.1.1 here.
kathy: also "sufficiently understood" is unclear
wilco: this is a standard assumption in rules with language. if you don't know lang of page, a single image with a text alt is a word in english and a word in french, assumption is page language can always be determined
maryjo: why is page lang important for this test
wilco: it's an odd edge case
maryjo: if image is a pic of file and alternative text is the filename, it's the name of the file
... language may not be a factor
... use of filename as alt text is usually not sufficient
charu: I had the same issue
wilco: applicability is to go check whenever the filename is the text alternative
maryjo: it wasn't clear this rule was to cover an edge case
charu: it is being used on cnn.com but rarely is it ok
wilco: how to make it clearer? sounds like description wasn't clear enough
charu: F30 is a failure of this rule in background
wilco: this rule is passing that the filename if descriptive under Expectation
<Wilco> https://act-rules.github.io/rules/9eb3f6#expectation
charu: does rule format indicate when manual testing/judgment call is needed?
wilco: no nothing explicit that testing has to be manual
... machine learning may be possible
... charu can you come up with a suggested solution to clarify concerns?
charu: will try
trevor: "sufficiently understood" is unclear
wilco: trevor please add this to your comments
... kathy comment for additional failure example
... agree add this example where filename is not adequate description
... filename comment from kathy
... filename doesn't require extension but almost always includes it
... should we send this back to community group?
... this is not accepted, open an issue with feedback assigned to Trevor
shadi: don't open an issue per comment, they are all in one issue?
wilco: correct
<Wilco> https://github.com/w3c/wcag-act/blob/master/wcag-ruleset-review-process.md