This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
See Issue 442: http://www.w3.org/WAI/PF/Group/track/issues/442 Raised at the F2F on May 5th. I checked the minutes but there is nothing more substantive there than what is in the issue: http://www.w3.org/2011/05/05-pf-minutes.html
Copying in the discussion: MC: aria-valuemax and aria-valuemin CS: editorial clarification that the MUST clause is for authors not user agents JC: always represent value of sliders as floating point between 0 and 1 CS: they can be set on Windows to any value JC: if author doesn't expose aria-valuetext, calculate percentage between 0 & 1 and speak that MC: aria-valuemin and aria-valuemax seem straightforward ... aria-valuetext overrides aria-valuenow <MichaelC_SJO> issue: should aria-valuetext override aria-valuenow at the AAPI level, or should they be separately mapped so AT can choose <trackbot> Created ISSUE-442 - Should aria-valuetext override aria-valuenow at the AAPI level, or should they be separately mapped so AT can choose ; please complete additional details at http://www.w3.org/WAI/PF/Group/track/issues/442/edit . MC: In UAIG, for MSAA and IA2, aria-valuetext overrides aria-valuenow
Filed FF bug: https://bugzilla.mozilla.org/show_bug.cgi?id=672202
Removed sentence from S&P mapping table that advises to use a string version of aria-value now for aria-text if aria-text is not provided.
REOPENED Please see https://bugzilla.mozilla.org/show_bug.cgi?id=672202#c6 "We give valuetext precedence at the MSAA level, and it seems to me we expose the numerical value via IA2 (IAccessibleValue). I believe this bug to be invalid." Andi I think we need to update the guide.