KEMBAR78
Add ARIA reflection tests for ariaBrailleLabel and ariaBrailleRoleDescription by nolanlawson · Pull Request #42751 · web-platform-tests/wpt · GitHub
Skip to content

Conversation

@nolanlawson
Copy link
Member

@nolanlawson nolanlawson commented Oct 25, 2023

Per w3c/aria#2039

Adds reflection tests for ariaBrailleLabel <-> aria-braillelabel and ariaBrailleRoleDescription <-> aria-brailleroledescription.

pkra pushed a commit to w3c/aria that referenced this pull request Jan 9, 2024
…ions (#2039)

This adds the following string reflections to ARIAMixin:

- `ariaBrailleLabel` -> `aria-braillelabel`
- `ariaBrailleRoleDescription` -> `aria-brailleroledescription`

These reflections are already implemented in Chromium (see [here](https://source.chromium.org/chromium/chromium/src/+/main:out/fuchsia-Debug/gen/third_party/blink/renderer/bindings/modules/v8/v8_element.cc;l=1201;drc=168fe20dbf8ab7e47e36db5e528ec3c95c2f8af0) and [here](https://source.chromium.org/chromium/chromium/src/+/main:out/fuchsia-Debug/gen/third_party/blink/renderer/bindings/modules/v8/v8_element.cc;l=1228;drc=168fe20dbf8ab7e47e36db5e528ec3c95c2f8af0)), but not yet in WebKit or Firefox.

The purpose of this PR is to align with the de-facto behavior of Chromium. I don't see a strong reason for the spec not to include these particular reflections. (If there is one, please let me know!)

See also: #923

# 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](https://github.com/w3c/aria/wiki/ARIA-WG-Process-Document/_edit) or
[Test Overview](https://github.com/w3c/aria/wiki/ARIA-Test-Overview) for more information.

* [x] Related Core AAM Issue/PR: does not apply
* [x] Related AccName Issue/PR:  does not apply
* [x] Related APG Issue/PR: does not apply
* [x] Any other dependent changes? no.

# Implementation tracking

* [x] "author MUST" tests:  does not apply
* [x] "user agent MUST" tests: web-platform-tests/wpt#42751
* [x] Browser implementations (link to issue or when done, link to commit):
   * WebKit: No (https://bugs.webkit.org/show_bug.cgi?id=263663)
   * Gecko: No (https://bugzilla.mozilla.org/show_bug.cgi?id=1861201)
   * Blink: [here](https://source.chromium.org/chromium/chromium/src/+/main:out/fuchsia-Debug/gen/third_party/blink/renderer/bindings/modules/v8/v8_element.cc;l=1201;drc=168fe20dbf8ab7e47e36db5e528ec3c95c2f8af0) and [here](https://source.chromium.org/chromium/chromium/src/+/main:out/fuchsia-Debug/gen/third_party/blink/renderer/bindings/modules/v8/v8_element.cc;l=1228;drc=168fe20dbf8ab7e47e36db5e528ec3c95c2f8af0)
* [x] Does this need AT implementations? no.
@foolip foolip merged commit 8a2932f into web-platform-tests:master Jan 11, 2024
@cookiecrook
Copy link
Contributor

cookiecrook commented Feb 2, 2024

@foolip @nolanlawson et al, please get some accessibility-focused reviewers to approve the aria-related tests. While these tests are needed, the change the Interop 2024 deltas unexpectedly, after the test list was agreed upon.

I would have liked to alert the accessibility engineering teams at each browser and get them to sign off on any Interop 2024 deltas. We still could have checked in the tests, but if there was doubt about which work would be done for 2024, we might have moved these to a different file not already tagged with interop-2024-accessibility.

Thanks.

@cookiecrook
Copy link
Contributor

Now wondering if I can add suggested reviewers at an individual file level in the META.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants