Accessibility is on the minds of most public sector and many private sector organizations in Ontario, Canada that are creating new or significantly upgrading their existing websites. The government is mandating conformance to strict guidelines defined by WCAG 2.0. Does SharePoint have what it takes to do the job? In this presentation I provide you with an overview of the Accessibility to Ontarians with Disabilities Act (AODA) and its relationship to WCAG 2.0, and outline the key areas that need to be considered when building AODA-compliant sites. Finally I will present results of short experiments I did on SharePoint 2010 and 2013 as it relates to accessibility.

1. Haniel Croitoru

2. Haniel Croitoru

3. Thanks to our sponsors!

4. 




5. 





6. let’s play a game…

7. not fair!

8. over 15 percent in Ontario

9. Mental Dysfunction or Impairment
• Understanding or using symbols
or spoken language
• Mental disorder
• Developmental disability
Auditory
• deafness or hearing impediment
Mobility
• reliance on an animal (guide dog)
• Reliance on a remedial
appliance/device (wheelchair)
Visual
blindness or visual impediment
Speech
• muteness or speech impediment
Coordination
• Epilepsy
• brain injury
• varying paralysis
• Lack of physical coordination
• Amputation

10. call for equality

11. aoda

14. 



16. wcag 2.0

17. 




18. Government of Ontario and the Legislative Assembly
2012 AA for new public and internal websites 1
2016 AA for all public websites and web content 1
2020 AA for all public and internal websites and web content
Public sector organizations, businesses and non-profit organizations (50+
staff)
2014 A for new public websites and web content
2021 AA for all public websites and web content posted after January 1, 2012 1
1.

19. wcag 2.0 principles

20. Perceivable
• Content can’t be invisible to all
senses
Operable
• UI components and navigation
must be operable
• Cannot require interaction that
a user cannot perform
Understandable
• Content or UI operation cannot
be beyond user’s
understanding
Robust
• Content must be robust
enough to be interpreted by a
wide variety of user agents,
including assistive technologies

21. perceivable

22. The logo on the left is
meaningless to someone
who doesn’t know the
company and its
branding.

23. Users need the ability to
control the time it takes to
perceive video. This
implies having controls to
pause, stop, and rewind
movies.

24. Content should be
presentable in different
ways (e.g. simpler layout)
without losing
information or structure
Username: JDoe
DOB: Oct 20, 1974
Member since: Jan 1, 2012
Member Status:
Active
Last Access:
Today
Username: JDoe
DOB: Oct 20, 1974
Member since: Jan 1, 2012
Member Status: Active
Last Access: Today

25. Hello World
Make it easier for
users to see and hear
content including
separating foreground
from background

26. operable

27. Make all functionality
available from a
keyboard

28. Provide users enough
time to read and use
content

29. Do not design content
in a way that is known
to cause seizures

30. Provide ways to help
users navigate, find
content, and
determine where they
are

31. understandable

32. pLaNeS Clip Each
Other at O'HARE;
Make text content
readable and
understandable

33. Make Web pages
appear and operate in
predictable ways

34. Help users avoid and
correct mistakes

35. compatible

36. Maximize
compatibility with
current and future
user agents, including
assistive technologies

37. what’s wrong here?

38.  https://www.google.ca/maps/place/Microsoft+Cana
da+Co/@43.612575,-
79.753878,17z/data=!3m1!4b1!4m2!3m1!1s0x882b
6a96cc399fdd:0x2091eb248a5a3848

39. achieving accessibility

42. sharepoint experiments

43. 


44. 

45. Issues
Achecker 10 known errors, 220 potential
errors, 54 HTML validation
errors,
804 CSS validation errors
PowerMapper 14 accessibility issues
AMP 80% WCAG Level A compliance
100% WCAG Level AA
compliance
HiSoftware® Cynthia Says™ 90% WCAG Level AA compliance
W3C Markup Validation Service 54 errors
Total Validator 97 errors, 8 warnings

46. 

47. Issues
Achecker 31 known errors, 412 potential
errors, 151 HTML validation
errors,
462 CSS validation errors
PowerMapper 22 accessibility issues
AMP 88% WCAG Level A compliance
100% WCAG Level AA
compliance
HiSoftware® Cynthia Says™ 83% WCAG Level AA compliance
W3C Markup Validation Service 151 errors, 33 warnings
Total Validator 291 errors, 16 warnings

48. 79%
16%
5%
Out of the box
Customization
Governance


49. 

50. Issues
Achecker 13 known errors, 277 potential
errors
PowerMapper 0 accessibility issues
AMP 63% WCAG Level A compliance
66% WCAG Level AA compliance
HiSoftware® Cynthia Says™ 3 WCAG Level A errors, 4 WCAG
Level AA errors
W3C Markup Validation Service 60 errors
Total Validator 122 errors, 16 warnings

51. 

52. Issues
Achecker 32 known errors, 383 potential
errors
PowerMapper 4 accessibility issues
AMP 68% WCAG Level A compliance
66% WCAG Level AA compliance
HiSoftware® Cynthia Says™ 2 WCAG Level A errors, 1 WCAG
Level AA errors
W3C Markup Validation Service 154 errors, 26 warnings
Total Validator 9errors, 10 warnings

53. 




54. sharepoint 2013 accessibility

55. 





56. 


57. planning for accessibility

58. 




59. 



60. 



61. 




62. final thoughts

63. 




64. 





65. 


66. Connect. Collaborate. Share.
Toronto SharePoint Users Group
http://www.meetup.com/TorontoSPUG/
Toronto SharePoint Business Users Group
http://www.meetup.com/TSPBUG/
SharePoint Saturday Toronto
http://spbuzz.it/spstoyam

67. 



