W3C home > Mailing lists > Public > public-aria-practices@w3.org > August 2018

Re: Feedback on new aria-invalid guidance for spin button

From: Michiel Bijl <michiel.list@moiety.me>
Date: Mon, 27 Aug 2018 16:41:02 +0200
Cc: public-aria-practices@w3.org
Message-Id: <A620F0B4-4105-44C2-8F0B-3EE6E55B1C63@moiety.me>
To: Matt King <a11ythinker@gmail.com>
How about something like this:

Most spinbutton implementations will prevent the input of invalid values. But, in some cases blocking invalid input might not be practical. In such scenarios aria-invalid is set to true if the value is outside of the allowed range.

This is pretty close to how I’d write it in an article or some such. I think I kept the information the same and only changed the tone slightly.

Talk soon.
— Michiel

> On 21 Aug 2018, at 01:18, Matt King <a11ythinker@gmail.com> wrote:
> Per our discussion a couple weeks ago of issue 704 which asks questions about the spin button pattern, I created pull request 825 which proposes the following language for the roles, states, and propertie section of the spin button pattern:
> “The spinbutton element has aria-invalid set to true if the value is outside the allowed range. Note that most implementations prevent input of invalid values, but in some scenarios, blocking all invalid input may not be practical.”
> Before I merge, I’d like some feedback. Is the language clear or does it neeed any changes? Please comment in the PR:
> https://github.com/w3c/aria-practices/pull/825
> Thanks,
> Matt
Received on Monday, 27 August 2018 14:41:27 UTC

This archive was generated by hypermail 2.3.1 : Monday, 27 August 2018 14:41:28 UTC