This ticket is the fruit of a discussion with @marloes_bosch! Currently component-authors have the flexibility of adding the label of "Accessible" to their own component. That means that this label currently doesn't hold much value, as people not fluent in a11y are being forced for themselves to choose to label their component accessible or not accessible. The first step here is to introduce the new role for user accounts: #69 Next, we need enough users on the platform that are accessibility experts [blocker for now] Next we need to label all components 'non-accessible' to have that as a default. Next we need to allow normal users on the platform to flag components as: "needs accessibility review" (Should this be a feature for paying members or does paying make it prioritised?) Next we need to provide a list overview of components that are in the waiting list for this "need accessiblity review" so a11y-experts can find them. Next we need to make sure that a11y-experts get a button on a component-detail page to tag them accessible. When this button is clicked, the master-branch of the gitlab-repo of that component will need to be tagged with "a11y-reviewed". This needs to happen in Git because of the updatable aspect of components. We can use this tag as a timestamp of when the repo got reviewed, and in this way we also don't hinder further collaboration on the component. Once tagged, we need to show the accessibility status to the end-user with an explanation of how many commits ago, it was tagged as accessible. quick mockup:  Next we need to think on how to re-apply for the label to make it more current, and what flow needs to happen there. Likely remove-tag and re-add tag?