WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Landmarks versus HTML microdata?

for

From: Steve Faulkner
Date: Sep 27, 2020 9:59AM

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 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 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 REMOVED>
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >