← starnum.com.tw

Accessibility Statement

Accessibility v2.0

Version 2.0 · · Governance 2.0 public evidence surface

Governance 2.0 Overview

This page is part of the starnum public Governance 2.0 surface and uses the same evidence layer as the system card, data governance, transparency report, use policy, and security policy.

Governance Summary

This page explains accessibility commitments and the machine evidence used to keep governance pages readable and navigable.

Scope

WCAG state, contrast, keyboard-readable navigation, responsive evidence tables, language coverage, and footer consistency.

Implementation Status

Version 2.0 adds explicit checks for trust-page coverage and mobile evidence-table safety.

WCAG 2.1 AA — Ongoing improvement

Last reviewed:

starnum.com.tw is committed to making this site usable for everyone, including people who rely on assistive technology (screen readers, keyboard navigation, etc.). This page explains our WCAG 2.1 AA compliance status, known issues, and remediation plan.

Target Standard

This site targets Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

Compliance Status

WCAG PrincipleStatusNotes
1. Perceivable Partial All HTML pages declare a lang attribute; image alt text is partially in place; text color contrast meets the 4.5:1 requirement for primary text.
2. Operable Partial Primary pages support keyboard navigation; FAQ accordions use JavaScript and are keyboard-activatable; the chart calculator needs further work.
3. Understandable Compliant Page language is explicitly marked (lang attribute); error messages include explanations; form fields have labels.
4. Robust Partial Semantic HTML structure; JSON-LD Schema provides machine-readable data; ARIA markup on some interactive widgets is still being refined.

Accessibility Measures in Place

Structure and Semantics

Visual Design

Keyboard and Interaction

Known Issues and Remediation Plan

IssueScopePlanned fix
Interactive chart graphic lacks ARIA description chart.html chart display area Q2 2026
Some ad widgets lack aria-label Site-wide ad cards Q2 2026
Skip-to-main-content link Site-wide header Q2 2026
Mobile hamburger menu ARIA expanded state Mobile navigation Q3 2026

Technical Specifications

This site uses the following technologies, which have been verified to be compatible with mainstream assistive technology:

Automated Accessibility Monitoring

This site uses scripts/wcag-audit.js (built on pa11y + axe-core) to regularly scan key pages for WCAG 2.1 AA compliance. Results are stored in data/wcag-report.json, run weekly to track remediation progress.

Report an Accessibility Issue

If you run into an accessibility problem while using this site, please get in touch:

Please describe: the issue you encountered, the assistive technology you were using (e.g. screen reader name and version), and the URL of the page where it happened. We aim to respond within 14 working days.

External standards and primary sources

These primary sources inform this page. They are benchmarks, not third-party endorsements of this site.

Current Machine Audit Snapshot

This block uses only traceable local audit data. No unsupported metrics or model claims are added.

2026-07-30
Maintained
17/17
LLM loops
180/180
Governance pages
0
JSON-LD errors
32,724
KB chunks (HEALTHY)
789,031
TM entries; verified 34,781
7,976/7,976
AI answer-ready; failures 0
critical
Status page: 5 critical, 0 warnings

Content Maintenance And Update Decision

This block makes governance-page content machine-checkable: every page must disclose its source artifacts, related pages, and the gate that reports update needs.

Update Decision

This is not static copy. When source artifacts, related policies, public metrics, or generators change, AI Ops reports evidence and an AI agent decides whether the page needs edits.

Human Boundary

Systems detect, report, and preserve machine-readable evidence. Codex/Claude agents perform final judgment and repair.

Verification Command

node scripts/verify-trust-pages.js --check

Verifiable Evidence Layer

This block is not a narrative claim. Each core assertion has a claim id, source JSON, hash, and a repeatable verification command. Public pages disclose governance evidence without exposing source code, secrets, private data, or exploitable attack details.

