E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 3 (In chronological order)

From: Wing Kuet
Date: Sun, Sep 27 2020 2:54AM
Subject: Landmarks versus HTML microdata?
No previous message | Next message →

Does anyone have any opinion of HTML microdata being used to comply with WCAG 1.3.6 Identity Purpose? At the moment I am advising a client that Aria landmarks are used to identify regions of a page but if microdata is introduced is that an addition to the landmarks or an alternative to landmarks?


Regards,

Wing Kuet
Accessibility Consultant & Software Tester
Test Partners Ltd
= EMAIL ADDRESS REMOVED =

From: Birkir R. Gunnarsson
Date: Sun, Sep 27 2020 9:51AM
Subject: Re: Landmarks versus HTML microdata?
← Previous message | Next message →

For 1.3.5/1.3.6 to be effective we must use mechanisms that are
standardized and can be interpreted by user agents.
Landmarks are standard and interpretable by user agents today, at
least most of them, and are a core part of the HTML standard. So I
would focus on that for identifying regions. I don't know much about
micro data, time to learn.
My understanding is that this is author specific markup that can be
put in for submitting data or encoding information on the author's
website. It's not standardized and is therefore not useful for
1.3.5./1.3.6

On 9/27/20, Wing Kuet < = EMAIL ADDRESS REMOVED = > wrote:
> Does anyone have any opinion of HTML microdata being used to comply with
> WCAG 1.3.6 Identity Purpose? At the moment I am advising a client that Aria
> landmarks are used to identify regions of a page but if microdata is
> introduced is that an addition to the landmarks or an alternative to
> landmarks?
>
>
> Regards,
>
> Wing Kuet
> Accessibility Consultant & Software Tester
> Test Partners Ltd
> = EMAIL ADDRESS REMOVED =
> > > > >


--
Work hard. Have fun. Make history.

From: Steve Faulkner
Date: Sun, Sep 27 2020 9:59AM
Subject: Re: Landmarks versus HTML microdata?
← Previous message | No next message

Microdata is not exposed as accessibility information, no assistive
technology makes use of it.
--

Regards

SteveF
Accessibility is political[image: ✊]
Working for the web
<https://twitter.com/stevefaulkner/status/940835584410574850>,
anywhere and everywhere [image: 🖖🏽]


On Sun, 27 Sep 2020 at 16:51, Birkir R. Gunnarsson <
= EMAIL ADDRESS REMOVED = > wrote:

> For 1.3.5/1.3.6 to be effective we must use mechanisms that are
> standardized and can be interpreted by user agents.
> Landmarks are standard and interpretable by user agents today, at
> least most of them, and are a core part of the HTML standard. So I
> would focus on that for identifying regions. I don't know much about
> micro data, time to learn.
> My understanding is that this is author specific markup that can be
> put in for submitting data or encoding information on the author's
> website. It's not standardized and is therefore not useful for
> 1.3.5./1.3.6
>
> On 9/27/20, Wing Kuet < = EMAIL ADDRESS REMOVED = > wrote:
> > Does anyone have any opinion of HTML microdata being used to comply with
> > WCAG 1.3.6 Identity Purpose? At the moment I am advising a client that
> Aria
> > landmarks are used to identify regions of a page but if microdata is
> > introduced is that an addition to the landmarks or an alternative to
> > landmarks?
> >
> >
> > Regards,
> >
> > Wing Kuet
> > Accessibility Consultant & Software Tester
> > Test Partners Ltd
> > = EMAIL ADDRESS REMOVED =
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >