Bugzilla

(In reply to Erik Nordin [:nordzilla] from comment #2)
> What do you all think?

Per the [WAI ARIA specification](https://www.w3.org/TR/wai-aria/): 
> A few properties, such as aria-activedescendant, aria-valuenow, and aria-valuetext are expected to change often.
And [aria-valuetext](https://www.w3.org/TR/wai-aria/#aria-valuetext) is specifically created for a fixed range of values, `for example, on a range widget such as a slider or progress bar` which gives a very limited set of use cases. Those use cases likely will have pre-selected measurements, like `%`. While there could be examples of custom set of values that would need l10n, like `small`, `medium`, and `large` for sizing, this still could be manually localized by Fluent's attributes. 

The implementation right now silently removes `aria-valuetext` from the DOM, no errors thrown. At the same time, the example that I am working on now (which could be [the lucky 13th instance](https://searchfox.org/mozilla-central/search?q=aria-valuetext&path=&case=false&regexp=false)), has a set of 12 pre-localized values (months) that is just being reused across the Datepicker and MonthYear Spinner. Fluent also does allow a non-localized string to be assigned to the `aria-valuetext` when the widget is mutated, so the rule here is not strictly enforced.

I submitted a patch, just in case :)

(In reply to Erik Nordin [:nordzilla] from comment #2)
> What do you all think?

Per the [WAI ARIA specification](https://www.w3.org/TR/wai-aria/): 
> A few properties, such as aria-activedescendant, aria-valuenow, and aria-valuetext are expected to change often.

And [aria-valuetext](https://www.w3.org/TR/wai-aria/#aria-valuetext) is specifically created for a fixed range of values, `for example, on a range widget such as a slider or progress bar` which gives a very limited set of use cases. Those use cases likely will have pre-selected measurements, like `%`. While there could be examples of custom set of values that would need l10n, like `small`, `medium`, and `large` for sizing, this still could be manually localized by Fluent's attributes. 

The implementation right now silently removes `aria-valuetext` from the DOM, no errors thrown. At the same time, the example that I am working on now (which could be [the lucky 13th instance](https://searchfox.org/mozilla-central/search?q=aria-valuetext&path=&case=false&regexp=false)), has a set of 12 pre-localized values (months) that is just being reused across the Datepicker and MonthYear Spinner. Fluent also does allow a non-localized string to be assigned to the `aria-valuetext` when the widget is mutated, so the rule here is not strictly enforced.

I submitted a patch, just in case :)