aria icon indicating copy to clipboard operation
aria copied to clipboard

clarifying existing live region announcement behavior on creation/rendering of new live regions

Open cookiecrook opened this issue 1 year ago • 6 comments

Closes #1216

Codifies existing UA behavior for live regions, especially in the context of creation and initial rendering, where only alert live regions are announced.

PR tracking

Check these when the relevant issue or PR has been made, OR after you have confirmed the related change is not necessary (add N/A). Leave unchecked if you are unsure. Read the Process Document or Test Overview for more information.

  • [x] Related Core AAM Issue/PR: N/A
  • [x] Related AccName Issue/PR: N/A
  • [x] Any other dependent changes? None

Test, Documentation and Implementation tracking

Once this PR and all related PRs have been been approved by the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.

  • [x] WPT Tests: Not yet testable.
  • [x] Does this need AT implementations? No.

Preview | Diff

cookiecrook avatar Jan 31 '24 23:01 cookiecrook

Check if PR introduces errant RFC-2119 Error: The added code should not contain must | must not | shall | shall not | should | should not | may

@pkra @spectranaut Can you help me understand the problem with this RFC-2119 change? Yes, it's a change, but it's not "errant."

cookiecrook avatar Feb 01 '24 00:02 cookiecrook

Check if PR introduces errant RFC-2119 Error: The added code should not contain must | must not | shall | shall not | should | should not | may

@pkra @spectranaut Can you help me understand the problem with this RFC-2119 change? Yes, it's a change, but it's not "errant."

The github action being used for this is not that smart.

This won't stop us from merging the PR.

cc @daniel-montalvo in case there are better options known on the W3C end.

pkra avatar Feb 01 '24 08:02 pkra

FWIW we could at least change the language of the message and replace "introduces errant" with "contains no".

From what I recall, GitHub Actions don't provide a warning-level, which might be more appropriate. Ideally, we could make it possible to manually dismiss the "failure" (like we can with IPR check).

pkra avatar Feb 01 '24 08:02 pkra

Discussed briefly during PR triage at today's meeting: https://www.w3.org/2024/02/01-aria-minutes.html#t02

spectranaut avatar Feb 01 '24 19:02 spectranaut