Finally, I found some time to explore Twitter's @anywhere. The Drupal module that implements this new product is Twitter @Anywhere. Although it is a beta module, I have not experienced any problems with it. What is @anywhere, and is it different than other Twitter modules?

The Twitter project uses the older Twitter REST API, which also used OAuth 1 for authentication. The @anywhere API switches much of the load to the client side by using more JavaScript widges. By switching to OAuth 2, the new API significantly reduces the live of the credentials. The latter is an important secrity step for those users who never log off Twitter after making a connection. For a public computer, this means the connection could be hijacked by the next user of the machine.

If you look at a the right column of this page, you do not see a lot of difference. There is, however, another difference that is not so obvious. The current module includes the following options:

• Hovercards - When you are on the Twitter site, you will notice that a little context-aware box appears when you  hover the mouse over a Twitter account, such as @pagevisions. This card allows you to follow, unfollow, or toggle device updates.
• Auto-linkification -  Instead of Hovercards, @pagevisions would be an automatic link to PageVisions Twitter account page.

Whether you use hovercards or auto-linkification (what a name), your page now has a link to the Twitter account. Of course, there is a minor technical problem. Neither of these features make a page more accessible to the visually impaired. On the other hand, they shouldn't confuse a screen reader. Only checking this page using various accessibility tools will give a preliminary answer to that question. The final answer awaits the response by those with visual impairements who use assitive devices.