Friday, July 20, 2012

Next Canberra Gov 2.0 event, 14 August - take a walk on the web side with two fantastic speakers

Pia Waugh is organising the next Gov 2.0 event in Canberra, which will be hosted by DEEWR in their Theatre at 50 Marcus Clarke Rd from 12:30-1:30pm on Tuesday 14 August.

This time the event features two fantastic speakers, and has a much larger limit due to the large size of the venue.

The speakers are:
  • Michael (Mick) Chisnall (@michaelchisnall), the Director of the Australian Capital Territory’s Government Information Office, who will be talking about the ACT's efforts in the open government space, and
  • Keren Flavell (@KerenFlavell), a founding partner of Wholesome Media and co-founder of Bushfire Connect - a community driven crisis alert tool for sending fire warnings between communities. She'll be talking about the social engagement strategy and TownHall Facebook application developed by Wholesome Media for the Parliament of Victoria
Both have done awesome work in the Gov 2.0 space and have many practical tips and experiences to share.

Alongside the speakers there will be an open mike for people to talk about their latest online initiatives and plenty of engaged attendees to share stories with.

Note that this is a food-free event, however this also means it is free to attend! For anyone seeking food,  there's a cafe next door and plenty of other options nearby.

So if you're looking for some good Gov 2.0 tips and insights, learn more about the event and register at:  http://gov2augustact.eventbrite.com/


Read full post...

Thursday, July 19, 2012

Should government agencies or Ministers supply content to newspapers if it will end up paywalled?

Thirty years ago if you wanted to read the news, you bought a newspaper. A paper newspaper, with real money.

As a result all of a government's announcements - media releases, Ministerial statements, advertising and other content had a price tag by default.

You didn't get to see them if you didn't pay the paper's price (except if you browsed in-store - a practice news agents discouraged).

Over the last twenty years however, news has become freely available online. Go to any print publisher's masthead, online-only news service or agency website and you can read the releases, statements and even see the ads without paying a cent.

Clearly this has been good for governments, who can reach a wider audience with their content due to the lack of a 'paywall' barrier to consumption.

However with the major newspapers now considering paywalls, should government agencies be prepared to go back to the days of allowing commercial providers to charge money for the content they provide to newspaper proprietors for free?

This is a thorny question. On the surface it looks easy - it was OK before, it should be OK now. However we have a new generation of citizens who grew up with free news, who are less inclined to pay for news and therefore government is likely to struggle to reach them.

At the same time we have a phlethora of news sites, some will be paywalled but others won't. Agencies can now distribute releases, statements and even advertisements via their own websites, email lists, and social media channels.

So does government need to rely on traditional media to carry straight news? It is still appropriate for agencies to allow newsprint publishers to 'clip the ticket' for the content they release for free?

Should there be a requirement that Ministerial and agency content isn't hidden behind the paywall and remains part of the free content provided by news services? A traffic generator, but not a profit centre?

I don't have a ready answer to this.

I would expect the news publishers would be quite happy commercialising government content, as they have done in the past, as it gives them cheap content to boost their profits (which can, of course, be taxed).

I also expect that older public servants and politicians wouldn't even question the right of publishers to make money from government content, as it was done before.

However for younger people the situation may not be so black-and-white.

Read full post...

Wednesday, July 18, 2012

How Facebook has become a risk for public servants, and what you can do about it

If you are one of the majority of public servants with a Facebook account, then it may be time to reconsider how you use the service.

As discussed in ZDNet's post, Is Facebook damaging your reputation with sneaky political posts?, Facebook is now posting messages in your timeline and saying you 'Like' the messages simply because you once 'Liked' the Facebook Page that posted them.

So what does this mean, and how is it a risk to public servants?  Here's how it works.

When you 'Like' a Page in Facebook, Facebook assumes this means you also like all the content, status updates, images and other material, that may be posted on that Page by its administrators.

To be 'helpful' Facebook will automatically place some of the Page's content in the newsfeeds of your Facebook friends, with a notice that you 'Like' the content.

Facebook calls this a feature, as quoted in the ZDNet article,

To help people find new Pages, events, and other interesting information, people may now see posts from a Page a friend likes. These posts will include the social context from your friends who like the Page and will respect all existing settings.

This may sound innocent enough, but what it means in practice is that if you ever 'Liked' a Facebook Page for any reason, any new content posted in that Page may now appear to your friends as explicitly 'Liked' by you.

As Pages can change administrator, content and focus, that innocuous Facebook Page on pet rabbits you liked two years ago may now start spewing controversial, obnoxious or otherwise inappropriate content into your Facebook friends' newsfeeds - with each piece of content indicating that you 'Liked' it.

This could merely be embarassing, or it could put your career at risk.

Say you 'Liked' a Facebook Page for a charity you support that works in a policy area covered by your agency. Due to a change in government policy, that charity loses funding and, as a result, begins posting messages on its Facebook Page which are strongly critical of the government's new policy to galvanise their supporters to write to the Minister. Even worse, one of the Page's administrators has been radicalised and frames some of these messages in very strong, almost abusive, language.

