E-mail List Archives
Thread: Accelerated Mobile Pages (AMP)
Number of posts in this thread: 3 (In chronological order)
From: Tomlins Diane
Date: Mon, Aug 08 2016 9:23AM
Subject: Accelerated Mobile Pages (AMP)
No previous message | Next message →
Hello everyone,
Our organization is looking into this new AMP thing from Google - https://www.ampproject.org/docs/get_started/about-amp.html
Briefly, the HTML is described as:
"AMP HTML is a subset of HTML for authoring content pages such as news articles in a way that guarantees certain baseline performance characteristics."
I was asked about the accessibility of AMP, and since it's so new, I haven't found much. However, with specific AMP tags like amp-img and amp-embed and others, I would not expect any screen readers to have any support for these at this time.
Anyone have any thoughts or input on this??
Thanks!!
Diane R Tomlins
From: Patrick H. Lauke
Date: Mon, Aug 08 2016 9:38AM
Subject: Re: Accelerated Mobile Pages (AMP)
← Previous message | Next message →
On 08/08/2016 16:23, Tomlins Diane wrote:
> I was asked about the accessibility of AMP, and since it's so new, I
> haven't found much. However, with specific AMP tags like amp-img and
> amp-embed and others, I would not expect any screen readers to have
> any support for these at this time.
The various amp-specific tags are web components which, in practice,
are turned into "proper" markup.
For instance, https://ampbyexample.com/components/amp-img/ turns into:
<amp-img ...>
<i-amp-sizer ...></i-amp-sizer>
<img ... alt="an image" ... src="/img/amp.jpg">
</amp-img>
And https://ampbyexample.com/components/amp-video/ turns into
<amp-video ...>
<i-amp-sizer ...></i-amp-sizer>
<div fallback="">
<p>Your browser doesn't support HTML5 video.</p>
</div>
<video ...>
<source type="video/mp4" src="/video/tokyo.mp4">
<source type="video/webm" src="/video/tokyo.webm">
</video>
</amp-video>
Accessibility challenges/problems will be the same as those of regular
HTML (such as making sure you provide proper alt for an amp-img, an
appropriate meaningful fallback for amp-video, etc).
(as an aside, it's possible to test all the various amp-specific
constructs directly on that ampybyexample.com demo site, using your
regular desktop/mobile browser/AT, to get an idea of how they'll behave)
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: Tomlins Diane
Date: Mon, Aug 08 2016 9:53AM
Subject: Re: Accelerated Mobile Pages (AMP)
← Previous message | No next message
Thanks Patrick :)
>The various amp-specific tags are web components which, in practice, are turned into "proper" markup.
>Accessibility challenges/problems will be the same as those of regular HTML (such as making sure you provide proper alt for an amp-img, an >appropriate meaningful fallback for amp-video, etc).
> (as an aside, it's possible to test all the various amp-specific constructs directly on that ampybyexample.com demo site, using your regular >desktop/mobile browser/AT, to get an idea of how they'll behave)
Good to know!
>P
--
>Patrick H. Lauke
>www.splintered.co.uk | https://github.com/patrickhlauke
>http://flickr.com/photos/redux/ | http://redux.deviantart.com
>twitter: @patrick_h_lauke | skype: patrick_h_lauke