{"id":170,"date":"2010-10-29T10:00:56","date_gmt":"2010-10-29T14:00:56","guid":{"rendered":"http:\/\/accessibleinsights.info\/blog\/2010\/10\/29\/help-build-an-accessible-apps-library\/"},"modified":"2010-10-29T10:00:56","modified_gmt":"2010-10-29T14:00:56","slug":"help-build-an-accessible-apps-library","status":"publish","type":"post","link":"https:\/\/accessibleinsights.info\/blog\/2010\/10\/29\/help-build-an-accessible-apps-library\/","title":{"rendered":"Help build an accessible apps library"},"content":{"rendered":"
\n

One aspect of the state of usability we refer to as "accessibility" that has irritated me of late is that some have seemed to play pretty fast and loose with the definitions.  Most of us recognize that the term "accessible" has both a connotation and a denotation, both a literal and figurative meaning.  With regard to online web development, there are specific "rules" of engagement as to actual techniques used to accomplish web accessibility.  For many of us, though, we tend toward the most fundamental of all of the meanings:  Can I use it or not?<\/p>\n

  <\/p>\n

There’s a practical aspect to what most users and consumers define as accessible.  For example, to each situation, I apply my "WSA" standard.  I need to be able to access, use or otherwise consume the product, establishment or service without sighted assistance.  That means that from beginning to end, it must be possible for me to complete the entire transaction or task on my own. <\/p>\n

 <\/p>\n

With the above in mind, I’d like to assemble a list of some of my readers favorite accessible apps for blogs, phones, Facebook and Twitter.  I’ve no doubt there are other lists or resources out there, but there is something to be said for a compilation generated by those who have personal experience in real world situations.   <\/p>\n

Before you begin sending in your ideas, though, ask yourself the following:  Does this suggestion rise to the "WSA" threshold?<\/p>\n

  Here are a few stipulations to consider as a guideline when offering your picks:    <\/p>\n

1:  The web site from which you choose the app must be accessible.  This includes the download page.   <\/p>\n

2:  If your pick is a blog app, the dashboard of your blog as well as the app install must be accessible.  No fair asking your brother or your assistant to do the install for you.  If you know how to do it, you must be able to, using your own access software such as a screen reader, puffer, stylus, touch board or whatever.  <\/p>\n

3:  Once installed, you must be able to set up or configure the app to your preferences unassisted.  This also includes the registration process.  <\/p>\n

4:  Once configured, you must be able to use it yourself on your own site, FB page, or phone.  <\/p>\n

If you have to ask someone to read to you the serial number printed on a sticker on the product packaging, or complete the registration procedure or enter the graphical verification key, or download it from the developer site for you, it is not fully accessible. <\/p>\n

 <\/p>\n

So, if your app meets our usability standards from the word "go," as they say, then send me your picks.  Hey, I just installed an FB app that I cannot recommend.  I got all the way done, installed, configured, etc…only to find that, while I can "see" it on my FB page, I cannot use it!  Thanks, FB, for yet another inaccessible tab.  Sigh.  Well, I hope you all enjoy it, because I can’t.  <\/p>\n

anyway, I look forward to reading your favorites.  help me build an accessible apps library that everyone can use.  <\/p>\n

LL      <\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"

One aspect of the state of usability we refer to as "accessibility" that has irritated me of late is that some have seemed to play…<\/p>\n

Continue readingHelp build an accessible apps library<\/span><\/a><\/div>\n","protected":false},"author":145,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[10,8],"tags":[],"class_list":["post-170","post","type-post","status-publish","format-standard","hentry","category-data-mining","category-social-media-mania","entry"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/accessibleinsights.info\/blog\/wp-json\/wp\/v2\/posts\/170","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/accessibleinsights.info\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/accessibleinsights.info\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/accessibleinsights.info\/blog\/wp-json\/wp\/v2\/users\/145"}],"replies":[{"embeddable":true,"href":"https:\/\/accessibleinsights.info\/blog\/wp-json\/wp\/v2\/comments?post=170"}],"version-history":[{"count":0,"href":"https:\/\/accessibleinsights.info\/blog\/wp-json\/wp\/v2\/posts\/170\/revisions"}],"wp:attachment":[{"href":"https:\/\/accessibleinsights.info\/blog\/wp-json\/wp\/v2\/media?parent=170"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/accessibleinsights.info\/blog\/wp-json\/wp\/v2\/categories?post=170"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/accessibleinsights.info\/blog\/wp-json\/wp\/v2\/tags?post=170"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}