70 pre-built scenarios

Test Case Library

Browse, filter, and select from curated test cases for evaluating AI systems across all dimensions.

Sign in

Access your evaluation projects.

or

Forgot your password?

Don't have an account? Create one

Create account

Start evaluating your AI systems.

or skip the password

Already have an account? Sign in

Reset password

Enter your email and we'll send you a reset link.

Back to sign in

Choose a new password

Enter and confirm your new password below.

Evaluation Builder

Define your system, select criteria, choose test cases, and run your evaluation.

1
System
2
Criteria
3
Test Cases
4
Evaluate
5
Results

Define Your System

Select Evaluation Criteria

These five dimensions define what "good" looks like for your AI system. We've pre-set the weights based on your system type - higher weight means that dimension counts more toward your overall score.

Hover the ⓘ icon next to each criterion to learn what it measures and when you might want to adjust its weight.

Select Test Cases

We've suggested test cases based on your system type. Select the ones you want to include, or add your own.

Run Evaluation

For each test case, paste the actual system output and score the result.

0 / 0 scored

Your Projects

+ New Evaluation
EU AI Act

EU AI Act Compliance Audit

Pre-configured evaluation template with all high-risk test cases mapped to EU AI Act obligations. Produces structured test evidence to support the testing and accuracy parts of your Articles 9-15 technical documentation.

Includes 54+ high-risk test cases across all 5 evaluation dimensions

Back to Dashboard

Compare Evaluations

Session Activity

Your wizard activity in this tab. This log stays in your browser and clears when you refresh or close the page. See our Privacy Policy for the site analytics we do collect.

Blog

Insights on AI evaluation

Practical guides, frameworks, and best practices for testing AI systems before production.

Views expressed in these articles reflect the EvalSpec team's experience and research. They do not constitute professional, legal, or regulatory advice.

← Back to all posts

The EU AI Act Deadline Everyone Forgot About Is Four Days Away

The Digital Omnibus gave most teams sixteen months of breathing room on high-risk AI obligations. That's real relief, and it's easy to see why compliance leads relaxed. But one deadline was never part of that deal. Article 50 transparency obligations come into force on 2 August 2026, and for anyone running a chatbot, generating synthetic content, or deploying emotion recognition, that date is now days away, not months.

What actually lands on 2 August

Article 50 covers four specific disclosure duties. AI systems that interact directly with people, chatbots, voice assistants, virtual agents, must make clear the user is talking to a machine, not a human. Emotion recognition and biometric categorisation systems need to notify the people they're analysing. AI-generated or manipulated content, including deepfakes, needs machine readable marking. Text published to inform the public on matters of public interest needs a disclosure if it was AI generated, unless a human has reviewed it editorially.

None of this is new law. It's the part of the Act the Digital Omnibus explicitly left untouched. Existing systems get a four month grace period on watermarking specifically, running to 2 December 2026, but the core disclosure duties for new deployments start now.

The gap between "we know about this" and "we've tested it"

Most teams we talk to can recite the August deadline. Fewer can point to where in their product the disclosure actually happens, or confirm it survives a redesign, an A/B test variant, or a third-party widget embedded in the flow. That's the practical risk here. Compliance isn't a policy document, it's a behaviour that has to be verified every time the interface changes.

Before this week is out, it's worth checking three things. First, does every conversational AI surface in your product state clearly, and early, that it's AI, not a person? Second, if you generate images, video or audio, is there a durable, machine readable marker attached to the output, not just a visible watermark that gets cropped or stripped? Third, if any part of your product uses emotion or sentiment detection on user input, is that disclosed before the data is captured, not buried in a privacy policy nobody reads?

The takeaway for QA and product teams

Treat Article 50 the way you'd treat any other functional requirement: write a test for it, run it against every release, and don't rely on a design review from six months ago to still be accurate. The Omnibus bought time on high-risk classification. It didn't buy time here.

If you need help mapping these disclosure requirements to concrete test cases you can run against your own product, that's exactly what EvalSpec is for.

Try EvalSpec free - evaluate your AI system across all 5 dimensions. No code required.

Start your free evaluation

Testing an AI system yourself?

Get the 70 test cases behind this framework, indexed by dimension and difficulty, or run a free evaluation with your own AI system.

The information in this article is provided for general guidance only. EvalSpec is a diagnostic evaluation tool and does not provide legal advice, regulatory certification, or compliance guarantees. For legal or regulatory questions, consult a qualified professional.

404

Page not found

The page you're looking for doesn't exist.

Back to home