aria-api 0.2.7 → 0.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -79,9 +79,19 @@ See `matches()` for details.
79
79
 
80
80
  ## closest(element, selector)
81
81
 
82
- Similar to [Element.closest()](https://developer.mozilla.org/en-US/docs/Web/API/Element/closest)
82
+ Similar to [Element.closest()](https://developer.mozilla.org/en-US/docs/Web/API/Element/closest).
83
83
  See `matches()` for details.
84
84
 
85
+ ## getParentNode(node)
86
+
87
+ Similar to [Node.parentNode](https://developer.mozilla.org/en-US/docs/Web/API/Node/parentNode),
88
+ but takes `aria-owns` into account.
89
+
90
+ ## getChildNodes(node)
91
+
92
+ Similar to [Node.childNodes](https://developer.mozilla.org/en-US/docs/Web/API/Node/childNodes),
93
+ but takes `aria-owns` into account.
94
+
85
95
  # What is this for?
86
96
 
87
97
  First of all, I thought that something like this should exist. I currently use
@@ -100,7 +110,7 @@ That said, this is what I think it could also be used for:
100
110
  - [Core Accessibility API Mappings 1.1](https://www.w3.org/TR/core-aam-1.1/)
101
111
  - [HTML Accessibility API Mappings 1.0](https://www.w3.org/TR/html-aam-1.0/)
102
112
  - [WAI-ARIA Graphics Module 1.0](https://www.w3.org/TR/graphics-aria-1.0/)
103
- - [Digital Publishing WAI-ARIA Module 1.0](https://www.w3.org/TR/graphics-aria-1.0/)
113
+ - [Digital Publishing WAI-ARIA Module 1.0](https://www.w3.org/TR/dpub-aria-1.0/)
104
114
  - [Accessible Name and Description Computation 1.1](https://www.w3.org/TR/accname-1.1/)
105
115
 
106
116
  I try to update the code whenever a new version of these specs becomes a
@@ -111,18 +121,23 @@ recommendation.
111
121
  - This is a pet project. I do not have the time to do extensive testing and
112
122
  may skip some details now and then. I am happy to receive bug reports and
113
123
  pull requests though.
124
+ - The standards are still in a very rough state. Many things are
125
+ unclear/undecided and therefore no browser really implements them. So
126
+ naturally, this library cannot really implement the standards either.
114
127
  - This library does not do any validity checks. Invalid attributes or roles
115
128
  will not produce any warnings.
116
129
  - In order to calculate the "hidden" attribute,
117
130
  [Window.getComputedStyle()](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle)
118
131
  is called. This only seems to return reliable values if the element is
119
132
  attached to `document`.
133
+ - Due to security restrictions it is not generally possible to inspect the
134
+ content of iframes, so they are ignored.
120
135
 
121
136
  # Related projects
122
137
 
123
138
  - [Visual ARIA Bookmarklet](http://whatsock.com/training/matrices/visual-aria.htm):
124
139
  Displays role, name, and description in any website. Maintained by one of
125
- the editors of the [accname]() speca.
140
+ the editors of the [accname]() spec.
126
141
  - [axe-core](https://github.com/dequelabs/axe-core/) and
127
142
  [Accessibility Developer Tools](https://github.com/GoogleChrome/accessibility-developer-tools):
128
143
  These are libraries for accessibility testing. They solve many of the same
@@ -133,3 +148,5 @@ recommendation.
133
148
  Draft spec for exposing the accessibility tree to JavaScript.
134
149
  - [chrome.automation](https://developer.chrome.com/extensions/automation):
135
150
  A propriatary API that exposes the accessibility tree to JavaScript.
151
+ - [babelacc](https://xi.github.io/babelacc/):
152
+ A tool to compare the output of different libraries.