Re: HTML5 default implicit semantics

There's also a murky middle ground representing CMS and blog systems where
the main tool may be made from either customised or pre built but
importantly significant  content may be created by anyone and may not be
quality controlled.

Steve Lee
Sent from my mobile device Please excuse typing errors
On 6 Nov 2015 21:23, "White, Jason J" <jjwhite@ets.org> wrote:

>
> > On Nov 6, 2015, at 13:31, John Foliot <john.foliot@deque.com> wrote:
> >
> > Léonie Watson [mailto:lwatson@paciellogroup.com] wrote:
> >>
> >> When ARIA first came into existence we thought it was temporary. We've
> come
> >> a long way since then and ARIA is clearly here to stay. Perhaps this
> means we're
> >> at a good point to reevaluate the overall strategy and roadmap for ARIA?
> >
> > +1 to that.
>
> I think the point was well made at the plenary session at TPAC that there
> are two aspects of Web technology: (1) tools such as APIs, Web Components,
> etc., that allow application authors to create their own customized
> features, e.g., new widgets; and (2) pre-built features for authors to use
> in their applications and documents, for example HTML elements.
>
> The Web needs both, and we need to be able to make both accessible.
>
>
> ________________________________
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
>
> Thank you for your compliance.
>
> ________________________________
>