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
As part of API improvements to make description implementation more streamlined, a conversation for a solution for auto-populating the accessible name with the visual name was started in #1526
I am hoping we can do something similar for the auto-rounding numeric values that are accessible in the PDOM.
The visually displayed values are rounded, so this should be easy to align.
AND, where numeric values are not visually displayed, but are still accessible via the PDOM, it would be helpful to make these values human readable through rounding to 2 or 3 decimal places. Could we capture these additional numeric values as well with an auto-rounding process?
This would be ideal for Alternative Input and Tier 1 description.
The text was updated successfully, but these errors were encountered:
As part of API improvements to make description implementation more streamlined, a conversation for a solution for auto-populating the accessible name with the visual name was started in #1526
I am hoping we can do something similar for the auto-rounding numeric values that are accessible in the PDOM.
The visually displayed values are rounded, so this should be easy to align.
AND, where numeric values are not visually displayed, but are still accessible via the PDOM, it would be helpful to make these values human readable through rounding to 2 or 3 decimal places. Could we capture these additional numeric values as well with an auto-rounding process?
This would be ideal for Alternative Input and Tier 1 description.
The text was updated successfully, but these errors were encountered: