The ANARI SDK is a comprehensive implementation of the Khronos ANARI (ANother API for Rendering and Imaging) standard, designed for scientific visualization rendering. It provides a core C/C++ frontend library, multiple device backends including a CPU reference renderer (helide using Embree), an experimental GPU backend (helide_gpu using SDL3 GPU), a remote rendering device over TCP, a debugging/serialization device, and a no-op sink device. The SDK also includes a Conformance Test Suite (CTS) for validating device correctness via image-based comparisons (SSIM/PSNR), a reusable base framework (Helium) that abstracts common device implementation patterns (parameter management, deferred commits, object lifecycle), code generation tools that produce C++ code from JSON extension definitions, and an OpenUSD Hydra render delegate plugin for integration with Pixar's USD ecosystem. Additionally, it ships example applications (viewer, capability analysis tool, Blender add-on) and a rich set of test scenes for performance and correctness testing.
The w3c/html-aria repository maintains the ARIA in HTML W3C specification — a normative document defining which ARIA roles, states, and properties are permitted on each HTML element, plus the implicit ARIA semantics of native HTML. It is not a conventional application; it is a standards artifact with engineered supporting infrastructure: a ReSpec-based spec source (`index.html`) auto-published to gh-pages via GitHub Actions, a corpus of standalone HTML conformance test pages in `tests/`, and a cross-tool implementation report in `results/implementation-results.html`. The repo functions as the authoritative rulebook that accessibility conformance checkers (Nu HTML Validator, axe-core, IBM Equal Access, ARC Toolkit) implement against, so its 'production output' is normative rules consumed by validator software. The test corpus encodes each normative rule as a discrete, self-contained HTML page with explicit pass/fail expectations — for example, pages verifying that `aria-hidden="true"` is forbidden on focusable elements, that `aria-rowspan` must not coexist with a native `rowspan`, and which roles are allowed on `button`, `summary`, `img`, and `li`. The implementation report tracks, per rule and per vendor tool, whether the rule is implemented (yes/partial/missing), linking to tool-specific GitHub issues. The contribution workflow enforces cross-repo coordination: normative changes require a corresponding web-platform-tests PR and coordination with checker maintainers before merging, which is an unusually well-governed process for a spec repository. Maintenance is steady: commits continue through late 2026, the implementation report was updated in March 2026, Dependabot monitors GitHub Actions, and the W3C auto-publish pipeline runs on every push. Technical drift is low — the spec deliberately tracks the WHATWG HTML Living Standard, deprecates (rather than abandons) outdated ARIA features, and is built on the actively maintained ReSpec toolchain. The main fragility is external: implementation gaps in vendor checkers are documented openly in the report, and cross-repo synchronization with WPT and checker projects creates coordination risk, but the repo itself is current and professionally curated.