Skip to content

[Snyk] Upgrade dom-accessibility-api from 0.4.7 to 0.5.14 #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

[Snyk] Upgrade dom-accessibility-api from 0.4.7 to 0.5.14 #5

wants to merge 1 commit into from

Conversation

@whitedragon206
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade dom-accessibility-api from 0.4.7 to 0.5.14.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 15 versions ahead of your current version.
  • The recommended version was released 6 months ago, on 2022-04-25.
Release notes
Package name: dom-accessibility-api
  • 0.5.14 - 2022-04-25

    Patch Changes

    • #827 a1daca5 Thanks @ nolanlawson! - Follow aria-labelledby and aria-describedby if they point to elements in the same shadow root.
  • 0.5.13 - 2022-03-01

    Patch Changes

    • #811 5b0f48e Thanks @ eps1lon! - Prefer button subtree over title attribute.

       const name = computeAccessibleName(<button title="from-title">from-content</button>);
-'from-title' === name
+'from-content' === name

      <button title="from-title">from-content</button> would previously compute the accessible name "from-title".
      This is correct in ACCNAME 1.2 but is changed in the latest editors draft.
      The latest editors draft specifically refers to HTML-AAM which says that the subtree should take precedent over the title attribute.
      computeAccessibleName now calculates "from-content" as the accessible name.

  • 0.5.12 - 2022-02-21

    Patch Changes

    • #800 de554b0 Thanks @ pablo-abc! - Remover circular dependency, which fixes warnings thrown in certain environments.
  • 0.5.11 - 2022-01-27

    Patch Changes

    • #796 cb38778 Thanks @ calebeby! - <input type="number" /> now maps to role spinbutton (was textbox before).
  • 0.5.10 - 2021-10-29

    Patch Changes

    • #770 7066180 Thanks @ eps1lon! - Allow computing name for inaccessible elements

      This is mainly targetted at integration with @ testing-library/dom.
      But it can also be used as a general performance boost when used in a JSDOM environment.
      The rationale is that most elements are part of the a11y tree.
      In those cases computing a11y tree exclusion is wasted.
      Since it's expensive, we can disable it.
      The recommendation is to only ignore a11y tree inclusion locally and specifically
      enable it for the tests where you do know that a11y tree inclusion will play a role.

  • 0.5.9 - 2021-10-18

    Patch Changes

    • #762 b3e4a17 Thanks @ eps1lon! - Compute name from author for menu role.

      Previously we wouldn't compute any name for menu to pass some web-platform-tests that covered an exotic use case.
      Now we correctly respect name from author (e.g. aria-label or aria-labelledby).

  • 0.5.8 - 2021-10-08

    Patch Changes

  • 0.5.7 - 2021-08-05

    Patch Changes

  • 0.5.6 - 2021-06-03

    Patch Changes

    • #666 26ee73d Thanks @ eps1lon! - Consider <label /> when computing the accessible name of <output />

      Given

      <label for="outputid">Output Label</label> <output id="outputid"></output>

      Previously the accessible name of the <output /> would ignore the <label />.
      However, an <output /> is labelable and therefore the accessible name is now computed using <label /> elements if they exists.
      In this example the accessible name is "Output Label".

  • 0.5.5 - 2021-05-31

    Patch Changes

    • #627 0485441 Thanks @ eps1lon! - Ensure certain babel helpers aren't required

      Source:

      -const [item] = list;
+const item = list[0];

      Transpiled:

      -var _trim$split = list.trim().split(" "),
-_trim$split2 = _slicedToArray(_trim$split, 1),
-item = _trim$split2[0]
+var item = list[0];

    • #629 383bdb6 Thanks @ eps1lon! - Use label attribute for naming of <optgroup> elements.

      Given

      <select>
	<optgroup label="foo">
		<option value="1">bar</option>
	</optgroup>
</select>

      Previously the <optgroup /> would not have an accessible name.
      Though 2D in accname 1.2 could be interpreted to use the label attribute:

      Otherwise, if the current node's native markup provides an attribute (e.g. title) or element (e.g. HTML label) that defines a text alternative, return that alternative [...]

      This was confirmed in NVDA + FireFox.

  • 0.5.4 - 2020-10-09
  • 0.5.3 - 2020-09-28
  • 0.5.2 - 2020-08-26
  • 0.5.1 - 2020-08-20
  • 0.5.0 - 2020-08-10
  • 0.4.7 - 2020-07-30
from dom-accessibility-api GitHub release notes
Commit messages
Package name: dom-accessibility-api
  • ce7b5e3 release: 0.5.14 (#828)
  • ee39387 test: Run with Node 18, drop 12 (#829)
  • 252ee23 chore(deps): bump jest-junit to ^13.0.0 (#825)
  • a1daca5 fix: Follow aria-labelledby and aria-describedby if they point to elements in the same shadow root (#827)
  • bc4c891 chore(deps): bump @ types/react to ^18.0.0 (#826)
  • 9e469cf chore(deps): bump react to ^18.0.0 (#823)
  • eb41881 chore(deps): bump concurrently to ^7.0.0 (#821)
  • 8ae3b57 chore(deps): lock file maintenance (#820)
  • 6d12652 chore(deps): bump minimist to ^1.2.2 [security] (#818)
  • 5165ead chore(deps): bump actions/checkout action to v3 (#814)
  • 22e4074 chore(deps): bump minimatch to ^5.0.0 (#808)
  • d59462c chore(deps): bump changesets (#819)
  • 2cd2f6c chore(deps): bump node.js to 16.14.2 (#816)
  • 1c67898 release: 0.5.13 (#813)
  • 5b0f48e fix: Prefer button subtree over `title` attribute (#811)
  • a0a0d81 chore(deps): lock file maintenance (#812)
  • 98284fd chore(release): 0.5.12 (#809)
  • de554b0 fix: Remove circular dependency (#800)
  • 42cd189 chore(deps): bump changesets (#807)
  • 9f8a7f9 chore(deps): bump @ babel/core to ^7.14.3 (#806)
  • b92159e chore(deps): bump babel to ^7.14.3 (#803)
  • 5a8cb7a chore(deps): bump node.js to 16.14.0 (#805)
  • 6aa1dbd chore(deps): lock file maintenance (#799)
  • bcc93a6 chore(deps): bump node.js to 12.22.10 (#801)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@whitedragon206 @snyk-bot