Custom criteria

Want WebLens to check something the published criteria set doesn't cover yet? That's where the service team comes in.

What a custom criterion looks like

Every WebLens criterion answers one question, on the same evidence, the same way, every time. A custom criterion is no different, the only thing custom is what it's checking for.

Typical reasons teams ask for one:

• A house rule that isn't in WCAG or the Siemens Design System (e.g. a particular field-order convention in your product line).
• A pattern that's specific to your application, a regulated form, a configurator step, a multi-tenant entry screen.
• A measurement we don't run yet but you'd want to track over time.

How we add one

Custom criteria are built and validated by the WebLens service team. We work through it with you in three rounds:

1. You describe the rule and share examples of what should and shouldn't trigger it.
2. We build the criterion, run it against a labelled set, and publish its expected accuracy alongside it.
3. We ship it to your workspace and you can opt it into any assessment from then on.

Get in touch

Email aps.accessibility.it@siemens.com with a short description of the criterion you'd like added and a couple of representative pages, and we'll take it from there.