<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Social Media at BU &#187; Engagement</title>
	<atom:link href="http://blogs.bu.edu/socialmedia/tag/engagement/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.bu.edu/socialmedia</link>
	<description>Notes and Ideas from Boston University&#039;s Social Media Communicators</description>
	<lastBuildDate>Tue, 07 May 2013 21:13:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
		<item>
		<title>Accessibility and engagement at #satechBOS</title>
		<link>http://blogs.bu.edu/socialmedia/2011/08/03/accessability-and-engagement-at-satechbos/</link>
		<comments>http://blogs.bu.edu/socialmedia/2011/08/03/accessability-and-engagement-at-satechbos/#comments</comments>
		<pubDate>Wed, 03 Aug 2011 20:40:47 +0000</pubDate>
		<dc:creator>Rebecca Loya</dc:creator>
				<category><![CDATA[Conferences & Events]]></category>
		<category><![CDATA[#satechBOS]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[BU]]></category>
		<category><![CDATA[Ed Cabellon]]></category>
		<category><![CDATA[Engagement]]></category>
		<category><![CDATA[Eric Stoller]]></category>
		<category><![CDATA[Inside Higher Ed]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[Student Affairs]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://blogs.bu.edu/socialmedia/?p=348</guid>
		<description><![CDATA[Last Friday, I attended the Student Affairs Technology Unconference at Boston University, an event bringing together student affairs professionals in higher education to discuss current and future technology trends. Ed Cabellon, the Director of the Campus Center at Bridgewater State University, organized the event and led the ceremonies. Since this was an &#8220;unconference,&#8221; participants voted [...]]]></description>
			<content:encoded><![CDATA[<p>Last Friday, I attended the <a href="http://edcabellon.com/tech/satechbospreview/">Student Affairs Technology Unconference</a> at Boston University, an event bringing together student affairs professionals in higher education to discuss current and future technology trends. <a href="http://twitter.com/#!/EdCabellon">Ed Cabellon</a>, the Director of the Campus Center at Bridgewater State University, organized the event and led the ceremonies. Since this was an &#8220;unconference,&#8221; participants voted on topics online prior to the event. It was more like an open discussion than a conference. <a href="http://satechbos-eorg.eventbrite.com/">Attendees</a> came from all over, including North Carolina and Florida. Some were very proficient in social media, while others were just beginners. Many great topics were covered including analytics, blogging, QR codes, location-based services, SEO, Twitter, LinkedIn, Facebook and privacy. But I&#8217;m going to go into a little more detail about what stood out to me: accessibility and keeping content engaging.</p>
<p><span id="more-348"></span></p>
<p>To be honest, when <a href="http://ericstoller.com/blog/">Eric Stoller</a>, higher ed technology expert, brought up the subject of <a href="http://www.w3.org/WAI/intro/accessibility.php">accessibility</a>, I wasn&#8217;t really sure what that meant. &#8220;Ensuring our websites are usable by people of all abilities and   disabilities is a legal and moral obligation many higher ed institutions   have failed to live up to,&#8221; Eric writes on his blog. When building a school building, you would always think to make it wheelchair accessible, but the same logic usually is not top of mind when thinking about the web. The Internet is a valuable resource, and students who might have auditory, visual or cognitive disabilities should be able to access it too. In addition, making the web more accessible naturally leads to better SEO. Sounds like a win-win to me. The easiest way to get accessibility on the agendas of IT departments, technology vendors, administrators etc. is to start talking about it. Social media provides excellent channels for creating hype, so let&#8217;s get this initiative going!</p>
<p>Next up is student engagement. As a student, it was interesting to hear how higher ed professionals are trying to get my attention online: contests, iPads, blogs, etc. Social media is a very successful way to communicate with students, but only if you&#8217;re doing it right. The first step is to have a plan. Creating the accounts is a start, but a long-term plan and a lot of manpower is required to make those accounts successful. Part of this means giving students opportunities and content they wouldn&#8217;t receive elsewhere. You need to give a reason for your school&#8217;s community to to follow or fan you. Keep content fresh, engaging and be helpful. If a student is tweeting about limited seating in the library, offer them a different place to study or offer to petition for more seating. Become a trusted source for students.</p>
<p>I learned a lot at <a title="#satechBOS" href="http://twitter.com/#!/search/%23satechbos" target="_blank">#satechBOS</a> and if you&#8217;d like to check out more of the discussion, visit the <a href="https://docs.google.com/a/bu.edu/document/d/1HBb3sCxJ5MdmlLkWHRl7tcmhKde12tBSvuqv7Eiw0g4/edit?hl=en_US&amp;pli=1">Google Doc</a> for lots of great resources and coverage.</p>
<p><em>Rebecca is a senior at Boston University studying public relations. Follow her <a title="@BeckyLoya" href="http://twitter.com/BeckyLoya" target="_blank">@BeckyLoya</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.bu.edu/socialmedia/2011/08/03/accessability-and-engagement-at-satechbos/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
