@wcstack/tilt 1.31.0 → 1.32.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.ja.md +4 -0
- package/README.md +4 -0
- package/package.json +1 -1
package/README.ja.md
CHANGED
|
@@ -160,6 +160,10 @@ core.dispose();
|
|
|
160
160
|
|
|
161
161
|
Core の構造サーフェスは wcstack I/O ノード横断の規範です([async-io-node-guidelines §3.9](../../docs/async-io-node-guidelines.ja.md))。要素なしで signals に束縛するには [@wcstack/signals — Core を直接束縛する](../signals/README.ja.md#core-を直接束縛する要素なし) を参照。
|
|
162
162
|
|
|
163
|
+
## アクセシビリティ
|
|
164
|
+
|
|
165
|
+
**WCAG 2.5.4 Motion Actuation(レベル A)**: デバイスを動かして操作するものは、動かさずにも操作できなければ**ならず**、モーション入力自体を無効化できなければならない。全員が端末を傾けられるわけではない — 車椅子に固定された端末もあれば、振戦は傾き入力をノイズに変える。具体的には: 傾き駆動の操作すべてに、同じコードパスへ流れる並行入力(キーボード・ポインタ・ボタン)と、センサーへの反応を止める手段(`stop` コマンドがまさにそれ)が要る。[`examples/state-tilt-maze`](https://github.com/wcstack/wcstack/tree/main/examples/state-tilt-maze) が参照実装: 矢印キーとドラッグがセンサーと同じ疑似傾きチャネルに乗り、ゲームロジックはどの入力が有効かを知らない。
|
|
166
|
+
|
|
163
167
|
## ライセンス
|
|
164
168
|
|
|
165
169
|
MIT
|
package/README.md
CHANGED
|
@@ -164,6 +164,10 @@ core.dispose();
|
|
|
164
164
|
|
|
165
165
|
The structural Core surface is normative across wcstack IO nodes ([async-io-node-guidelines §3.9](../../docs/async-io-node-guidelines.md)); to bind it into signals with no element at all, see [@wcstack/signals — Binding a Core directly](../signals/README.md#binding-a-core-directly-no-element).
|
|
166
166
|
|
|
167
|
+
## Accessibility
|
|
168
|
+
|
|
169
|
+
**WCAG 2.5.4 Motion Actuation (Level A)**: anything operated by moving the device **must** also be operable without moving it, and the user must be able to disable the motion input. Not everyone can tilt a phone — devices get mounted on wheelchairs, and tremors turn tilt input into noise. Concretely: every tilt-driven interaction needs a parallel input (keyboard, pointer, buttons) feeding the same code path, plus a way to stop reacting to the sensor (the `stop` command is exactly that). [`examples/state-tilt-maze`](https://github.com/wcstack/wcstack/tree/main/examples/state-tilt-maze) is the reference shape: arrow keys and pointer drag ride the same simulated-tilt channel as the sensor, so the game logic never knows which input is active.
|
|
170
|
+
|
|
167
171
|
## License
|
|
168
172
|
|
|
169
173
|
MIT
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@wcstack/tilt",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.32.0",
|
|
4
4
|
"description": "Declarative Device Orientation component for Web Components. Framework-agnostic deviceorientation wrapper via wc-bindable-protocol.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.esm.js",
|