Event Invitation: Adapt Symbols Workshop: Implementation Approach Session

[View this event in your browser](https://www.w3.org/events/meetings/a124c8bf-3982-4d0f-8862-7440d677983b/)

 Adapt Symbols Workshop: Implementation Approach Session Upcoming Confirmed
===========================================================================

 06 May 2025, 16:00 -17:00 Europe/London

[ WAI Adapt Task Force ](https://www.w3.org/groups/tf/personalization-tf/calendar/)This is a specific part of the overall [Adapt Symbols Workshop](https://www.w3.org/events/meetings/bbc58010-4239-4aa9-8ef2-3c05344aaed9/), where we will present a summary of the work (use cases, implementation requirements) and any specific barriers we foresee.

The goal is to highlight any specific barriers we foresee, how we plan to address them, and seek feedback on our proposed approaches to doing so.

We have a [draft matrix](https://docs.google.com/spreadsheets/d/19AfygtoQ11uRFu1kBZWuwobKVa8N2GuZzvzDhOVjIa4/) detailing the use cases/requirements/issues we've looked at. From this, we have the following specific questions that we'd like to cover with you on the call:

- Highlighting our concern around the keying scheme: we intend to provide a dictionary of concepts, but using Unicode code points for Bliss characters is actually keying off the visual presentation of the concepts (we can elaborate on the call; there is some more detail in the matrix).
- Accessible name for rendered symbols.
- Technical expertise required to personalise the fonts vs. cascading a set of fonts - and any fingerprinting risks associated with both possible approaches.
- Need for multiple `<rt>`s per `<ruby>` (laid out appropriately).
  
  
  - **Update:** After further research last night, we found that this does appear to be possible (including having the rendered symbols horizontally laid out).
- Overloading of `<ruby>` / are we looking at something like `<ruby symbol>` or similar?
- What to do if a symbol set font doesn't have a symbol for a concept that is being used - presumed default behaviour of showing a blank square/diamond will confuse users.

**Note:** Our matrix is a draft, and we are currently down one technical member of the group due to illness alas, so we still have some issues to look into amongst ourselves first (as noted in the matrix).

 Agenda
------

[Agenda](https://github.com/w3c/adapt/wiki/2025%E2%80%9005-Face-to-face-meeting#day-2---2025-05-06-tuesday) Joining Instructions
--------------------

 Instructions are restricted to meeting participants. You need to [ log in](https://auth.w3.org/?url=https%3A%2F%2Fwww.w3.org%2Fevents%2Fmeetings%2Fa124c8bf-3982-4d0f-8862-7440d677983b%2F) to see them.

 Participants
------------

### Organizers

- Matthew Atkinson
- Janina Sajka
- Lionel Wolberger

### Groups

- [WAI Adapt Task Force](https://www.w3.org/groups/tf/personalization-tf/) ([View Calendar](https://www.w3.org/groups/tf/personalization-tf/calendar/))

### Invitees

- James Craig
- Anne van Kesteren
- Kevin White

 Report feedback and issues on [ GitHub](https://github.com/w3c/calendar "W3C Calendar GitHub repository").