Releases: eps1lon/dom-accessibility-api
v0.7.1
v0.7.0
Minor Changes
-
#1048
d9ad334Thanks @TomPridham! - Cachewindow.getComputedStyleresultsShould improve performance in environments that don't cache these results natively e.g. JSDOM.
This increases memory usage.
If this results in adverse effects (e.g. resource constrained browser environments), please file an issue.
v0.6.3
v0.6.2
v0.6.1
Patch Changes
-
#934
8acefc3Thanks @alonidiom! - Supportaria-descriptionas descriptor -
#933
a593ee0Thanks @jlp-craigmorten! - Support"none"role as a synonym for the"presentation"role
v0.6.0
Minor Changes
- #919
215955eThanks @MatanBobi! - add anisDisabledfunction to check if elements are disabled or not
v0.5.16
v0.5.15
v0.5.14
Patch Changes
- #827
a1daca5Thanks @nolanlawson! - Follow aria-labelledby and aria-describedby if they point to elements in the same shadow root.
v0.5.13
Patch Changes
-
#811
5b0f48eThanks @eps1lon! - Prefer button subtree overtitleattribute.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 thetitleattribute.
computeAccessibleNamenow calculates "from-content" as the accessible name.