I want to rename the screenreader text for the setting wheel (for accessible text, zoom to fit, keyboard shortcuts...). Which line in the "Aa Text Labels" is it?
When opening up a .story file on my end, I see the accessibility controls in lines 42 and so on:
Perhaps it is in a similar area within your course. Would it be possible for you to upload a copy of your .story file to this thread or privately in a support case? Clearly identifying this within your project's player properties would be helpful in order to assist you better!
Those entries from line 42 on I found. But there is no line with "settings". When I focus the setting wheel in the playbar with my screenreader NVDA says "settings" but I want it to be something else...
I attached my .story. I deleted all the actual slides, but does not matter because the player stays the same.
Thanks so much for sharing your file and clarifying what you are looking for!
I believe what you are experiencing is a bug. I will get in touch with our team and notify them of this. We'll be sure to update this thread in the future with any news so you are in the loop!
I'm curious to see if others in the community have come across a workaround!
3 Replies
Hi Moritz,
When opening up a .story file on my end, I see the accessibility controls in lines 42 and so on:
Perhaps it is in a similar area within your course. Would it be possible for you to upload a copy of your .story file to this thread or privately in a support case? Clearly identifying this within your project's player properties would be helpful in order to assist you better!
Thanks so much!
Hi Luciana,
thank you for your response!
Those entries from line 42 on I found. But there is no line with "settings". When I focus the setting wheel in the playbar with my screenreader NVDA says "settings" but I want it to be something else...
I attached my .story. I deleted all the actual slides, but does not matter because the player stays the same.
Thank you for your help!
Moritz
Hi Moritz,
Thanks so much for sharing your file and clarifying what you are looking for!
I believe what you are experiencing is a bug. I will get in touch with our team and notify them of this. We'll be sure to update this thread in the future with any news so you are in the loop!
I'm curious to see if others in the community have come across a workaround!