- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Jan 2024 12:04:04 +0000
- To: public-apa@w3.org
anssiko has just labeled an issue for https://github.com/w3c/a11y-request as "REVIEW REQUESTED": == DeviceOrientation Event Specification 2024-01-29 > 2024-02-29 == - name of spec to be reviewed: DeviceOrientation Event Specification - URL of spec: https://www.w3.org/TR/orientation-event/ - What and when is your next expected transition? A new CR Snapshot expected in March 2024 - What has changed since any previous review? See https://www.w3.org/TR/orientation-event/#changes - Please point to the results of your own self-review https://github.com/w3c/deviceorientation/issues/131 - Where and how to file issues arising? https://github.com/w3c/deviceorientation/issues - Pointer to any explainer for the spec? https://w3c.github.io/motion-sensors/ Other comments: This spec initially reached CR in August 2016 ([history](https://www.w3.org/standards/history/orientation-event/)) and was [retired in 2017](https://www.w3.org/TR/2017/NOTE-orientation-event-20170530/) due to the Geolocation WG closure. In 2019 DAS WG adopted this spec and during 2019-2024 made substantial interoperability, test automation, privacy and editorial improvements as outlined in the [changes](https://www.w3.org/TR/orientation-event/#changes) section. These changes since the previous CR Snapshot from 2016 align the specification with widely available implementations, improve interoperability including testability, and add new features for enhanced privacy protections. The Accessibility Checklist responses expand on a few areas that may benefit from your comment and review prior to our expected publication. Feedback on other aspects is also welcome. Thank you for your accessibility review! See https://github.com/w3c/a11y-request/issues/71 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 January 2024 12:04:06 UTC