it’s not immediately clear to me what the advantage of using a would be from an accessibility viewpoint, if you’ve got the written description right there.
Very understated. Having the written fallback for visual users, which then doubles up what the accessibility services see. Frustrating to no end!
Aside: progressbar is a type of meter right? Is a donation goal a progressbar or a meter?
A donation goal is a meter because donations can be exceeded. In fact, exceeding a donation is something to be celebrated, so the client would want to call attention to that fact. In contrast, a progress bar restricts the value to the max value or 1 if no max is given because, conceptually, tasks can only be completed.
<meter>is the one semantic element I understand being replaced by divs because it’s pretty much impossible to style.Very understated. Having the written fallback for visual users, which then doubles up what the accessibility services see. Frustrating to no end!
Aside:
progressbaris a type ofmeterright? Is a donation goal aprogressbaror ameter?A donation goal is a meter because donations can be exceeded. In fact, exceeding a donation is something to be celebrated, so the client would want to call attention to that fact. In contrast, a progress bar restricts the value to the max value or 1 if no max is given because, conceptually, tasks can only be completed.
From
meter’s documentation:Their handling of maximums is functionally the same
Sure, their handling of maximum is the same. But the donation target shouldn’t be modeled as a maximum, but either by the ‘high’ or ‘optimum’ value.