-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider allowing CSS inline
display to modify the whitespace character joins in accessible name computation
#225
Comments
I think Bryan's summary was that inlines would concat without space.
and "block-like" values (pretty much every display value besides
Bryan's thought was this also applies to pseudo elements, but the Again, I'm not yet sure if this is implementable, and there are a number of other open questions... |
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, then there might be a need to revisit the idea of a CSS-AAM spec. |
CSS's most current definition of how to most correctly convert to plaintext is here btw: https://www.w3.org/TR/css-text-4/#plaintext |
Thanks @fantasai... that and the cross-referenced section, CSS Text: 4.3.1. Phase I: Collapsing and Transformation, seem like the most promising path forward. |
Discussed in today's meeting: https://www.w3.org/2024/02/01-aria-minutes.html#t05 |
From another PR that I'm mostly gutting due to merge conflicts and an inability to land on consensus in time for the looming AccName CR.
Presumably the interior contents would be promoted for "adjacency" consideration?
Originally posted by @cookiecrook in #168 (comment)
The text was updated successfully, but these errors were encountered: