E-mail List Archives
Thread: Evaluating Twitter Feed
Number of posts in this thread: 8 (In chronological order)
From: Kathryn.Frederick
Date: Wed, Sep 23 2020 11:45AM
Subject: Evaluating Twitter Feed
No previous message | Next message →
Good Afternoon,
I've been asked if a webpage that features embedded Twitter content is accessible. The content above the heading level 1, prior to the tweets, states something like "Twitter ads and privacy info." So, I'm led to believe this is a native Twitter embed on this page. Can anyone speak to the accessibility, or lack thereof, of this interface? I, as a screen reader user, I can navigate through and past the content, but am trying to find more technical specifications for this situation. When you evaluate the implementation of Twitter/external content, what are you looking for?
In this parcitular instance, the pluses of this Twitter feed are:
* The feed does not auto-refresh; there is a button at the bottom that says "load more tweets."
* Some tweets have headings, but most do not (this isn't consistent)
* A negative is there is no "skip navigation (or other applicable link)". So, an individual either has to tab through all the tweets, or can navigate by headings to read the rest of the page's content.
* Should there not be, at minimum, a "skip tweets," link?
Thank you in advance for any assistance you can provide.
Sincerely,
Katie Frederick, Program Administrator
From: Steve Green
Date: Wed, Sep 23 2020 12:23PM
Subject: Re: Evaluating Twitter Feed
← Previous message | Next message →
When we evaluate the implementation of embedded Twitter/external content, we test it to the same level as the rest of the page.
I don't believe I have ever encountered an embedded Twitter panel that was fully conformant with WCAG 2.1 AA. My understanding is that certain aspects of it are customisable, but we never have admin access to investigate that.
I have encountered some that are effectively a keyboard trap because they keep loading more content as you scroll down, so you can never reach the end. Obviously there is eventually an end, but you may need to tab through thousands of tweets to get there.
Steve Green
Managing Director
Test Partners Ltd
From: Kathryn.Frederick
Date: Wed, Sep 23 2020 12:31PM
Subject: Re: Evaluating Twitter Feed
← Previous message | Next message →
Steve,
Thank you for your feedback. This feed does not auto-refresh, but users must navigate through the tweets, some of which have headings, but most do not, to reach the other content on the page. Thanks again for your perspective.
Katie Frederick, Program Administrator
Bureau of Services for the Visually Impaired
Opportunities for Ohioans with Disabilities
From: Steve Green
Date: Wed, Sep 23 2020 12:37PM
Subject: Re: Evaluating Twitter Feed
← Previous message | Next message →
What I have seen isn't so much an auto-refresh as lazy loading being used to continuously add to the list of tweets as you scroll down. Because this happens below the end of the visible content, you don't even know it is happening. Hopefully yours isn't doing that.
Steve
From: glen walker
Date: Wed, Sep 23 2020 12:50PM
Subject: Re: Evaluating Twitter Feed
← Previous message | Next message →
After you agree to a 30+ page terms and conditions page,
https://developer.twitter.com/en/developer-terms/agreement-and-policy, you
can create a feed via https://publish.twitter.com/. I played with it for a
minute and there aren't many options ("set customization options" button).
You can specify the size (width/height) of the element, a light/dark color
theme, and the language. The feed itself is embedded with an iframe, which
isn't surprising. The language seems to propagate down such that the lang
property is set on the first main <div> in the <body>. The feed always
seems to have a "load more tweets" (or "Weitere Tweets laden" in my German
test case) button at the bottom so there isn't an infinite scroll problem.
But you do have to tab forever to get through it. From a conformance
perspective, tabbing forever isn't a strict failure. From a UX
perspective, it'd be nice to have a "skip tweets area" link.
From: glen walker
Date: Wed, Sep 23 2020 12:51PM
Subject: Re: Evaluating Twitter Feed
← Previous message | Next message →
Also meant to mention you can get some info at
https://help.twitter.com/en/using-twitter/embed-twitter-feed
On Wed, Sep 23, 2020 at 12:50 PM glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> After you agree to a 30+ page terms and conditions page,
> https://developer.twitter.com/en/developer-terms/agreement-and-policy,
> you can create a feed via https://publish.twitter.com/. I played with it
> for a minute and there aren't many options ("set customization options"
> button). You can specify the size (width/height) of the element, a
> light/dark color theme, and the language. The feed itself is embedded with
> an iframe, which isn't surprising. The language seems to propagate down
> such that the lang property is set on the first main <div> in the <body>.
> The feed always seems to have a "load more tweets" (or "Weitere Tweets
> laden" in my German test case) button at the bottom so there isn't an
> infinite scroll problem. But you do have to tab forever to get through
> it. From a conformance perspective, tabbing forever isn't a strict
> failure. From a UX perspective, it'd be nice to have a "skip tweets area"
> link.
>
From: Kathryn.Frederick
Date: Wed, Sep 23 2020 1:01PM
Subject: Re: Evaluating Twitter Feed
← Previous message | Next message →
Thank you, Glen, those were my initial thoughts after looking at it. I appreciate the feedback.
Katie Frederick, Program Administrator
Bureau of Services for the Visually Impaired
Opportunities for Ohioans with Disabilities
From: Kathryn.Frederick
Date: Wed, Sep 23 2020 1:03PM
Subject: Re: Evaluating Twitter Feed
← Previous message | No next message
Thanks for this link. I found it ironic the bookmark/share article buttons weren't labeled. Nevertheless, I appreciate the share. ð
Katie Frederick, Program Administrator