30% to 40% metrics contain a 'Requirement level:' at the end of the translation. The use of the required, recommended and optional is explained properly here: https://internet.nl/faqs/report/ and linked in the report.
Given there are so many tests that have a requirement level, i think it would make sense to add this as a separate field in all metric translations. Meaning that all metrics will have a requirement level field, where the front-end can choose to make 'required' an implied state as is the case now on internet.nl. This also might make it easier to maintain these requirement levels when policies change.
30% to 40% metrics contain a 'Requirement level:' at the end of the translation. The use of the required, recommended and optional is explained properly here: https://internet.nl/faqs/report/ and linked in the report.
Given there are so many tests that have a requirement level, i think it would make sense to add this as a separate field in all metric translations. Meaning that all metrics will have a requirement level field, where the front-end can choose to make 'required' an implied state as is the case now on internet.nl. This also might make it easier to maintain these requirement levels when policies change.