Within the theme, I can remove the background colour however, I cannot style the Disabled Component Item Icon Colors. The disabled icon colour is always the same as the Color.
Hey @hbailey, sorry to tag you, but it’s my first time back in a while and I’d like to know if I’m making a mistake or if this is how Evolve works now.
You need to go to the support hub at https://intellum.my.site.com/s/ and if you haven’t already been given an account, use the Request Login link to get access.
Why can’t you add a colour to those items (disabled and whatnot) - just click the + and choose a colour? Does that work?
Thanks Helen, I’ve since requested a login for the support hub.
It would seem the only colours that affect the icons on the Narrative comonent are the Color and the Hover. The Selected, Disabled and Visited don’t appear to do anthing.
The course in question used an article style. However, please bear in mind that this theme has not been touched since last year, so the course should look and act the same. I was only editing text within it.
Before raising the issue here, I used a test course with no article style and the main theme also does not affect the colour of the disabled icon in a narrative component.
In the past I’m sure Evolve would not show the disabled buttons on the first and last frames, so I guess something has changed.
Yes, that’s correct - what’s changed is that we’ve made a big update to the Narrative and Text Narrative components to make them WCAG 2.1 accessible. They are not flagged as such yet because we are currently in the process of getting them tested & certified by a third party.
One of the main reasons these two components were not accessible was because the slide navigation buttons were removed on the first/last slide.
Obviously we do try to avoid making changes that could change the look/feel/behaviour of an existing course but in situations like this it is unavoidable.
Yep that does seem to be an oversight. I will get that logged up and fixed. However, if you are trying to make the button invisible when disabled just be aware that doing that creates a disconnect between what is accessible via the keyboard/screen reader and what is on screen, so would likely be considered an accessibility failure.
@BarryBPS yeah Discourse is so well put-together - I don’t recall ever having a single issue with it since I’ve been at Intellum! Also seems to me to be a great example of getting Open Source just right.
