krds-verify

Automate KRDS UI/UX compliance verification by auditing pages, components, and service patterns against a 311-item checklist. This process generates a structured verification report with P/F/E/N/A grading and actionable improvement suggestions for governance compliance.

The KRDS 311-item checklist is used for UI/UX auditing to evaluate government digital services across style, component, basic pattern, and service pattern categories. It ensures consistency with KRDS guidelines and reduces manual auditing time.

Yes, you need krds-onboarding before running KRDS verification checks. The verification process requires an onboarded institution type from krds-onboarding to properly assess digital services against the KRDS guidelines.

KRDS compliance auditing grades digital service patterns using P/F/E/N/A grading within a comprehensive verification report. It applies integrated style, component, pattern, and service verifiers to evaluate readiness against KRDS standards.

Yes, you can use KRDS verification for QA checks, product reviews, and service readiness assessments. It automates end-to-end verification across multiple categories and outputs actionable improvement suggestions for governance compliance.

A key limitation when auditing government digital services against KRDS guidelines is the dependency on krds-onboarding. Verification cannot proceed without an onboarded institution type, and the audit is strictly bound to the 311-item checklist scope.