Re: @purpose

Hi John, Charles, all,

On 12/04/2021, 21:09, "John Foliot" <john@foliot.ca> wrote:
> The concerns:
> 1. I thought our attribute could be used on more than just an input type of text - in fact, that is one of the primary benefits to me, as @autocomplete cannot be applied to <select>, <legend> (or an aria grouping for radio buttons or check-boxes), nor radio buttons or checkboxes. As such I believe we need to re-author or modify the opening paragraph to better explain that the @purpose attribute can be applied to *ANY* form input. (Open question: can it be applied to a div marked as content editable?)

I think it'd be a good idea to make the @purpose attribute applicable to more form fields. In fact, I have been drafting an email over the past couple of days which I will send imminently that ties in with this and asks if we should consider going even further.

> 2. The last paragraph - do we really anticipate a space separated collection of values for @purpose? Can anyone bring forth a use-case? (I can't), and so we may have to remove that final sentence (which also restates that there is no default value - so we need to tighten that text up anyway).

I'm interested as to what everyone thinks about this. I can't think of a reason to have more than one purpose on a single input (or valid grouping) but I defer to your and others' experience.

best regards,


Matthew
-- 
Matthew Tylee Atkinson
--
Senior Accessibility Engineer
TPG Interactive
https://www.tpgi.com

A Vispero Company
https://www.vispero.com

--
This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.

Received on Wednesday, 14 April 2021 12:43:19 UTC