Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to guidelines for annotating regions of SVG #44

Open
VenissaCarolQuadros opened this issue Sep 10, 2023 · 3 comments
Open

Changes to guidelines for annotating regions of SVG #44

VenissaCarolQuadros opened this issue Sep 10, 2023 · 3 comments
Assignees

Comments

@VenissaCarolQuadros
Copy link
Member

VenissaCarolQuadros commented Sep 10, 2023

Need to explore (possibilities like as suggested by @JRegimbal ) and decide on the most appropriate changes to the current SVG guidelines for annotating regions within the SVG without changing the tactile rendering of the graphic (specifically for the 'guidance' mode).

Currently a circle node with attribute data-image-target= {target number} is being used for this purpose. The target number serves to indicate the sequence in which the user should be guided to the various targets. The circle area indicates the size of the target (/the annotated region) and the centre of the circle is used to calculate the distance from the target (to generate appropriate audio guidance cues). (Other shapes could also be used for the purpose but a circle was thought to be the simplest both for the annotator and for the technical implementation of distance calculation etc.- but it comes with limitations such as the shape of the annotated space)

@JRegimbal
Copy link
Collaborator

To add a bit more detail to what I'm thinking, I don't like the idea of having the same element be displayed or metadata solely depending on a custom tag. Visualizing our tactile SVGs with a regular viewer and expecting more or less the same to appear on a pin array is, IMO, a good feature. While re-using tags like <circle> is convenient, it may not be necessarily be better. I'm wondering if we can use the metadata tag and/or another XML spec in a separate namespace to add annotations on the visible elements.

@jeffbl
Copy link
Member

jeffbl commented Oct 26, 2023

@VenissaCarolQuadros This is currently status-less. Should this go into backlog, or are you planning to address this in the near term?

@VenissaCarolQuadros
Copy link
Member Author

Moved it into backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants