There are a handful of attributes that need to be well represented in ChromeVox output:
- for some attribute
- check all supported roles include the attribute (using it in an appropritae way with suitable message strings and prioritized well in relative to the other parts of the output rule).
- customize for braille if needed
Most attributes we get as part of the $staste collection of attributes. However, there are some free-floating attributes (e.g. invalid state) that require more specific formatting / message templating. Another example is posinset/set size.
Comment 1 by bugdroid1@chromium.org
, Dec 13 2017