Back to Explore

A11yance/axobject-query

GitHub
2 watchersOpen source

Last release: 2024-07-10

axobject-query provides programmatic access to an approximate Chrome AXObject Model and maps AXObject concepts to the WAI-ARIA 1.1 roles model. It includes utilities like AXObjects for working with the mapped objects and their related HTML and ARIA concepts, useful when you need a semantic layer representation as exposed to assistive technology.

Project status

  • Maintenance status: Evidence suggests the repo is not actively maintained now. The last upstream push was 2024-12-17, and no further updates are shown after that relative to 2026-06-09 (suggesting a quiet or maintenance-mode period rather than ongoing development).
  • Apparent update cadence: Updates cluster in mid-2024 (notably multiple versions in early to mid July 2024), then activity appears to stop after late 2024-12. There is no evidence of steady cadence closer to today.

AI summary generated 2026-06-09

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v4.1.0

    2024-07-10

    No release notes were provided in the supplied release metadata for v4.1.0. The code diff for v3.2.4 -> v4.1.0 shows a semantic change to the AX object model data (DisclosureTriangleRole), plus build and dependency/tooling updates.

  • v3.2.4

    2024-07-02

    No release notes were provided for v3.2.4, so documented changes cannot be verified. The available code diff content shows substantial internal test refactoring rather than a user-facing feature description.

  • v3.2.3

    2024-07-01

    Release v3.2.3 (from v3.2.2) removes the deep-equal-json dependency from runtime code and replaces its usage in elementAXObjectMap with a bespoke attribute-array comparison function. The iterator-based test expectation for elementAXObjectMap changes (length from 70 to 71), indicating a behavioral/data-level change not described in the provided release notes.

  • v3.2.2

    2024-06-22

    v3.2.2 appears to restore backwards compatibility that was broken in v3.2.0, primarily by switching the library used for deep equality comparisons (from dequal to deep-equal-json). The diff also shows a major internal tooling change, migrating the test runner setup away from Jest-based scripts toward Tape plus Babel-based execution.

  • v4.0.0

    2023-09-25

    Release v4.0.0 was published, but no release notes were provided by the publisher. As a result, the specific code changes and potential upgrade impacts (API, behavior, fixes) are not documented in the available release data.

  • v3.2.1

    2023-06-13

    Release v3.2.1 primarily bumps the package version metadata and updates the dependency lockfile. The provided release notes do not include any described functional changes.

  • v3.2.0

    2023-06-13

    Release v3.2.0 appears to be an ARIA and HTML mapping audit with expanded role coverage and improved test assertions. The code diff shows a switch in internal deep equality logic (deep-equal to dequal), new accessibility mappings (TextAreaRole, additional DisclosureTriangleRole concepts), and Flow type tightening.

    BreakingFeatures
  • v3.1.1

    2022-10-23

    This v3.1.1 release does not include any implementation code changes in the diff provided. The only changes are metadata updates, including a version bump in package.json and package-lock.json, and an expansion of CHANGELOG.md text.

  • v3.1.0

    2022-10-23

    Release v3.1.0 contains substantial internal refactors centered around making several AX mapping objects iterable via Symbol.iterator, along with new tests covering the behavior. The diff also changes elementAXObjectMap lookup semantics by switching key comparison to deep equality, and updates CI tooling configuration (eslint parser and GitHub Actions Node versions).

  • v3.0.1

    2021-10-04

    Release v3.0.1 was published on 2021-10-04, but the publisher did not provide any release notes for this version. Without documented changes, developers should review the corresponding commit diff and changelog (if available in the repo) before upgrading to understand potential behavioral or compatibility impacts.