Everyone whether they have a disability or not needs to have the same experience when using any intranet information or applications. Employees with a disability may use devices to help them. Your intranet needs to be compatible with these to avoid risking breaking the guidelines and any law that applies in the country where the person works.
Accessible content is also easier to adapt to use with mobile devices e.g. smartphones, tablets, and laptops with their different screen sizes. Try thinking of accessible content as being a step further on from it meeting your usable standard.
If your intranet has information or applications that are not accessible to all employees, you will be breaking the web accessibility guidelines. Legislation and codes of practice based on the latest World Wide Web, Web Accessibility Initiative (W3C Accessible content WCAG 2.0 AA) guidelines will apply in most countries. US Section 508 and UK DDA 1995 are two examples. These guidelines are at three levels, A, AA, and AAA covering the most basic problems to the most advanced problems experienced by people with a disability when using your intranet.
Many organisations find it difficult to see the benefits from publishing standards. I remove the barriers to show the benefits from each publishing standard in this series of posts. Publishing standards aim to:
- Reduce the risk of sensitive information leaks
- Improve the overall user experience
- Make people using your intranet more satisfied with it
- Improve people’s productivity
- Improve people’s quality of work
Knowing that you are helping people with disabilities to use your intranet gives three main benefits:
- People with disabilities using your intranet will have the same or similar experience to anyone else. This will encourage more frequent and extensive use because the intranet is accessible and usable and meets the needs for everyone.
- You can encourage your publishers to make their content and applications accessible to meet their legal requirements. There is the added, sometimes overlooked, benefit that accessible content also displays well in other devices such as tablets and smartphones if it meets accessibility standards.
- Your organisation complies with a legal requirement. It can also see investment made in your intranet has the benefit of being available in other devices that help with new ways of working and while mobile.
My next post on navigation will be the last in this series. I hope you have found them helpful.
Posted in benefit, best practice, digital workplace, governance, intranet, SharePoint, standards, value
Tagged accessibility, benefit, best practice, digital workplace, governance, intranet, publishing, standards, 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?
Posted in benchmark, best practice, content management, governance, intranet, publishing, standards, usability
Tagged accessibility, best practice, governance, intranet, publishing, standards, training, usability, value
When you are faced with implementing SharePoint 2010 your intranet needs the right standards to make the launch and ongoing use a great success.
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:
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.
Posted in benefit, governance, intranet, SharePoint 2010, standards, usability, web accessibility
Tagged accessibility, collaboration, governance, intranet, sharepoint 2010, standards, usability standards
This is another example of BT’s intranet standards used to give users a great experience.
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.
Posted in best practice, content management, intranet, publishing, standards, usability, web accessibility
Tagged accessibility, best practice, bt intranet, content, publishing, standards