search

w3c / miniapp-lifecycle

MiniApp Lifecycle
https://w3c.github.io/miniapp-lifecycle/
Other
7 stars 6 forks source link

Accessibility Considerations text is confusing or incorrect #32

Closed pes10k closed 2 years ago

pes10k commented 2 years ago

This issue is being filed as part of of PING's horizontal review

The current accessibility considerations section says (in total)

As MiniApp Lifecycle is not user aware and does not involve user interaction, accessibility consideration is not needed in this specification.

This seems incorrect or misleading since many of these events will happen because of user interaction, no? (the app being launched, a page being shown, closed and / or switched with another, etc)

This is not a blocking privacy issue, but im mentioning it since it came up during the review

QingAn commented 2 years ago

This seems incorrect or misleading since many of these events will happen because of user interaction, no? (the app being launched, a page being shown, closed and / or switched with another, etc)

@pes10k In this case, yes, MiniApp Lifecycle change is triggered by user interaction. MiniApp Lifecycle spec defines GlobalState and PageState to indicate whether the MiniApp is shown or hidden, which can be used to accommodate assistive technologies.

Does it address this issue by adding some text description like the above in the Accessibility Considerations section?

pes10k commented 2 years ago

Yep, just clarifying that the proposal does involve (sometimes) responding to user interactions would be sufficient here. Thanks!

QingAn commented 2 years ago

resolved