<scribe> scribe: kathy
wilco: CFC last Friday, got one
+1 and no objections
... No issues, accepted.
RESOLUTION: Accept Audio element content has text alternative
wilco: second CFC last week, one +1 and no objections
RESOLUTION: Accept Element with aria-hidden has no content in sequential focus navigation
wilco: meta viewport allows for
zoom has been merged, fairly minor change
... propose a CFC
RESOLUTION: Move "Meta viewport allows for zoom" to CFC
helen: object element and iframe need updates
trevor: role attribute - jean yves has a separate PR with suggestions
wilco: should CG have more time?
trevor: sure
chris: HTML graphics - PR should be ready to approve
wilco: 3 surveys open. Hoping to
do more surveys. If 3 is too much, let us know.
... due before next week's meeting
<Wilco> https://github.com/w3c/wcag-act-rules/pull/120
wilco: this PR moves 3 rules from
proposed to approved
... and updates approved rules
<Wilco> https://deploy-preview-120--wai-wcag-act-rules.netlify.app/standards-guidelines/act/rules/73f2c2/
wilco: able to show a version
history. Rule Versions heading replaces change log. Added each
version (proposed, latest, and previous)
... Implementations are only shown on approved and proposed
rule (not older versions).
wilco: showing diff
... from "compare" link
trevor: why always show the proposed version?
wilco: can only show proposed
version if there is a change
... can hide proposed one
trevor: I would've thought the
proposed would show updates
... are implementations only showing if latest version is
implemented? would it be good to add a column for older
versions?
wilco: have to figure out how to do that. Implementation table is relevant only to the page (version) its on
<ChrisLoiselle> On Rule Versions bulleted items - for the third bullet, do we want to have the wording of historical or deprecated prior to the date? Similar to bullet 1 and 2 Proposed and Latest?
kathy: change link to Proposed Updates if date is later than Latest version
wilco: I can make that work
... Implementation tables are now dynamically generated
... added Type col, and implementation's version number
chris: add previous version and then dates for other versions
wilco: I will make the change
<scribe> ... new content going live tomorrow
kathy: open in a new tab was not working for me
wilco: might be a version
thing
... latest and proposed open in a new tab
... this will get fixed tomorrow
... will take a look
wilco: #1873 adding reviewers
helen, kathy, wilco
... skipping aria work
... will close #1858 based on chris and wilco conversation.
change not necessary.
wilco: want to intro this, but
wait for Daniel for details
... implementation tables - 5 active implementers, 2 working to
get their data in
... major development, want visibility for this work
... w3c can tweet, announce on news page
... will write a blog post
... Daniel wants to wait on announcement until "coming soon"
implementations are added
... when can we remove "under development" banner
kathy: agree to wait for the coming soon data if it is coming soon
wilco: yes, they are expected
soon
... want to review rules that don't map to wcag
... Type column data: wcag and non-wcag rules
trevor: ok with releasing even with small changes needed
wilco: agree
... suggest talking with your marketing dept to help
promote
<Wilco> https://wai-wcag-act-rules.netlify.app/standards-guidelines/act/implementations/
trevor: Issue #1836 state
transition definition and examples
... questions in bullets under examples
... is this format helpful for our discussion?
wilco: change in definition of
focusable - something isn't focusable if it redirects focus
within a second
... also, what if we had definitions that we know are
subjective and allowed in applicability
trevor: how to constrain the language in the rule to more programmatic is the challenge
chris: would loading icon be an example
trevor: search example - yes if
loading icon shows while results are found provide the status
message. Transition is a state.
... how to tell people to test the transitions between
states