Fuqiao Xue

Preview: https://raw.githack.com/MichaelWangzitao/MiniApp-UI-Componets/main/index.html

Created https://github.com/w3c/miniapp-components per [yesterday's CG meeting](https://www.w3.org/2021/07/15-miniapp-minutes.html#t01).

Related discussions: https://www.w3.org/2021/08/19-miniapp-minutes.html#t03

Related discussions: * https://www.w3.org/2021/04/08-MiniApp-minutes.html#t10 * https://www.w3.org/2021/04/22-miniapp-minutes.html#t01 * https://www.w3.org/2021/05/20-MiniApp-minutes.html#t03

Another related question: If we don't expose the DOM tree, is it possible to expose an accessibility tree for accessibility APIs to provide a representation that can be understood by...

Because it was proposed by the authors of MiniApp frameworks in the CJK meeting, I will try to ask them. IMHO the biggest benefit is that website client-side JavaScript code...

> If we don't expose the DOM tree, is it possible to expose an accessibility tree for accessibility APIs to provide a representation that can be understood by assistive technologies...

Filed https://github.com/w3c/miniapp/issues/166 for the accessibility tree issue.

The reason is that PING sometimes also files security issues, and we usually just label it as `security-needs-resolution`. Currently, it appears in "Security" but not in "PING".

The reason may be because [ReSpecs's language matching method](https://github.com/w3c/respec/blob/471d6f5b20aab17e0b9db969418ef53f4b568d4c/src/core/utils.js#L176-L208) is relatively simple. Ideally, the algorithm in [BCP 47](https://www.rfc-editor.org/info/bcp47) should be used. See https://github.com/wooorm/bcp-47-match for an example.