How to Use the RADAR Framework
What is RADAR?
RADAR is a structured framework that aims to simplify and standardise one of the world’s most comprehensive legislations to govern digital platforms–Regulation (EU) 2022/2065, more commonly known as the Digital Services Act (DSA).
RADAR dissects and breaks down the regulatory provisions of the DSA into thematic categories with specific infringements and corresponding observable indicators. Each category and infringement have a unique identifier, the sole purpose of which is to create a standardised tagging system for its stakeholders.
RADAR is a platform agnostic, community-driven framework that is designed to evolve with the DSA to ensure that it remains accurate, relevant and useful in the long term.
Who can use it
RADAR can be used by a diverse set of stakeholders to help identify, assess or address potential infringements of the DSA. Regulatory authorities, civil society organisations, private companies tackling online harms, researchers, and even digital platforms themselves can benefit from using this framework.
Why is it important
Fundamentally, RADAR is designed to make legalistic and confusing regulatory requirements posed by the DSA more accessible for everyone, especially to those without legal training and expertise. It takes a community-driven approach to ensure that it isn’t siloed off and disconnected from the actual needs of the community.
Moreover, through the provision of each unique identifier, RADAR enables a systematic and standardised way to share information about potential infringements of the DSA. Doing this not only allows stakeholders to speak the same language, but also streamlines and strengthens enforcement efforts.
Who owns RADAR
RADAR is maintained by Check First OY (FI3143603-4) and is licensed under CC-BY-SA 4.0. You can contact Check First by email at radar[at]checkfirst.network
Video Walkthrough
New to RADAR? Watch this 2-minute video for a quick tour of the framework's key features.
In this video, you'll learn how to:
- Navigate the framework by categories or DSA articles
- Search for specific platform behaviours and violations
- Identify infringements using observable behaviours
- Generate standardised reports with the Tag Generator
💡 Tip: After watching, continue reading below for detailed step-by-step instructions and best practices.
How Does It Work?
🏷️ The Tagging System
Each potential DSA infringement has a unique ID (like cr_01). When you identify issues on a platform, you match them to these standardised tags based on observable behaviours.
🔍 Observable Behaviours
Each infringement includes specific "observables" - concrete behaviours or patterns you might witness. If you see these behaviours, it indicates a potential infringement.
📊 Community Intelligence
When multiple reports use the same tags, patterns emerge. This collective intelligence helps identify systemic issues and priority areas for enforcement.
Step-by-Step Guide
Step 1: Identify the Issue
Document what you observed on the platform. Be specific about:
- What happened
- When it occurred
- Which platform features were involved
- How users were affected
Step 2: Browse the Framework
Use RADAR to find matching infringements:
- Start with Categories - Find the general area (e.g., "Content-Related", "Dark Patterns")
- Review Infringements - Read through the specific violations in that category
- Check Observables - Match your observations to the listed behaviours
- Note the IDs - Record all relevant infringement IDs
Step 3: Create Your Report
Write your detailed analysis, including:
- Executive summary
- Detailed findings
- Evidence and screenshots
- Impact assessment
Step 4: Add RADAR Tags
Include a RADAR Tagging Annex at the end of your report with all identified infringement IDs. This standardised format enables cross-report analysis.
RADAR Tagging Annex Template
Copy this template and add it to the end of your report:
--- ANNEX: RADAR Framework Tags Digital Services Act Infringement Analysis Platform: [Platform Name] Assessment Date: [YYYY-MM-DD] RADAR Version: [e.g., 1.7] Identified Infringements: Category: Content-Related Infringements - cr_01: Failure to take action against Illegal Content * Observed: [Brief description of what you observed] * Evidence: [Page/Section reference in main report] - cr_02: Misapplication of Notice-and-Action Mechanisms * Observed: [Brief description] * Evidence: [Reference] Category: Dark Patterns - dp_01: Obstruction * Observed: [Brief description] * Evidence: [Reference] Total Infringements Identified: [Number] DSA Articles Potentially Violated: [List article numbers] ---
Real-World Example
Scenario: Difficult Account Deletion
You discover that a social media platform makes it extremely difficult to delete an account - requiring multiple confirmations, waiting periods, and hiding the option deep in settings.
Your process:
- Document the deletion process with screenshots
- Search RADAR for "account deletion" or browse "Dark Patterns"
- Find dp_01 "Obstruction" matches your observation
- Include this tag in your report's annex
Result: Your report now uses standardised language that can be compared with other reports, helping identify if this is a widespread issue.
Best Practices
✅ Do:
- Be specific about what you observed
- Tag all relevant infringements
- Reference evidence in your main report
- Use the latest RADAR version
- Include dates and platform versions
❌ Don't:
- Force-fit observations to tags
- Use tags without evidence
- Modify the tag IDs
- Skip the observable matching step
- Forget to specify RADAR version
💡 Pro Tips
🌐 RADAR Web Metadata
For digital reports, articles, or research published on the web, you can embed RADAR metadata directly in your HTML. This enables automated scanning, browser extensions, and aggregation tools to read your tags.
Method 1: Meta Tag (Recommended)
Add this to your HTML <head> section:
<meta name="radar-assessment" content='{"version":"1.7","platform":"Example Platform","date":"2024-12-20","categories":{"cr":["cr_01","cr_02"],"dp":["dp_01"],"icg":["icg_03"]}}'>
Method 2: JSON-LD Script Tag
For richer data, use a structured data approach:
<script type="application/ld+json">
{
"@context": "https://radar.checkfirst.network/schema.json",
"@type": "DSAAssessment",
"version": "1.7",
"platform": "Example Platform",
"assessmentDate": "2024-12-20",
"infringements": {
"cr": ["cr_01", "cr_02"],
"dp": ["dp_01"],
"icg": ["icg_03"]
},
"totalInfringements": 4,
"report": "https://example.com/full-report"
}
</script>
Benefits of Web Metadata
- Machine Readable: Automated tools can scan and aggregate RADAR tags across the web
- Browser Extensions: Future extensions could display RADAR assessments for any webpage
- Search Integration: Enables RADAR-aware search engines and databases
- Verification: Links assessments directly to published reports
- Transparency: Makes DSA compliance assessments publicly discoverable
Reading RADAR Metadata
To check if a webpage has RADAR metadata, paste this into your browser console:
// Quick check for RADAR metadata
const meta = document.querySelector('meta[name="radar-assessment"]');
if (meta) {
console.log('RADAR Assessment Found:', JSON.parse(meta.content));
} else {
console.log('No RADAR metadata found');
}
Quick Generator
Generate your metadata tag:
Join the Community
RADAR is a community-driven framework. By using these standardised tags, you're contributing to a collective understanding of DSA compliance across the digital landscape.
Questions or suggestions? Visit CheckFirst or contribute to the GitHub repository.