James Craig comments

Results 535 comments of


                                            James Craig

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

If so, we may be able to close this one.

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

@twilco brought up a related case where the list markup is invalid, but one or more engines still render the bullet, and therefore may need an exception in the mapping...

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

> @twilco brought up a related case where the list markup is invalid, but one or more engines still render the bullet, and therefore may need an exception in the...

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

Conclusion has been that the UA stylesheet (as defined in HTML) is sufficiently specified behavior to render the bullet. Therefore, HTML-AAM should be updated to expose `` as a list...

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

Perhaps this is a good time to remind the group that [WebKit uses list bullet render style](https://twitter.com/cookiecrook/status/1337226933822603270) as one of a number of heuristic ways to determine whether a list...

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

ARIA spec verbiage could be something like: > ~ In scenarios where multiple implementations render semantic styles (such as a bullet on an invalid list item) or consistently remove semantic...

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

@scottaohara and I discussed this today. Consensus specifically on the **listitem** issue was that HTML-AAM would change verbiage to something like "li where the accessibility parent is a list" (e.g....

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

We did not discuss in detail how this pattern would be applied to contexts beyond list, but I assume @scottaohara plans to do the same for other descendant roles related...

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

More on the "required context" topic here: - https://github.com/w3c/aria/issues/2166 - https://github.com/web-platform-tests/interop-accessibility/issues/120

Add `nameFrom: heading` to AccName text alt algorithm

Dependent upon related ARIA spec change: - https://github.com/w3c/aria/pull/1860