Meeting minutes
ACT rules page redesign
<hdv> Wider redesign project: https://github.com/w3c/wai-wcag-supporting-documents-redesign/wiki/Requirements-Analysis issues welcome here: https://github.com/w3c/wai-wcag-supporting-documents-redesign/issues
hidde: am working on supplemental guidance for wcag like techniques and understanding docs
… consistency of WAI resources
… to include ACT rules
… header, footer, links to supporting info shown
… comments welcome
… separate main content from meta info for users to find important info
trevor: is "Rule:" necessary? may be repetitive on all rules
… h1 tag after seems weird
… what is reading order of page?
hidde: about this page is last. it's marked as supplementary. a screen reader can jump to it if want to
trevor: it looks really nice
moe: who is audience? why develop a different presentation for ACT rules?
hidde: redesigning understanding and techniques to WAI and wcag for consistent look
wilco: share link in IRC and ask for feedback from mailing list and how to provide commments
Results of CFC on updates to the ACT rule process
wilco: CFC this week about updating the rule process. 4 approvals, no objections
… accepted, merge PR
Form control has non-empty accessible name: https://www.w3.org/2002/09/wbs/93339/ACTFormControl/results
wilco: 6 responses
… Assumptions, I don't know from Detlev
trevor: concerned about the disclaimer, but it's a common disclaimer
wilco: noted, move on
… kathy asked why button isn't included in rule. maybe had a button rule already and then wrote this one.
maryjo: also menuitem. maybe this rule is focused on input
kathy: maybe add an explanation why button has a separate rule since they both check for non-empty accname
charu: change this rules name for input or select
… instead of "form controls" and then explain why buttons and menuitem not included
wilco: "form fields" better?
<MoeKraft> I have to drop but nice hearing everyone on the call.
wilco: reasonable to split up input fields, select fields, buttons to separate rules
… substantial change requiring this rule to be deprecated
maryjo: is that necessary?
wilco: this rule covers input and select. why not 2 separate rules? hesitation is aria 1.2 may change
… can we provide this feedback and approve this rule?
… deprecate later if necessary
… 6 approvals, can go to CFC
Object element has non-empty accessible name: https://www.w3.org/2002/09/wbs/93339/ACTObjectName/results
wilco: 7 responses
… empty accname for decorative object would be appropriate in assumptions should be added
… implementation data charu's comment add other ways to provide accname
kathy: H53: Using the body of the object element (https://www.w3.org/WAI/WCAG21/Techniques/html/H53.html) to provide the text alternative.
wilco: that technique does not work in Chrome
… think H53 is wrong
… inconsistency in this rule and wcag
charu: H53 provides fallback if object doesn't load but doesn't provide accname
wilco: I will open an issue with wcag about H53
… Question 5 my comment - this rule maps to 1.1.1 assuming object is loading non-text content. loading an HTML page is not non-text content. think mapping is wrong
trevor: are you thinking of adding more requirements to the rule? depending on what the object holds
wilco: for video, this would map to 1.1.1. Other pages would be different
maryjo: how do screen readers handle objects with text alternative?
wilco: comment from moe to explain failures more. agree
… not ready to publish
… liaison - mary jo
ARIA required owned elements: https://www.w3.org/2002/09/wbs/93339/ACTRuleARIArequiredOwns/results
wilco: 5 responses
<Wilco> https://act-rules.github.io/rules/bc4a75#passed-example-4
trevor: invalid html
… aria-checked value needed
wilco: add attribute to fix
… explicit and implicit roles identical - ul/li example li in div
… liaison - trevor