– DRAFT –
Feel the Vibe: enhancing haptics for accessibility and more fun

Slideset: https://www.w3.org/2023/07/breakout_haptics_TPAC/haptics.pdf

[Slide 1]

[round table introduction]

harry: welcome to haptics for accessibility session
… emails available for further discussion

[Slide 2]

<xiaoqian> slides

harry: go through ToC

[Slide 3]

harry: introduction of Tencent Game team

[Slide 5]

harry: background of haptics
… Haptics amend human machine interaction

[Slide 6]

harry: Haptics Taxonomy

[Slide 7]

[Slide 8]

[Slide 9]

Harry: here are some reasons worth mentioning to improve usability and accessibility

[Slide 11]

[Slide 12]

[Slide 13]

[show how to start designing a Haptic Effect]

[Slide 14]

Selen: Versatility and flexibility are the core design concepts throughout the entire solution

[Slide 18]

Selen: show how to implement haptics with their SDK

[Slide 19]

Selen: MTGPA Haptics .HE Format shows in picture
… data format is also compiled with IEEE standard

[Slide 15]

[Slide 16]

Selen: Sync to Audio and Video Design
… designed 2 solutions
… Vibration playback mechanism and Vibration Synchronization Scheme

[Slide 17]

Selen: Haptics has implemented in Games

[Slide 21]

Selen: background of users, and haptics can help visually impaired users to gain more information and understanding.

[Slide 22]

Selen: use cases include: chat, news, videos etc.,

[Slide 24]

Selen: Haptics solution for input method

[Slide 25]

Solution for maps

[Slide 26]

Selen: Promote Haptics as a Common Human Language
… Integration with Web contents, support by Web platform, adoption in Accessibility guideline
… harry will introduction standardized about haptics

[Slide 28]

harry: the fragmentation will cause a compatibility issues, there are several advantages to standard haptics, since we improve the usability

[Slide 29]

[Slide 30]

harry: haptics stack show in slide
… some standardization work has start in different org
… including: ISO MPEG-I, IETF Haptics Media, IEEE P2861.3/Haptics Industry Forum etc

[Slide 31]

[Slide 32]

harry: Haptic Data Model in MPEG
… 3 types format
… depend on situation

[Slide 33]

harry: Haptic File Format
… 3 types format

[Slide 34]

harry: introduction of encode and decode
… 2 types of input and 3 types of output

[Slide 35]

Harry: IEEE P2861.3 Haptic Enhancement for Mobile Game, for mobile haptics platform: interface, data, evaluation

angel: suggest to jump into your proposal

Harry: sure

[Slide 39]

harry: Some Thoughts on W3C Vibration API
… doesn't support sophisticated haptic wave forms
… doesn't support precision haptics

[Slide 40]

harry: Some Thoughts on W3C Gamepad Extension API
… show possible amendment for W3C standard

[Slide 42]

harry: examples

[Slide 43]

harry: some takeaway
… raise some questions

mattreynolds: I edit that API, and implement into Chromium
… I can give you more context here
… basically decided that is going to be delegated to legacy device support
… planning on adding new effects to interface
… still a lot of work to do

harry: are you consider a new API for that?

mattreynolds: yes, MS is working on an update to explainer
… can't tell you exactly last I heard

<xfq> https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/HapticsDevice/explainer.md

mattreynolds: also we want this work for service too, and with more devices
… I don't think we are going to tie specific to USB

cabanier: good to see this going
… we have an applications to create waveforms

Harry: I assume also support openXR APIs?

cabanier: yes

harry: there are also some XR work in W3C, how you promote those in two groups

cabanier: @@

chunming: does haptics consider feedback from user?

harry: no guidelines to say that, we also confused.
… now way to determine
… if we define haptics as human language, I think we should work on guidelines and rules

Matio: maybe could be possible to make some simplified font of device, to create feedback
… not only to accept some but by some movements to create

PHANTOM

<xfq> Phantom from 3D Systems

mattreynolds: last slide open questions
… 1 is the easy one to implement, we can cross the system API
… 2 yes, to across the device
… I think we have decided that it would be good to have active waveforms associated with haptic effects so that we could do the down sampling to support on plus or take full devices as well as the more modern devices.
… 3 Probably didn't able to have things to extensive use case, especially for accessibility. I don't really have a good sense of that.
… I think the rest of the room should provide feedback on that. And should there be a guideline for I think a guideline would be good, but probably should not be part of the specification.
… @@1

cabanier: earlier question, controller can provide feedback
… like 3 or 4 pressure sensitive sensors on there
… use that develop can decide how to interactive

Harry: in conclusion what is proper way to move this forward

mattreynolds: little frustrating for us, by now we have a venue to discuss, we need to encourage MS to ring that proposal to a CG
… no CG yet

angel_: what about incubate in WICG?

mattreynolds: not sure, sounds like a path