Relax aria-valuenow requirement on slider role

[adampage]

Closes #2260

Relaxes a requirement for the slider role by permitting authors to omit aria-valuenow in favor of aria-valuetext alone.

I purposefully left the adjacent “browsers MAY implement the repair techniques...” statement unchanged, as well as the slider-specific repair technique that it cross-references. Both still seemed compatible with this change.

My introduction of “or” in the slider’s Required States and Properties cell on line 7738 looks unprecedented in the spec in terms of its format. I’d be grateful for the editors to weigh in on that?

Test, Documentation and Implementation tracking

Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.

• "author MUST" tests:
• "user agent MUST" tests:
• Browser implementations (link to issue or commit):
  • WebKit:
  • Gecko:
  • Blink:
• Does this need AT implementations?
• Related APG Issue/PR:
• MDN Issue/PR:

---

Preview | Diff

[netlify]

✅ Deploy Preview for wai-aria ready!

Name	Link
🔨 Latest commit	6475927
🔍 Latest deploy log	https://app.netlify.com/sites/wai-aria/deploys/66aae5d62ba13900080b84d7
😎 Deploy Preview	https://deploy-preview-2290--wai-aria.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[adampage]

Hi @daniel-montalvo, could you advise me on this prettier error?

[daniel-montalvo]

Thanks @adampage I approve this since it is coming from a fork.

@pkra This is complaining because it can't find the branch relax-aria-valuenow, which I guess makes sense because this is coming from a fork. Is this expected behavior?

In any case, weren't we supposed to disable prettier for ARIA for now?

[spectranaut]

Thanks @adampage I approve this since it is coming from a fork.

@pkra This is complaining because it can't find the branch relax-aria-valuenow, which I guess makes sense because this is coming from a fork. Is this expected behavior?

In any case, weren't we supposed to disable prettier for ARIA for now?

I opened an issue for the prettier issue: #2294

[scottaohara]

added some suggested text to clarify the aria-valuenow repair should only occur if both aria-valuetext and aria-valuenow are missing.

I'd also like to see user agent or AT SHOULD NOT expose an aria-valuenow fallback value if the aria-valuetext is specified but aria-valuenow is not. For instance, in my recent testing i recall screen readers (though don't remember exactly which ones) would expose a fallback value when aria-valuenow wasn't specified (usually a 50%)

[adampage]

I'd also like to see user agent or AT SHOULD NOT expose an aria-valuenow fallback value if the aria-valuetext is specified but aria-valuenow is not.

Here’s a stab at that, @scottaohara.

[adampage]

Heya @jnurthen, quick editors question: I just noticed that the spec seems to prefer “user agents” over “browsers” for normative statements? I found only 2 matches for \bBrowser(s)?\s+(MAY|SHOULD|MUST)\b versus 77 for user agent(s).

One of those 2 “browser” matches was in this PR’s slider section, so I swapped it out in this latest commit. Would it be scope creep for me to just take care of the last remaining one (in the scrollbar section).

[smhigley]

With that additional change/comment, LGTM!