Is there a plan to add ARIA/html labels to the controls/buttons in the player navigation bars so that screen readers pick these up in the page hierarchy? Currently, the pause/play button, back buttons, menu buttons, etc. are marked Unlabelled on the NVDA page elements list (accessed by pressing CapsLock + F7).
 

I'm creating a Knowledge Base and adding our branding to the theme. I've changed the page titles (for the menu panels on the landing page) to our brand colour but DKO seems to be creating its own colour for visited and unvisited pages, regardless of the colours I add. Please can you advise.
 

Is there a way to remove the numbering from the course pages in the outline (using the course player experience)? I've removed the learning objects. The numbering doesn't help with navigation and it doesn't make for a good screen reader experience.
 

I have added a multiple choice question to an existing page. One answer is correct. I want to offer multiple attempts at the question but I want my own incorrect feedback to show when their answer is incorrect, before they select try again. When I turn off multiple attempts the incorrect feedback shows, but I can't work out how to have both options.
 

Is there a way to change the size of the body text style? I'm wary of choosing heading styles for body text because of the risk of skipping heading levels and being less accessible as a result, but the body text seems a little too small. I can see how to edit heading level styles but not paragraph/body text.
 

What's the best practice advice for ensuring glossary terms within a page are accessible to those using assistive technology? When I add a glossary term to a word, the screen reader will read the word as a link and then you can use the keyboard to open that glossary text box. However, this method doesn't recognise the glossary link when using the screen reader to search the hierarchy of the page. I've also tried adding a lightbox action to a word as a glossary pop-up. This is recognised by th...

The WCAG guideline 1.4.4 mentions the need for a user to be able to resize text without assistive technology up to 200%. Is this something that DKO offers?