Change bullet color in Rise

Thanks for checking in, everyone! I don't have any updates right now, but we'll let you know if we make any adjustments in Rise 360 that will help with changing the bullet color. 

Hi there, we also want to change the bullet point color in an unordered list in a text block. When will this be fixed? 

Hello - is there any update on being able to change the colour of the bullets. It really needs to be in place to meet today's accessibility needs. Thanks in advance!

Hello - Has this been resolved? Would be very helpful for me.

This seems to be something that everyone wants but has not been resolved in three years. Reading through a lot of these threads to help understand the program better I find that there is a lot of discussion from the 360 staff that its on the roadmap and it has been documented but no resolve.

My issue is my bullets are white with a white background and black text. Are we able to have any confirmation about when this will be actually looked at.

It's possible to change bullet colors in Rise by editing HTML after exporting:

1. Export your course from Rise.

2. Open index.html which is in the root of output folder for Web or XAPI output, in scormcontent folder for SCORM 1.2 output.

3. Copy the contents of window.courseData variable - literally all the text in-between the quotes:


4. Go to https://www.base64decode.org/ , paste contents into the top textbox, and tap <DECODE> button.

5. Copy the decoded text from the bottom textbox and paste into a text editor of your choice, I'm using Sublime Text.

6. Find your bullets by searching for the list item text:



7. Now go to the <ul> parent tag:

and add the color styling like this:

So in above, I added

style=\"color:#FF0000;\"

to <ul> so default bullets become red. Remember the backslashes (\) before the quotes.

8. Now copy all the text from your text editor.

9. Go to https://www.base64encode.org/ , paste the text into the top textbox, make sure these settings are selected:



and tap >ENCODE< button. 

10.  Copy the encoded text from the bottom textbox and paste to replace over the window.courseData variable text inside the quotes you copied in step 3.

11. Save your changes to index.html and open in browser, bullets should now be the color you want:

If you just see a white screen, make sure you had correct settings in step 9 and included backslashes in step 7.

I think the point is that we shouldn't need to do this outside of the software. Working outside of Rise means that each time you republish the course, you need to update the code, which is a garbage way to work on anything. In my industry, changes and updates happen often, and the functionality should be built within the software as it is for most layout/word processing software on the market today... It's basic text editing which already exists in CSS/HTML workflows, so it seems a bit odd that in the 3 years this issue was put in, nothing has changed.

Trying to give them the benefit of the doubt, but agree in substance.

My IT team just figured out a way to start with collapsed menus, rather than expanded...another feature I've requested. On my wish list, that was an essential feature for usability. One of my "courses" contains dozens of curated content pieces. Opening with a collapsed menu eliminated the long laundry list of resources that overwhelmed our users. Now they just see the major categories and expand only when they want to see the resources within it. My IT team also developed a way to automate changing the html code each time we purplish the course. I will share on a collapsed menu thread for the community once I have the code and how it was automated. This just happened this week.

Thanks again for sharing your code.

Wow! That's a lot of work. Thanks so much for sharing this work-around. Perhaps because you have dug deep into the code that by sharing it with everyone might help the Articulate folks expedite adding this functionality.

I love the Articulate product line, community, heroes, staff and support teams. Everyone is so helpful and supportive. The number of feature requests is undoubtedly large in number and have to be prioritized. As an ID, this is just one of those things that would make all the difference on the design end. Admittedly, not the biggest fish to fry.

Thanks again for your contribution!

Hi Articulate team, any updates on this?