bernard van isacker - phoenixkm - vipi's specific experience in using social media

ViPi’s specific experience in using social media – case study

7 May 2013

Amersveldestraat 189, 8610 Kortemark - Belgium – Tel: 00 32 (0) 51 568570 - www.PhoenixKM.eu – [email protected]

ViPi KA3-ICT network project Background on PhoenixKM What do we want to achieve? How do we do it? How do we use it for project outcomes

dissemination? Caveats/ do’s and don’ts What about accessibility?

Outline


Main specialisation in SEM=SEO+SEA+SMO

o SEO (search engine optimization) o SE(M)A (search engine marketing/advertising) o SMO (social media optimization) o Main clients: insurance and music industry

Social focus: o ICT enabling people with disabilities during education, job seeking and

employment o Special interest in basic ICT and ICT-based assisted technology (AT) skills

training o We coordinate 3 projects:

2 KA3-ICT projects (ViPi – basic ICT skills trainings, SGSCC – post ViPi focused on social competence training using ViPi tools)

1 Leonardo Da Vinci Development of Innovation Project (ATLEC – ICT based assisted technology knowledge)

About us


What do we want to disseminate as a project?

Updates on our project work: news current affairs of projects Surveys or analyses we prepared. Final deliverables that are ready to go out: downloads, software Organisation of an event, either local or European Presentations made at events Pictures of events Videos of the project and or of events Reaching out to press/media Other ideas?

What?


How do we do this?

Reaching out to various stakeholders and

gatekeepers Using various complementary (accessible)

channels And making use of what FREE tools can offer

us

How?


Twitter and aggregators like TweetDeck o Have something meaningful to say

and use hashtags (#) o Re-tweet only project relevant material o Material: 140 character message, image,

sound, video, PDF, image + sound, links o Delivery methods: tweetwall, embedded in

website, rss (FB, Tumblr, ...), data to e-mail

Social media - Twitter

http://tweetdeck.com/


Facebook page (not profile) o Avoid a ratatouille of postings o Make the page attractive o Material: 'unlimited' character message, image

(galleries), tagging, sound, video, PDF, image + sound, links

o Delivery methods: rss (Twitter), video embedding

Social media - Facebook


YouTube channel and videos o Select relevant videos o Videos can be made easily with

smartphones using various apps if needed o Material: video, sound, screencapturing,

captured presentations o Delivery method: embedding, link, rss (FB,

Twitter, ...), channels

Social media - YouTube


SlideShare o Upload your presentations,

newsletters, etc. They transfer to textual versions and are annotated with tags -> Google friendly

o Material: PPT, PDF, documents, video o Delivery method: embedding, rss (FB,

Twitter, ...)

Social media - Slideshare


Social media connections


Twitter : twitter.com/ViPi_project

ViPi Twitter

https://twitter.com/ViPi_project

https://twitter.com/ViPi_project


Facebook : www.facebook.com/vipiproject

ViPi Facebook

https://www.facebook.com/vipiproject

http://www.facebook.com/vipiproject


YouTube : youtube.com/user/AccessForAlleu

ViPi YouTube

youtube.com/user/AccessForAlleu


SlideShare : slideshare.net/phoenixkm

ViPi SlideShare

http://www.slideshare.net/phoenixkm


Don’ts Chase quantity in followers, tweets, likes, etc. Have a say about everything. Share personal data and opinions (religious, political)

Do’s

Ensure you reach those you need to reach (quality) Think before tweeting Don’t pretend to be a “guru”, “expert”, etc. in your

profile.

Do’s & Don’ts


Accessibility social media - common accessibility issues Lack of section headings: screenreader users use the “H”

shortcut to enlist all headings that appear in a website, document or presentation: eg. <h1> instead of <b> and large font size, heading functionalities in MS Word, LibreOffice, ...

Poor colour contrast An inability to navigate using keyboard only: rich internet

applications in Facebook Missing text equivalents for images Inability to resize text Videos lacking captioning (subtitles):very time consuming

(various languages), even we don't always respect it, but it should be a standard procedure

Accessibility issues


Twitter vs. Easy Chirp: accessible via screenreader o http://www.easychirp.com

Facebook vs. m.Facebook: accessible via screenreader o http://m.facebook.com

YouTube vs. Easy YouTube / Accessible YouTube / Amara (subtitles): video functionalities accesible via keyboard

o http://www.cs.unc.edu/~gb/AccessibleYouTube and subtitles using Amara - http://www.universalsubtitles.org/en/

SlideShare vs. EasySlideShare:accessible via keyboard o http://icant.co.uk/easy-

slideshare/?slides=http://urlslideshare

Accessible alternatives

http://www.easychirp.com/

http://m.facebook.com/

http://www.cs.unc.edu/~gb/AccessibleYouTube

http://www.cs.unc.edu/~gb/AccessibleYouTube

http://www.universalsubtitles.org/en/

http://icant.co.uk/easy-slideshare/?slides=http://urlslideshare





Accessible project outcomes Accessible Word doc Accessible PDFs Daisy book versions

Project documents


Contact details

Mr. Bernard Van Isacker Business consultant Mobile: (B) +32 496 334056 Mobile: (GR) +30 6942 868812 Phone: +32 51 568570 E-Mail: [email protected]

Contact us

mailto:[email protected]

bernard van isacker - phoenixkm - vipi's specific experience in using social media

Technology

kortemark belgium tel

social media slideshare

rss twitter

media connections

project work

project outcomesdissemination

emailsocial media twitter

channelssocial media