James Craig

Apologies if this had previously been covered, but does "zbl" include _only_ Bliss at the exclusion of the overlapping ARASAAC symbol set? Assuming the goal is language-independent communication, why shouldn't...

I agree that Ruby (see collapsed example in OP) would be a great way to approach this, and perhaps even polyfill-prototyped (short term solution) with a custom CSS font that...

@r12a wrote: > > I agree that Ruby (see collapsed example in OP) would be a great way to approach this, > > Did you read the earlier part of...

@russellgalvin wrote: > The point is that you never have to update an alphabet whereas a dictionary has to be regularly updated with new vocabulary. There is no thought that...

Agenda+ since this is coming up in the context of the Interop Accessibility Focus Area

@w3c/aria-editors please add new milestone for 2024... Need to resolve this for Interop 2024 so we don't have to pull out the WPT tests from the [Accessibility Focus Area](https://github.com/web-platform-tests/interop-accessibility/issues/115).

FWIW, we did remove/change the nbsp tests in WPT, because the ARIA spec resolved on ASCII whitespace, which does not include non-breaking space.

@smhigley, @accdc, and @MelSumner would be good reviewers.

I think Bryan's summary was that inlines would concat without space. `foobar` = "foobar" `foo bar` = "foo bar" (interior space between inline elements meaningful) and "block-like" values (pretty much...

If the solution gets complicated enough, such as a table listing all the CSS display values (or other properties for that matter) and how they affect Accessibility API related mappings,...