# RAMP accessibility issues

**URL:** <https://meta.discourse.org/t/ramp-accessibility-issues/164000>\
**Category:** UX\
**Tags:** accessibility\
**Created:** [September 14, 2020, 5:11pm UTC](https://meta.discourse.org/t/ramp-accessibility-issues/164000 "2020-09-14T17:11:38Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![KKavoussanakis](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kkavoussanakis/32/193630_2.png) [@KKavoussanakis](https://meta.discourse.org/u/KKavoussanakis)\
**Post date:** [April 7, 2021, 1:24pm UTC](https://meta.discourse.org/t/ramp-accessibility-issues/164000/14 "2021-04-07T13:24:12Z")

</div>

I fell a bit behind with this, though we upgraded the forum. But thought to reply to the people who took the time (many thanks!) to look into this thread.

> [@riking](#):
>
> The `styleguide` plugin will show you all of the colors 🙂
> 
> [https://theme-creator.discourse.org/styleguide/atoms/colors](https://theme-creator.discourse.org/styleguide/atoms/colors)

Thanks. If I click on your link, Wave finds 13 accessibility (low contrast) issues, but not on the colours themselves. That’s because, unlike the colours page, it does not show how they are used (as background or foreground with lettering).

> [@elijah](#):
>
> My recollection is the admin side of Discourse has separate (harder to edit) style sheets to make it harder for people to accidentally lock themselves out of a usable admin interface with CSS changes.

Let me know how I can help; it does have many contrast errors.

---

_[View the full topic](https://meta.discourse.org/t/ramp-accessibility-issues/164000)._
