Tags: accessibility, best practice, governance, intranet, publishing, standards, training, usability, value
I have reviewed many intranets and have been amazed at the variety of publishing standards and how they are enforced. These vary from no publishing standards through to everything being locked down depending on the importance of complying with standards. More importantly it is the amount of time, effort, and money that is used to enforce people to comply with the standards when they publish information.
I sometimes think organisations lose the plot and forget to look at the costs being spent for the benefit being gained.
Your intranet needs standards to make sure your organisation complies with business, user, regulatory, and legal requirements in any country it operates in. The best approach is to have ‘smart’ standards that need the minimum time, effort, and cost which achieving the maximum effectiveness and benefits. How many of these questions can you answer “yes” to?
- Do you train your publishers on what your intranet standards?
- Do you also train your publishers on why your intranet has these standards?
- Do you educate and support your publishers with guidance to understand more about your standards?
- Do you embed any of your standards in the publishing templates e.g. branding, navigation menu?
- Do publishers need to comply with your standards before their content is published e.g. images need to have alternative texts before they can be used?
- Do you review content for compliance?
- Do you remind your publishers if their content is non-compliant?
- Do you remove content if no action by your publishers to comply?
- Do you measure how compliant your intranet is?
- Have you measured it more than once?
If you answered “yes” to all these questions then award yourself a gold medal!
If you answered “no” to any of these questions perhaps you had better contact me?
Tags: accessibility, collaboration, governance, intranet, sharepoint 2010, standards, usability standards
How can you do this? Firstly you need to be clear why you have standards. The reasons why usually include:
- Legal: web accessibility, copyright and image rights
- Regulatory: compliance with country and international agreements
- Business: content reviewed regularly and up to date
- Users: content ownership clear, easy to use and find
Your intranet standards need to:
- Improve the overall user experience
- Make people more satisfied
- Increase productivity
- Save costs
- Benefit the business
When using SharePoint 2010 I recommend five standards you must include. These cover the different types of content and tools that you can use with SharePoint 2010 ranging from accredited information through to collaborative discussions.
You need to be clear that all your information is managed and has an owner. Intranet managers need to be able to contact an owner if there is a problem with their content quickly and easily. People need to know who to contact if they need more information not shown or wish to check about anything that has been published. You need to reassure your senior managers that any risk has been removed of non-compliance from information not managed.
Your employees must be confident they are using the most up to date information. You need to clearly show a review date, in line with your information retention policy, for people to see. Your content must be reviewed regularly and be removed if it is no longer needed and out of date.
SharePoint 2010 permissions need to be correctly set so people only see the information they have permission to see. Get these right at an organisation-wide level to save time and effort later. Owners (site administrators) of content can decide at a site level who can have permission to create, edit, as well as view content published.
Your information must be usable and valuable to people using it. Use SharePoint 2010 webparts to create the experience research with people has shown is needed. Train your publishers on ‘tone of voice’ and ‘writing for the web’ to help achieve this. To use the full range of SharePoint 2010 features well you must make it easy for people to share views, discover other people and their skills, find the right information and use what they find with the minimum of effort and time taken.
This is not an optional extra. It is mandatory. You need to go that extra step beyond usable content and make sure your content is accessible to everyone whether they are impaired or not. It needs to meet WCAG 2.0 guidelines. Legal requirements do vary from country to country. For the UK AA level is the current expert recommendation.
What you need to do is check standards are complied with. This can be achieved by using people or outside auditors to check content or better still, if you can afford it, an automated compliance checker tool.
Tags: accessibility, best practice, bt intranet, content, publishing, standards
Most browsers, and especially those for people with visual impairment, allow users to adjust font sizes to suit their needs. Therefore, it is important that you do not fix font in an exact, or ‘absolute’, size because users may not be able to see it!
Style sheets in content management systems will take care of font sizes, but if you create your own HTML & style sheets, you must use relative sizing, e.g. -1, or +1.
HTML <font> tag
You should use style sheets instead of the <font> tag to define font attributes. If you still have existing <font> tags within your site you should make sure they are relative and not fixed. You must then switch to style sheets at your next re-design.
Using styles for fonts
When using styles also always use the relative tags, such as percentage or plus and minus. For example if you want a headline to be bigger then use something like +2, or 150%, or ‘bigger’. Similarly, to make something appear smaller in scale to the rest of the page use -1, 75% or ‘smaller’.
The use of percentage, ‘em’ units or other ‘relative’ mechanisms to define the font size makes it easy for users to change the text size using their browser settings.
Testing should be done in the initial stages of creating a set of styles so that subsequent pages linked to the same style sheet will work:
- you need to check pages using the “Largest” and “Smallest” text size settings in the browser
- also test using a range of browser resolutions and settings to ensure the content does not become truncated or cause overlapping sections of content and text
- switch off the style sheet in the browser to ensure the content is still meaningful.
Tags: accessibility, applications, governance, publishing, standards, users
When I asked a few weeks ago is your intranet breaking the law Janus Boye wanted me to cover other legal responsibilities we have. After a quick panic attack I recovered what poise I have and realised there are other areas where intranet managers, publishers and designers need to make sure their intranet is legal.
So here are key points you need to consider. I suggest you go to the Outlaw site for more details on legal information.
1. Information retention
We need to make sure we only retain the information needed by law and for the sound running of our organisation. But you need to consider whether you retain old copies of content. I know of someone who needed to show a copy of a web page as it was at the time of the incident to prove what guidance was actually being given to people.
2. Legal and regulatory frameworks
Like BT’s undertakings with Ofcom, you may need to meet regulatory requirements. This means there is often a need for some ‘knowledge firewalls’ to safeguard insider information in all sorts of industries such as the pharmaceutical, legal and banking industries. Incidentally the term ‘chinese wall’ is to be avoided according to Wikipedia.
This isn’t just personal. It could be commercial confidentiality too. If someone creates a page about issues with a piece of software how would they be affected?
4. Freedom of information (FoI)
This can be a big concern with intranet content. Anything published on your intranet may be subject to a FoI challenge. It could makes you less likely to share some details. This is probably likely to affect public service intranets most.
5. Data protection
Data Protection, particularly Personal Data and European Union rules for its use and storage, may affect your intranet systems, particularly HR systems.
Copying any content, especially an image, photo or multi-media file, from another website to insert on an intranet site is an infringement of copyright, unless you have permission from the copyright owner. To avoid any copyright problems restrict your uploading to content which you have created; colleagues, friends or relatives have created and given you permission to use; is provided by an official agency.
Tags: accessibility, applications, best practice, bt intranet, content, publishing, standards, value
My intranet could be breaking the law! Why? What? How?
Well if you have information or applications that is not accessible to everyone then you could be. Everyone, whether they have any impairment or not, need to have the same experience when using any intranet information or applications.
In BT we aim to achieve WCAG 2.0 standard. This is above the likely legal requirement for UK DDA 1995 and, more importantly, sets best practice for all users of BT’s intranet so they have a good experience whatever they use, whether they are impaired or not.
How are we doing this? Well, apart from my last post on how to use it as a lever for wider improvements, BT:
- Prevents web accessibility errors by training, clauses in contracts to buy web services, standards embedded in content templates
- Identifies and corrects web accessibility errors using an automated checker tool
- Guides users on how to use your browser, computer more accessibly.
Follow the right approach and you won’t get a nasty surprise. It only takes one discriminated user and you could have a really big problem to solve.
Prevention is much, much, cheaper and better than curing a problem like this.
Tags: accessibility, applications, bt intranet, intranet applications, usability standards
I sometimes come across sites and applications on BT’s intranet which could be more usable. I find it can be easier to pick up with the owner or developer about its accessibility as a lever to improve other areas such as usability. Why you may ask?
Well there are some improvements which are a matter of opinion. What is usable to one person maybe very unusable to another. They are subjective.
But accessibility is NOT subjective. Either a site is accessible or not. Also in most countries there is a legal requirement for web services (this includes intranets) to be accessible. The level required may vary.
Accessibility standards are available to everyone on the internet. So whether a site or application is developed, published or managed inside or outside of your organisation, the information will always be there.
When a site or application’s accessibility is being updated it is a great opportunity to improve the usability and make other changes at the same time.
So ideally you can improve a site or application so it is legal and improved in other ways to give a better overall experience for all users.
Preventing accessibility problems as well as correcting existing problems is very important for your users as well as your organisation’s legal responsibilities.
I’ll post soon about what BT does on web accessibility.
Tags: accessibility, applications, bt intranet, content, directory, intranet applications, oracle, people finder, publishing, standards, usability, users
Last Friday I was interviewed by the Intranet Benchmarking Forum about how BT was meeting our intranet users’ needs who use a mobile device. I also came across a great blog post and an internet report on mobility (over 40mb!).
So, I thought I would share what BT has done and what I would like to do in this post as it is becoming a hotter topic.
I posted about BT Intranet mobile users in June 2009 which links to examples. I feel progress in 2010 will move in different ways for content than for applications.
Now: BT’s intranet standards make sure a PDA heading is on the templates used by our content management system for publishing information. It means mobile users can click on this to see a text version of the same content. Changes made to the main version automatically update the PDA version so people can rely on the content being the same.
Future: With the increased capability of mobile devices used by people in BT I want to make sure the coding (CSS) used for the content is capable of sizing up or down for any device and enable images to also adjust their size. This means we only need one version that is usable and accessible to any device (mobile, laptop, desktop PC, etc) saving on costs and giving users a better experience.
For applications two versions are needed. The full, standard, functionality is available for people to use but for mobile devices only the cut down, key functionality is available.
For example with BT’s Directory I can check a person’s contact details, manager, organisation chart, whereabouts, team members and their whereabouts. For mobile devices only the contact details for the person found are available as that is the main reason why people use it.
The difficulty for me is persuading software vendors used by BT for intranet applications to understand why this is important and what is needed. It should keep me busy during 2010!
Tags: accessibility, applications, intranet applications, publishing, users
Has anyone seen the new free accessibility tool on the WAVE site? I thought you might be interested in knowing there is a simple to use and visual tool out there compared with other tools that tend to be a bit ‘techie’ in their results.
WAVE is a free web accessibility evaluation tool provided by WebAIM. It is used to aid people in the web accessibility evaluation process. Rather than providing a complex technical report, WAVE shows the original web page with embedded icons and indicators that reveal the accessibility of that page.
Even better from an intranet perspective, the WAVE Firefox toolbar allows you to evaluate web pages directly within your browser. Because no information is sent to the WAVE servers, the toolbar allows you to evaluate password protected, secure, or otherwise sensitive web content. The WAVE toolbar evaluates content as it is rendered within Firefox. This allows dynamically created, modified, or scripted content to be evaluated in real time.