You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The entire UI is built using a single SVG image. Although it looks neat, it is currently impossible to use with the keyboard (try pressing ↹ Tab). Additionally, the interface is certainly not accessible to users with screen readers.
It still doesn't work correctly, but I can't investigate it right now. I had to add a dummy <rect> element so the browser would know the dimensions and the position of the anchor. (Apparently the browser can't figure it out from the <use> element.)
Although incomplete and non-working, I hope this patch can be a starting point.
You can see an example of an SVG image that is completely navigable by keyboard on my own personal website: https://denilson.sa.nom.br/
Making it accessible by keyboard is only a fraction of making it fully accessible. I don't have enough experience with that, I'm sorry I can't help you further. I know it is related to adding ARIA attributes and a few other guidelines, but someone else can explain it better than me.
The text was updated successfully, but these errors were encountered:
Already on my to-do list, I may rework the entire UI in the next major release. However, it will take some time as I am currently busy with many other tasks. I will revisit this later.
The entire UI is built using a single SVG image. Although it looks neat, it is currently impossible to use with the keyboard (try pressing
↹ Tab
). Additionally, the interface is certainly not accessible to users with screen readers.There are two initial solutions: (pick one)
<a xlink:href="…">…</a>
element.I've tried implementing the second solution, and here's an incomplete patch:
It still doesn't work correctly, but I can't investigate it right now. I had to add a dummy
<rect>
element so the browser would know the dimensions and the position of the anchor. (Apparently the browser can't figure it out from the<use>
element.)Although incomplete and non-working, I hope this patch can be a starting point.
You can see an example of an SVG image that is completely navigable by keyboard on my own personal website: https://denilson.sa.nom.br/
Making it accessible by keyboard is only a fraction of making it fully accessible. I don't have enough experience with that, I'm sorry I can't help you further. I know it is related to adding ARIA attributes and a few other guidelines, but someone else can explain it better than me.
The text was updated successfully, but these errors were encountered: