# RAMP accessibility issues **URL:** \ **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:** 11
**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:** [March 24, 2021, 2:45pm UTC](https://meta.discourse.org/t/ramp-accessibility-issues/164000/11 "2021-03-24T14:45:37Z")
I will pluck the courage to do all the updates later (hopefully) and report again. Re theme, it all got a bit messy. We use (and modified) the Light theme. We made the following high-level changes to the colours: ``` Tertiary: #0088cc → #006498 Quaternary: #e45735 → #C93C1B Danger: #e45735 → #C93C1B Success: #009900 → #007A00 ``` The clever trick I thought of late is to just test the colours page for accessibility. 🙂 We then made a large number of changes using the CSS editor (admin/customize/themes/3/common/scss/edit) that I am not sure how to pass on (I can copy-paste, but I am not sure that’s what you want nor if you want it on this thread). I think if we could see the other colours mentioned (e.g. var(–primary-medium)) on a high-level interface, things may become easier. E.g. a classic one was #919191 → #595959, but my method just treats symptoms that I somehow see when traversing pages (and then again the dynamic nature of the “site” means that what passes today may not pass tomorrow). Happy to try in a different fashion too, just let me know, though at no point will I be able to run a demo service, check out code etc. I should also note that I could not fix admin/upgrade at all (and it has numerous contrast issues); I am not sure if it does not follow CSS or what the reason is. --- _[View the full topic](https://meta.discourse.org/t/ramp-accessibility-issues/164000)._