These messages begin appearing in the newsfeeds of your friends, complete with a notice that YOU 'Liked' them. Incidentally, you don't see them yourself because Facebook doesn't notify you that they're doing this and these messages don't appear in your own newsfeed.

One of your friends (a colleague at your agency) is horrified that you'd act so unprofessionally and sends screenshots of the messages with your 'Like' to HR, notifying them that you've broken the public service code of conduct by publicly criticising your agency and the government.

You get called in for a discussion with your manager and a HR representative, who shows you the screenshot and asks you to explain your conduct...

Will they believe you when you claim ignorance?


Now compound this issue by thinking about every single Facebook Page that you've every Liked.

Any of them could begin posting messages which could embarrass you, or threaten your job and, thanks to this Facebook feature, indicate automatically that you 'Liked' each message.

Even worse you don't even know when they're doing it because you don't see these messages in your own newsfeed.


So what should you do to deal with this?

Assuming that you're not prepared to close down your Facebook page or, at least, unLike all pages that you have liked, I recommend that public servants look at their 'Likes' page (accessible from their Favourites page) and cast an eye over the pages they've Liked to see if any are likely to post content that will get them in trouble in their friends' newsfeed.

Then make this a regular habit - check all your pages every month to see what they're saying.

Finally, bring this issue with Facebook to your agency's attention, so you'll not be accused of 'Liking' content you didn't.

Read full post...

Tuesday, July 17, 2012

Mapping social media channels to engagement levels (based on IAP2 spectrum)

I developed the Online Engagement Spectrum around three three years ago, based on the IAP2 Spectrum  of Public Participation (PDF) and some complementary work by Bang The Table (no longer at the original web address).

As Gadi Ben-Yedah over at his IBM's Business of Government blog has begun a series of posts considering how social media can be used by government to engage online based on the IAP2 Spectrum, I thought it was timely to repost my Spectrum for people to consider.


Online Engagement Spectrum 1.2

Read full post...

Sunday, July 15, 2012

Are Australia's web developers failing to deliver accessible websites?

In a recent story in ITNews, Accessibility checker surfaces errors, John Hibbert claimed that a new Mental Health website, www.mindhealthconnect.org.au, operated by the National Health Call Centre Network and funded by the Department of Health and Ageing, didn't meet the Australian Government's minimum web standards.

Based on a review using the ACheck tool for the minimum WCAG 2.0 'A' level of compliance, John reported that the checker:
highlighted two known problems, 245 "potential problems", 20 HTML validation errors and 115 cascading style sheet problems on the site.
I tend to always take the results of these tools with a grain of salt. Many of the reported validation errors and style sheet issues are often repeats of one single issue, or are not really issues at all, and the two known problems would take a couple of minutes to fix and do not pose direct accessibility risks at all.

However this article does highlight a concern I've had for several years - whether Web Developers, contracted to produce these sites for government, always have the appropriate skills and knowledge to develop accessible websites.

I've seen this type of issue repeated a number of times. A policy or program area, possibly with support from a central communication or IT area, goes out to tender for a website. Web Developers respond, get assessed and the successful tenderer goes about creating the site.

A few months later the site is complete with days to spare before the Ministerial launch - but fails accessibility testing by the agency.

"We didn't understand how important accessibility was to you" says the Web Developer. Note that I was in the room when these exact words were said to an agency by a reputable web developer regarding a website which was developed iteratively and we'd been giving them feedback about accessibility for a number of weeks.

So what happens next?

If accessibility was not explicit mentioned in the contract, the Web Developer asks for more cash to meet the requirement, even though it is a baseline requirement for all government websites across Australia, and says it won't be ready for launch.

If an accessibility level was explicitly agreed to in the contract, the Web Developer grudgingly assigns a junior developer to 'sort it out' - with a vague promise that it will be done in a few weeks or months.

The agency is left having to launch a website which doesn't meet the minimum and fix it as soon as possible afterwards - all because the Web Developer didn't recognise and act on the legal requirement for accessibility.

Of course there's many examples where Web Developers have done exceptional accessibility work for agencies, however I have seen and heard too many issues where professional Web Developers didn't understand the accessibility requirements of governments.

Delivering an inaccessible website to a government agency will cause that agency to break the law and expose it to enormous risks of legal damages. No vendor should ever put their client in this type of position knowingly, particularly where it is so easily avoidable.

My view is that any Web Developer that doesn't deliver a government website to at least the minimum accessible standards (unless otherwise explicitly agreed to by the agency in question) should not receive any payment until they have addressed all accessibility issues.

They should also lose their right to bid for other government business until they can prove they have fully trained their staff on accessible web design.

These may be harsh and strong measures, and I doubt they will be considered due to contractual and practical issues.

However if a vendor contracted to sell a government agency a car that turned out to not be street legal or rent them a building that turned out to not meet the building code, government would walk away without paying and ask for damages, plus be very cautious about working with that vendor again.

Why should it be any different with illegal websites?

Read full post...

Bookmark and Share