# Difficult to read checked items in checklist **URL:** \ **Category:** Bugs & Issues\ **Created:** [February 19, 2022, 7:28am UTC](https://community.fibery.io/t/difficult-to-read-checked-items-in-checklist/2575 "2022-02-19T07:28:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![haydnhkim](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/haydnhkim/32/1430_2.png) [@haydnhkim](https://community.fibery.io/u/haydnhkim)\ **Post date:** [February 19, 2022, 7:28am UTC](https://community.fibery.io/t/difficult-to-read-checked-items-in-checklist/2575/1 "2022-02-19T07:28:51Z")
Checked items in the checklist have a strikethrough added, making the text difficult to read. And later, if strikethrough is added to Fibery, it becomes more difficult to distinguish and read. Example: ` ~~This was mistaken text~~ ` In my case, I’m using a checklist to identify completed tasks. When I opened the entity to check the history, the contents were hard to read. Should checked items have strikethrough? Only checkmarks are active on GitHub or Discourse. - To do - Done I would like to have a variety of discussions on this topic. ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [February 19, 2022, 7:24pm UTC](https://community.fibery.io/t/difficult-to-read-checked-items-in-checklist/2575/2 "2022-02-19T19:24:29Z")
Strikethrough of Checked items in Checklists is an extremely common method of indicating “done”. Another option might be to “gray out”/“fade” the text, but strikethrough is much more common in my experience. Do none of the other tools you use have strikethrough for checklists? ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [February 19, 2022, 10:25pm UTC](https://community.fibery.io/t/difficult-to-read-checked-items-in-checklist/2575/3 "2022-02-19T22:25:33Z")
You can re-style checked items by injecting CSS into the page - this rule will work: ```auto ol[data-check-list-id] li[state="DONE"] .Item { text-decoration: unset; /* remove strikethrough */ color: #999; /* adjust the color */ } ``` Looks like this: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3bc7b269574fea5a9296a1cd701a9305ea7af0fd.png) Use a browser Add-On like [User Javascript and CSS](https://chrome.google.com/webstore/detail/user-javascript-and-css/nbhcbdghjpllgmfilhnhkllmkecfmpld) to do this. But it will only affect your own browser. ---
**Author:** ![haydnhkim](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/haydnhkim/32/1430_2.png) [@haydnhkim](https://community.fibery.io/u/haydnhkim)\ **Post date:** [February 20, 2022, 2:21pm UTC](https://community.fibery.io/t/difficult-to-read-checked-items-in-checklist/2575/4 "2022-02-20T14:21:55Z")
When I searched, many services that support markdown like seem to have similar discussions. > **[Strikethrough for checklists](https://agenda.community/t/strikethrough-for-checklists/9953)** > > I frequently use Agenda’s checklists to ensure I’ve done all the necessary followup from a meeting, but it can be hard to tell at a glance which items on a longer list are ‘live’ - the circle fades a little and gets checked off, but the text... > **[Disable strikethrough for checklists](https://talk.dynalist.io/t/disable-strikethrough-for-checklists/736)** > > Hi, I’m a newcomer to Dynalist. I’m liking it quite a lot. However, I find the fact that checked checklist items get greyed out and strikethroughed (struckthrough?) a bit excessive and rather irritating. There seems to be little point in having two... > **[How to remove strikethrough for checkboxes?](https://forum.obsidian.md/t/how-to-remove-strikethrough-for-checkboxes/5753)** > > After updating to 0.8.14, I found that the checkboxes have been modified, added a strikethrough and looked more muted. However, I use checkboxes for answers of questions rather than to-do lists. It seems weird to strikethrough the right answer, for... > **[Checkboxes behavior](https://beta.bear.app/t/checkboxes-behavior/54)** > > Hi! First of all, thanks for your work and the ability to test a new editor! I want to share feedback about checkboxes’ behavior in the new editor. Right now Bear has strikethrough font style in checked items. And new one has other styling with... Actually, I wrote the article because an external collaborator complained of discomfort to me, but it seems difficult to ask that person to inject css. I wrote the entire detailed specification of the task as a checklist, so it seems that the problem was bigger. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a628134332596b6cc4fd59c0c75cae52cc230919.jpeg) I will change my writing style. Instead of writing the entire document as a checklist, I’ll just checklist the simple stuff. Thanks for your interest in this discussion! ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [February 20, 2022, 6:32pm UTC](https://community.fibery.io/t/difficult-to-read-checked-items-in-checklist/2575/5 "2022-02-20T18:32:09Z")
I think it makes sense not to write large portions of text as checklist items. But _I am curious why you initially decided to do so_ (even though you are now changing your approach). Perhaps there is some other formatting/feature that could accomplish the goal you had for putting everything under a checkbox? As one example, which may not apply to your situation, I often use the “folding” capability of Headers to sort of indicate to myself that something no longer needs to be read in-full. This “folded” state does not get saved in the doc so it will not show up for other viewers, I think. But it is really just an example.