- From: John Foliot <john.foliot@deque.com>
- Date: Fri, 5 Apr 2019 10:05:21 -0500
- To: "lisa.seeman" <lisa.seeman@zoho.com>
- Cc: public-personalization-tf <public-personalization-tf@w3.org>
Received on Friday, 5 April 2019 15:06:13 UTC
Hi Lisa, This is exciting news. One point however - I think "field" as an attribute is redundant and not required. What we need is a mechanism for unequivocally stating the purpose *of a field*, but the field itself is programmatically created with the <input> element (a strong semantic), and helper apps should be able to determine that an input is a field via that semantic alone. For example, we'd never consider <p purpose="paragraph">, and so I remain unclear why we need/want <input purpose="data-field">. Is there a use-case you have in mind that would require a mechanism for indicating "data-field"? JF On Fri, Apr 5, 2019 at 9:41 AM lisa.seeman <lisa.seeman@zoho.com> wrote: > There is a Eurovision Hackathon that would like to implement our work. > They want everyone to enjoy and vote in the Eurovision contest! This will > count as a significant independent implementation! > Unfortunately we would really need to close the implementation for them. > They would use the action, feild, destination, symbol, easylang alternative > and numberfree alterative and maybe literal! > > > All the best > > Lisa Seeman > > LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter > <https://twitter.com/SeemanLisa> > > > > -- *​John Foliot* | Principal Accessibility Strategist | W3C AC Representative Deque Systems - Accessibility for Good deque.com
Received on Friday, 5 April 2019 15:06:13 UTC