James Craig

add aria-labelsynonyms

22

closes #1038 *** Preview | Diff

Implementation concerns over Orphaned Role requirements in Core-AAM, HTML-AAM… and possibly elsewhere.

16

### Core-AAM Spec prose: > When an element has a role but is not contained in the required context (for example, an orphaned listitem without the required accessible parent of...

ARIA should clarify distinction between “contents exposed as descendant text nodes” vs “name from contents” (Was: `listitem` should include `name from Contents` or `name prohibited`)

8

ARIA should clarify distinction between “contents exposed as descendant text nodes” vs “name from contents” This conversation started while @twilco was fixing an implementation bug, and noticed the `listitem` role...

"host language attribute" is not defined

4

"host language attribute" is not defined in main ARIA spec (and related) I heard today that a few ARIA veterans didn't know what this was. .... e.g. an HTML or...

Update from PR #1018 for nameFrom: heading

23

Part of #w3c/accname/issues/138 Adds `nameFrom: heading` (this overcomes PR #1018) Will update these along the way after further discussion and review. * [x] Related AccName Issue/PR: https://github.com/w3c/accname/issues/182 * [ ]...

Document interop of misspelled aria-labeledby and its conflict resolution

25

~~All three engines~~ **[WebKit and Chromium]** support a misspelled alternate of `aria-labelledby` without the UK-English-style double `l` (`aria-labeledby`). I think this dates back to a WebKit implementation that Chromium inherited...

Clarify whether author errors in "required accessibility parent/child" (formerly "required context") should be handled by UA

16

In the following Interop Accessibility issue: - https://github.com/web-platform-tests/interop-accessibility/issues/109 @nmlapre rightly calls out that several WPT accessibility "orphan" tests aren't specified in ARIA. ```html x ``` In fact, the [error handling...

Hard to know what the scope is since I haven't been in the convos, but it's clearly not a "screen reader" (for the blind) use case... Where the boundary overlaps...

clarifying existing live region announcement behavior on creation/rendering of new live regions

6

Closes #1216 Codifies existing UA behavior for live regions, especially in the context of creation and initial rendering, where only `alert` live regions are announced. # PR tracking Check these...

Requesting changes to new implementation-blocked merging process

16

I added the **Agenda** label b/c I don't know how to make progress on PR #1860 with the new process expectation, which seems unintentionally circular. - I filed https://github.com/w3c/accname/issues/138 four...