Project 508

A presentation on Web Standards and accessibility given at Xstrata plc

Transcript

1. Project 508 web standards and accessibility Tuesday February 7th, 2006 1
2. overview ‣ what are ‘web standards’ and ‘accessibility’? ‣ why is xstrata concerned by these issues? ‣ where does xstrata stand today? ‣ what is left to be done and when? 2
3. web standards 3
4. web standards 3
5. as a standard stand•ard c㷦TUBOEⓒSEc n. something, such as a practice or a product, that is widely recognised or employed, especially because of it’s excellence adj. regularly used, widely available or supplied 4
6. as a standard stand•ard c㷦TUBOEⓒSEc adj. regularly used, widely available or supplied n. something, such as a practice or a product, that is widely recognised or employed, especially because of it’s excellence 4
7. as a standard stand•ard c㷦TUBOEⓒSEc n. something, such as a practice or a product, that is widely recognised or employed, especially because of it’s excellence adj. regularly used, widely available or supplied 4
8. as a vision The World Wide Web Consortium (W3C) 5
9. as a vision The World Wide Web Consortium (W3C) “To lead the World Wide Web to its full potential by developing protocols and guidelines that ensure long-term growth for the Web”. http://www.w3.org The World Wide Web Consortium (W3C) is an international consortium which’s mission is: 5
10. html specs “HyperText Markup Language is used to structure information — denoting certain text as headings, paragraphs, lists and so on — and can be used to describe [..] the semantics of a document.” http://en.wikipedia.org/wiki/Html 6
11. css specs “Cascading Style Sheets (CSS) is a stylesheet language used to describe the presentation of a document written in a markup language.” http://en.wikipedia.org/wiki/Cascading_Style_Sheets 7
12. XHTML compliance CSS 8
13. how? XHTML compliance CSS 8
14. how? separate design from content XHTML compliance CSS 8
15. how? separate design from content semantic markup for content cascading style sheets for layout compliance 8
16. Flash Java compliance browser 9
17. and? Flash Java compliance browser 9
18. and? avoid proprietary technology Flash Java compliance browser 9
19. and? avoid proprietary technology no required plugins or extensions no device dependant programming compliance 9
20. web standards compliance 10
21. web standards compliance ‣ shows you care about your visitors 10
22. web standards compliance ‣ shows you care about your visitors ‣ maximise the number of potential visitors 10
23. web standards compliance ‣ shows you care about your visitors ‣ maximise the number of potential visitors ‣ faster loading and reduced bandwidth usage 10
24. web standards compliance ‣ shows you care about your visitors ‣ maximise the number of potential visitors ‣ faster loading and reduced bandwidth usage ‣ provide the foundation for accessibility 10
25. web standards compliance ‣ shows you care about your visitors ‣ maximise the number of potential visitors ‣ faster loading and reduced bandwidth usage ‣ provide the foundation for accessibility ‣ improve search engine rankings 10
26. web standards compliance ‣ shows you care about your visitors ‣ maximise the number of potential visitors ‣ faster loading and reduced bandwidth usage ‣ provide the foundation for accessibility ‣ improve search engine rankings ‣ make your markup easier to maintain 10
27. web standards compliance ‣ shows you care about your visitors ‣ maximise the number of potential visitors ‣ faster loading and reduced bandwidth usage ‣ provide the foundation for accessibility ‣ improve search engine rankings ‣ make your markup easier to maintain ‣ future-proof content and extensibility 10
28. web standards compliance ‣ shows you care about your visitors ‣ maximise the number of potential visitors ‣ faster loading and reduced bandwidth usage ‣ provide the foundation for accessibility ‣ improve search engine rankings ‣ make your markup easier to maintain ‣ future-proof content and extensibility ‣ it’s the right way of getting the job done 10
29. accessibility 11
30. accessibility 11
31. what is accessibility? 12
32. what is accessibility? “Making allowances for characteristics a person cannot change or cannot change easily.” Joe Clark 12
33. what is accessibility? “ Web accessibility refers to the practice of making Web pages on the Internet accessible to all users, especially those with disabilities.” http://en.wikipedia.org/wiki/Website_accessibility 13
34. what isn’t accessibility? ‣ a “text-only” page ‣ any separate “accessible” version ‣ any page tailored for a single disable audience ‣ any page made for an unsual device 14
35. why be accessible? ‣ because you can ‣ because you have to ‣ because of good public service ‣ because accessibility is a component of web standards 15
36. how do you do it? ‣ use valid semantic markup of content ‣ use valid cascading style sheets for layout ‣ don’t use images for text, navigation, etc. ‣ use proprietary technology with parsimony ‣ provide an accessibility statement 16
37. accessibility standards ‣ Web Content Accessibility Guidelines or WCAG ‣ WCAG 1.0 as 3 levels of conformance ➡ level A : minimum ➡ level AA : good ➡ level AAA : best practice 17
38. accessibility standards ‣ Web Content Accessibility Guidelines or WCAG ‣ WCAG 1.0 as 3 levels of conformance ➡ level A : minimum ➡ level AA : good ➡ level AAA : best practice 17
39. legal requirements In the UK, the Disability Discrimination Act 1995 (DDA) does not refer explicitly to website accessibility, but makes it illegal to discrimate against people with disabilities. 18
40. legal requirements In the UK, the Disability Discrimination Act 1995 (DDA) does not refer explicitly to website accessibility, but makes it illegal to discrimate against people with disabilities. In the UK, the Disability Discrimination Act 1995 (DDA) does not refer explicitly to website accessibility, but makes it illegal to discrimate against people with disabilities. A document (*) published in 2004 by the government's Disability Rights Commission to accompany the Act does refer explicitly to websites as one of the “services to the public” which should be considered covered by the Act. (*) Code of Practice: Rights of Access - Goods, Facilities, Services and Premises 18
41. some facts Over 11% of the U.K. population has a disability relevant to usage of the Web. That’s approximatively 808,000 people. Office for National Statistics (2001) 19
42. some facts 3.6% of the U.K. population - about 255,000 people - have a “sensory” disability. That means “difficulty in seeing” or “difficulty in hearing.” Office for National Statistics (2001) 20
43. some facts Some of the people with a mobility impairment – 5.7% of the population, or 404,000 people – will be affected by Web accessibility (musculoskeletal problems of the arms or hands). Office for National Statistics (2001) 21
44. some facts And finally, some people with a learning disability (about 2.1%, or 149,000 people) will be served by Web accessibility. Office for National Statistics (2001) 22
46. 1999 2000 2001 2002 2003 2004 2005 24
47. 1999 2000 2001 2002 2003 2004 2005 24
48. current design issues 25
49. current design issues ‣ lots of presentational – not semantic – content markup 25
50. current design issues ‣ lots of presentational – not semantic – content markup ‣ limited number of navigation items – can’t be expanded, non homogenous throughout site 25
51. current design issues ‣ lots of presentational – not semantic – content markup ‣ limited number of navigation items – can’t be expanded, non homogenous throughout site ‣ no sub-section category sorting of information (per year or per kind) 25
52. current design issues ‣ lots of presentational – not semantic – content markup ‣ limited number of navigation items – can’t be expanded, non homogenous throughout site ‣ no sub-section category sorting of information (per year or per kind) ‣ no contextual search 25
53. current design issues ‣ lots of presentational – not semantic – content markup ‣ limited number of navigation items – can’t be expanded, non homogenous throughout site ‣ no sub-section category sorting of information (per year or per kind) ‣ no contextual search ‣ fixed screen width (870px) 25
54. steps to take 26
55. steps to take ‣ cleanup and update the pages’ markup – validate against the W3C standards ‣ redesign the navigation schemes to enable the addition of extra sections or sub-sections ‣ design information sub-category sorting (tabs) ‣ design contextual search functions for reports, news or sustainability e.g. ‣ redesign the page layout – fluid or elastic 26
56. ✓ ‣ cleanup and update the pages’ markup – validate against the W3C standards ‣ redesign the navigation schemes to enable the addition of extra sections or sub-sections ‣ design information sub-category sorting (tabs) ‣ design contextual search functions for reports, news or sustainability e.g. ‣ redesign the page layout – fluid or elastic it’s {almost} done! 26
62. potential savings * 31
63. home page press room corporate potential savings * 31
64. home page press room corporate 8’990 39’780 18’979 potential savings * 31
65. home page press room corporate 8’990 39’780 18’979 5’315 9’865 6’126 potential savings * * in KBytes 31
66. overall average saving 50% 32
67. in terms of bandwidth 33
68. in terms of bandwidth 226,868,208 KBytes/year 33
69. in terms of bandwidth 226,868,208 KBytes/year 216 GBytes/year 33
70. in terms of bandwidth 226,868,208 KBytes/year 216 GBytes/year 113,434,104 KBytes ~ 180 CDs 33
71. ‣ redesign the global navigation scheme to enable the addition of extra sections ‣ redesign the overall page layout – fluid or elastic why almost? 34
86. demo new layout features navigation | window resize | zoom | markup 42
87. www.cybmed.com 43
88. usage stats 44
89. 12 months * Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Pages Files Hits * February 4th, 2006 incl. 45
90. 24 months * 0 375,000 750,000 1,125,000 1,500,000 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Pages Hits * Jan 2004 - Dec 2005 46
91. monthly usage * Most active month March 2005 : 403,256 pages sent. 20,356,661,049.00 bytes served. 865,951 requests handled. Monthly average: 255,144 pages sent. 14.897 GB served. 616,693 requests handled. * Jan 2004 - Dec 2005 47