You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add builtin actions (this is internally a bitflag, maybe a11y_actions: "focus, blur, ...").
Add custom actions for screenreaders to announce. (not sure how to represent these as a string for attributes lol)
Respond to actions (requires a new event on nodes like onaccessibilityaction).
Add some sort of ID system or similar for handling accessibility node associations.
Measure inline text spans (word measurements, sentence measurements, etc...) and integrate them with AccessKit's APIs. Currently we just add a name property to label/paragraph elements with the inner text of the element, however the ideal way to do this is to have each text span be its own InlineTextBox accessibility node.
a11y_named_by
,a11y_described_by
,a11y_radio_group
, etc...). Requires some sort of ID system (see below).a11y_actions: "focus, blur, ..."
).onaccessibilityaction
).name
property tolabel
/paragraph
elements with the inner text of the element, however the ideal way to do this is to have each text span be its ownInlineTextBox
accessibility node.- [ ]onblur
,onfocus
events.SetSequentialFocusNavigationStartingPoint
andBlur
actions for focusable nodes.UseFocus::validate_globalkeydown
only validates if keyboard focused. #883).use_focus
a11y_auto_focus
#878)freya_components
accessible and at least on par with ARIA-compliant widgets.I'm not fully up to date on the state IME support, but anything lacking in that area can also be thrown here.
The text was updated successfully, but these errors were encountered: