<scribe> scribe: ChrisLoiselle
Trevor: Reviews rule check sheet, talks to Iframe.
Helen: Waiting on Wilco to review.
Trevor: You can add me to the
list of reviewers.
... HTML page title , CfC?
Daniel: Not yet, either Wilco or Kathy next week.
Trevor: Two from Will, we will
review later.
... Two pull requests for Text content that change
automatically. Asks for reviews from others .
Heading is descriptive, Todd is not present , will skip
Tom , text has min contrast?
Tom: Working on it , will update.
Chris: Talks to open action items on Orientation, will follow up next week
<dmontalvo> https://github.com/act-rules/act-rules.github.io/pulls/
Trevor: Reviews PRs , first one is 1959, on applicability of rule. Asks for reviewers.
Helen: You can add me.
Trevor: On 1958, meta refresh,
there are enough reviewers, will monitor
... On 1956, css restrict orientation, adding Helen as reviewer
and Trevor and Tom
... On 1955, I will review image accessible name
descriptive.
Helen: Talks to her comment on issue regarding updates on 1955
Trevor: On 1950, Update on ACT rules to use WAI ARIA 1.2 , Wilco was to make changes. Tom made suggestions .
On 1945, add consistency , there has been one approval, but would like more reviewers.
Daniel: I think we convinced not to use italics .
Trevor: On 1935 , that was
separate from the apostrophe editorial change
... On call review, not sure it is necessary, but we can
possibly merge.
Helen: On editorial, we may not need the full time.
Trevor: On 1926, updating heading is descriptive , there are some changes requested. Todd has additional action items to pursue.
On 1925, one item exception, approved, should be ready to go.
On 1916, Helen is listed as reviewer .
On 1855, actioning feedback from Survey
Helen: Jean Yves is driving the technical side of this at moment.
Trevor: Any other pull requests?
<dmontalvo> https://github.com/act-rules/act-rules.github.io/issues?q=is%3Aissue+is%3Aopen+label%3APriority
Trevor: Talks to priority issues, currently 5 open per tracker. Nobody present on call is actively working on these items.
<trevor> https://github.com/act-rules/act-rules.github.io/labels/Priority
Thanks!
Trevor: There are priority issues, please take a look at these if you can and have time.
Will: Talks to pull request he was working on , thanks Trevor
Trevor: Opens this to Daniel or Helen
Daniel: Talks to semi automated testing tools and automated test rules. Now is the time for manual testing rules to be written. Talks to WCAG 3 and manual aspects of testing.
Helen: The rules that we write will be integrated into WCAG 3. It would be good for people who are not technical could contribute this way. Perhaps a subgroup would be used. We won't use code snippets, but more test processes .
Talks to 2.4.3 Focus order , lots of nuances and subjective , part of difficulty and variations . Would be a great way to shape WCAG future.
Third party interest is there.
There is a lot of work to be done, about one third have an automated rule associated to it.
Daniel: Would like to contribute.
Will: I reached out to you.
... I would be interested in this
<Helen> https://github.com/act-rules/act-rules.github.io/issues/1952
Helen shares the issue , 1952 , to track this effort
Chris: Happy to contribute as time permits
Trevor: Talks to issue 1953, applicability for stateful rules. Talks to issue and act rules format input aspects
also talks to common input aspects
<trevor> https://github.com/act-rules/act-rules.github.io/issues/1953
<trevor> https://www.w3.org/TR/act-rules-format/#input-aspects
<trevor> https://www.w3.org/TR/act-rules-aspects/
Trevor: I think it is a pretty good fit for include states in rules. It simplifies . Talks to comments made on issue , We included states and transitions as a sub-section of the DOM input aspect
Talks to organizing and referring to states and that they reference to, access to the link by the DOM , then focus
Trevor: How does that feel?
Helen: A bit technical .
Tom B: Usually real world examples expose wording updates that are needed .
Helen: Are you talking to on page load, etc. ? Notification messages made and focus of next page.
Trevor: I thought of forms and
error notifications.
... I think pointing out these here would allow us to reference
regarding the applicability. I.e. what does the tester think
vs. on us to get extremely technical on state.
Helen: It may help to talk to this on page load states vs. new page state. Different methods for similar type of interactions.
Trevor: Single Page Applications.
There may be issues with that as well.
Chris: Talks to partial page load, status updates, etc.
Trevor: Talks to his item 3 and 4 in his comments, we could cite them per ACT format and then other states where it is not clear, we can add glossary and refer to ACT repository .
Talks to including input aspects and states there, then referencing elsewhere.
Daniel: Talks to text no longer being relevant and needing to look at that as well.
Trevor: I believe we should have a slight modification of input aspects atomic rules, including state in dom tree , (4.5.1)
describing and nesting them and include examples in common input aspects note
Trevor: downsides that could be present , there may be a long list of elements in our examples . Transitions made need to be defined together, i.e. collapsed and expanded and the notion of transition .
Thanks, Daniel!