New settings and controls

Silktide 5 gives your organisation more control over how Silktide tests and how the work is handed out. Several of these are new. Others replace a Silktide 4 idea with a clearer one.

New concepts

• Criteria. The scored groups inside each module, such as Writing, SEO & AEO, or a regulation you choose. Review which checks belong to each one, and create criteria for your own policies. They replace the fixed category tree Silktide 4 used. See How scoring changed in Silktide 5. In the app they live under Website settings.
• Priority levels. Levels such as P1, P2, and P3 that say how urgently your organisation wants a check handled. They replace the severity badges Silktide 4 showed, and you can filter by them. They do not change how many points a check takes off a score. That impact comes from the priority and confidence Silktide assigns, which keeps scores comparable between organisations.
• Responsibilities. Labels such as editor, developer, or designer for who is expected to fix a finding. Each person can choose theirs in My settings so their own work comes first.
• Checks. One place to administer every website check, Silktide's and your own, filtered by priority, module, and status. In Silktide 4 this was spread across policies and website settings.

Reworked areas

• Regulations. Choose which accessibility and privacy regulations apply on each website, from that website's Compliance area. Silktide scores the ones you turn on, and uses them when it drafts an accessibility statement for you to review and publish.
• Usage. A screen showing your account's measured resource consumption over time, with room to look closer.
• Integrations. A catalogue for connecting Silktide to other systems, starting with Slack, plus MCP for AI tools you already use.
• Library policies. Choosing a policy for one website now lives in the Compliance module, next to the results it produces. Grouping checks into scored areas is handled by criteria.
• Labels. In Silktide 4 these were called tags. Silktide 5 calls them labels so they are not confused with HTML tags or the accessibility tags in a tagged PDF. See What happened to tags?.