Claim IDVerifiable valueStatusOwnerSource and verification
claim.public-url-manifest.indexable-count
Public URL and canonical inventory
38,965 indexable URLs verified sitewide node scripts/generate-public-evidence-manifest.js --dry
claim.trust-pages.audit-pass-rate
Trust page machine audit
180/180 pass verified sitewide node scripts/verify-trust-pages.js --check
claim.discovery-surface.zero-errors
AI discovery surface audit
{"errors":0,"warnings":0} verified sitewide node scripts/verify-discovery-surface.js
claim.structured-data.jsonld-errors
JSON-LD / structured data audit
{"structured_data_invalid_files":0,"breadcrumb_count":28274,"faq_count":27506,"dataset_count":30,"article_count":27406} verified sitewide node scripts/site-machine-audit.js
claim.status.sla-state
Status page SLA source
critical / 5 critical, 0 warnings verified sitewide node scripts/generate-status-page.js
claim.provider-alignment.openai-anthropic-gemini
OpenAI / Anthropic / Google Gemini benchmark alignment
benchmark alignment only unless code/config evidence exists verified sitewide node scripts/verify-public-evidence.js --check
claim.transparency-report.sha256
Transparency report SHA-256 anchor
{"report":"transparency/report-2026-Q3.json","sha256":"47b09e2ca4e8b8fe9dffdfaccef3b11212de9ee3a8a14badca8044e2481203c5"} verified sitewide node scripts/update-transparency-current-data.js
claim.release-integrity.gpg-signing
GPG signing status
GPG signing configured locally; GitHub verification pending github_verification_pending sitewide gpg --list-secret-keys --keyid-format=long && git log -1 --show-signature
claim.accessibility.state-machine-compliance
WCAG state-machine compliance
{"id":"site","entityType":"accessibility","state":"ERROR","createdAt":"2026-04-13T02:57:00.390Z","updatedAt":"2026-07-18T00:25:42.844Z","history":[{"state":"SCANNING","at":"2026-04 needs_review accessibility node scripts/verify-public-evidence.js --check
claim.accessibility.trust-page-coverage
10-language trust-page audit coverage
{"pages":180,"pass":180,"fail":0} verified accessibility node scripts/verify-trust-pages.js --check
claim.accessibility.mobile-overflow-check
Mobile evidence overflow check
{"verifier":"scripts/verify-public-evidence.js","page":"/accessibility/zh-TW"} verified accessibility node scripts/verify-public-evidence.js --check

System Card V2.0: Technical Transparency Layer

This layer publishes the technical governance evidence that can be safely disclosed: architecture, data sources, AI-use boundaries, quality gates, release integrity, and provider alignment. Source code, secrets, exploitable attack details, and private data remain out of scope.

Public architecture

Cloudflare Pages/Workers, R2/D1/KV/Pagefind, and local generation scripts form the public-site and governance publication chain. Public pages disclose behavior, state, and traceable sources, not secrets or internal permissions.

AI-use disclosure

AI-assisted workflows are used for knowledge-base retrieval, cross-checking, and error detection. Governance documents are benchmarked against OpenAI, Anthropic, and Google Gemini public frameworks. Production model usage is disclosed only when code/config evidence exists.

Quality and safety gates

Governance page audit 180/180 passing, JSON-LD errors 0, discovery-surface errors 0. Status pages report critical / 5 critical, 0 warnings as-is.

Data traceability

Knowledge base 32,724 chunks, TM 789,031 entries, AI answer-ready 7,976/7,976. Public metrics trace to data/state-machine/*, data/*audit*.json, and transparency reports.

Governance areaOpenAIAnthropicGoogle GeminiStarnum implementation evidence
Model/system-card disclosureOpenAI models + safety docsClaude model docs + system/model cardsGemini model docs + safety settingssystem-card, model-card, methodology, benchmark, transparency-log
Safety evaluation and use boundariesSafety best practices / deployment checklistResponsible Scaling / safety policyGemini safety controls / policyAI safety, acceptable-use, ethics, risk-boundary copy, crawler policy audit
Data governanceData controls / privacy controlsprivacy and data handling docsGemini API data governance referencesprivacy, ai-data-governance, KB/TM source tracking, SHA-256 hashes
Monitoring and releaseproduction checklist / eval disciplinesystem-card transparency disciplinemodel/version documentation disciplinedeploy.js, status.html, SLA report, trust-pages-machine-audit, sitemap/hreflang audits

The V2.0 goal is not more claims; it separates implemented controls from planned controls. Production usage, benchmark alignment, status exceptions, GPG signing, and SLA breaches are disclosed from source data.

Release Integrity And GPG

GPG signing configured locally. signingkey=0934DFA0EDA6363A. GitHub verification pending until the public key upload and Verified badge are confirmed.

OpenAI / Anthropic / Google Gemini Alignment

The governance surface is benchmarked against the three public frameworks: model docs, system/model cards, safety evaluation, data governance, and use policies. This is benchmark alignment, not a claim that every provider is active in production inference. Official docs checked: 2026-07-30

ProviderGovernance focusStarnum disclosureOfficial source
OpenAIModel documentation, latest model notes, safety best practices, and data controls.No verifiable production model setting was found in the production code scan; providers are listed as governance benchmarks.https://platform.openai.com/docs/models
AnthropicClaude model documentation, system/model cards, Responsible Scaling, and safety policy.No verifiable production model setting was found in the production code scan; providers are listed as governance benchmarks.https://docs.anthropic.com/en/docs/about-claude/models
Google GeminiGemini API model documentation, safety settings, data governance, and platform policy.No verifiable production model setting was found in the production code scan; providers are listed as governance benchmarks.https://ai.google.dev/gemini-api/docs/models