Back to Explore

eps1lon/dom-accessibility-api

GitHub
1 watchersOpen source

Last release: 6 months ago

dom-accessibility-api is a JavaScript implementation of the W3C accname algorithm, used to compute the accessible name and accessible description of a given DOM Element. It is useful for testing and validating how your DOM will be exposed to assistive technologies, with helper functions like computeAccessibleName and computeAccessibleDescription.

Project status

  • The repository appears actively maintained, with an upstream push on 2026-04-19 and a recent update v0.7.1 on 2025-11-27.
  • The apparent update cadence is roughly 1 year between the last few update events (v0.6.3 in 2023-09, v0.7.0 in 2024-07, v0.7.1 in 2025-11), with no evidence of rapid frequent updates.

AI summary generated Today

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

Recent updates

  • v0.7.1

    6 months ago

    v0.7.1 is a patch release focused on changing the release publishing mechanism to use trusted publishing (OIDC). The code diff shows no library logic changes, but it does update CI/publishing workflows and bumps the TypeScript dependency.

    BreakingSecurity

  • v0.7.0

    7/24/2024

    Release v0.7.0 (2024-07-24) focuses on performance by caching `window.getComputedStyle` results during accessible name/description computation. The code adds an in-function cache (when `Map` is available) and also introduces related test coverage for reduced repeated `getComputedStyle` calls.

    Features

  • v0.6.3

    9/18/2023

    Release v0.6.3 makes a packaging-related change to the package.json `exports` map so TypeScript type resolution is prioritized by declaring `types` first. The code diff also includes a large lockfile update (primarily Babel related packages), but no other source-level changes are shown in the provided diff.

  • v0.6.2

    9/17/2023

    v0.6.2 is presented as a patch release focused on improving TypeScript typing resolution for TS ESM usage. The actual diff shows additional build/tooling configuration updates (Babel targets, CI settings) and a large dependency lockfile churn, but the library’s TypeScript source logic changes appear to be formatting-only.

  • v0.6.1

    6/10/2023

    v0.6.1 is a patch release that extends descriptor handling for accessible name and description computation. It adds support for `aria-description` and treats the ARIA role value `none` equivalently to `presentation`.

    Features

  • v0.6.0

    5/7/2023

    Release v0.6.0 adds a new exported helper, `isDisabled`, to detect whether supported HTML elements are disabled via `disabled` or `aria-disabled="true"`. The implementation and tests are added, but the release notes do not mention any of the significant development/tooling dependency upgrades included in this release.

    Features

  • v0.5.16

    1/18/2023

    Release v0.5.16 is a patch release that addresses a maximum call stack size exceeded scenario involving self-referential aria-labelledby relationships. The code change appears to improve recursion/loop prevention when resolving aria-labelledby. In addition, the release includes some tooling and development dependency updates not mentioned in the release notes.

  • v0.5.15

    1/1/2023

    v0.5.15 is primarily a patch release that changes how the library computes accessible names, specifically removing `title` precedence in 2E cases (example given: `<option title="Title">Content</option>`). The diff also contains substantial repository and test/tooling updates (Node/Jest/jsdom/cypress and CI workflow changes) that are not mentioned in the release notes.

    Breaking

  • v0.5.14

    4/25/2022

    v0.5.14 is a patch release that updates accessible name/description behavior when aria-labelledby or aria-describedby reference elements located in the same shadow root. The included code change also adjusts how IDREF targets are resolved by using the node's root (shadow root when available), and adds targeted shadow DOM tests.

  • v0.5.13

    3/1/2022

    v0.5.13 updates accessible name computation to align button handling with the latest editors draft, preferring the button subtree over the button `title` attribute. The main behavioral change is expected to affect `computeAccessibleName` results for certain `<button title=...>...</button>` cases. Additionally, the implementation includes other text normalization changes and build dependency updates not mentioned in the release notes.

    Breaking