Haniel CroitoruEnvision ITJuly 12, 2014
Accessibility for Ontarians with Disabilities ActWhat is it, how well SharePoint addresses it, and other considerations
Haniel CroitoruEnvision ITJuly 12, 2014
Accessibility for Ontarians with Disabilities ActWhat is it, how well SharePoint addresses it, and other considerations
Thanks to our sponsors!
A bit about me… Senior consultant with over
15 years of project management and business analysis experience
Since 2003 focusing on SharePoint
MSc in Computer-Assisted Orthopedic Surgery and Master’s Certificate in Project Management from the York Schulich School of Business
PMP and PMI-ACP (Agile) certified
Scrum MasterProject ManagerSharePoint Consultant
Agenda Let’s play a game Need for Accessibility AODA & WCAG 2.0 SharePoint experiment Final thoughts
let’s play a game…
not fair!
over 15 percent in Ontario
Types of DisabilitiesMental 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)
Visualblindness or visual impediment
Speech• muteness or speech
impediment
Coordination • Epilepsy• brain injury• varying paralysis• Lack of physical
coordination• Amputation
call for equality
aoda
AODA
Developing, implementing and enforcing accessibility standards in order to achieve accessibility for Ontarians with disabilities with respect to goods, services, facilities, accommodation, employment, buildings,
structures and premises on or before January 1, 2025; and
AODA
Providing for the involvement of persons with disabilities, of the Government of
Ontario and of representatives of industries and of various sectors of the economy in the development of the accessibility standards.
2005, c. 11, s. 1.
AODA Section 14 Section 14 (INFORMATION AND
COMMUNICATIONS STANDARDS) applies to Accessible websites and web content
AODA uses W3C WCAG 2.0 as its conformance benchmark.
Other guideline: Authoring Tool Accessibility Guidelines (ATAG), Accessible Rich Internet Applications (ARIA) and the User Agent Accessibility Guidelines (UAAG).
Computers in everyday life
wcag 2.0
WCAG 2.0 Web Content Accessibility Guidelines
(WCAG) 2.0 ISO/IEC standard as of October 2012 Content - information presented to a user
in a web page: text, images, forms, sounds, etc.
Three levels: A, AA, AAA. AAA has the highest level of accessibility requirements.
AODA DeadlinesGovernment 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. except for pre-recorded audio descriptions
wcag 2.0 principles
WCAG 2.0 PrinciplesPerceivable• 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
perceivable
Text Alternatives
The logo on the left is meaningless to someone who doesn’t know the company and its branding.
Time-based Media
Users need the ability to control the time it takes to perceive video. This implies having controls to pause, stop, and rewind movies.
Adaptable
Content should be presentable in different ways (e.g. simpler layout) without losing information or structure
Username: JDoe
DOB: Oct 20, 1974Member since: Jan 1,
2012
Member Status: Active
Last Access:Today
Username: JDoeDOB: Oct 20, 1974Member since: Jan 1, 2012Member Status: ActiveLast Access: Today
Distinguishable
Hello WorldMake it easier for users to see and hear content including separating foreground from background
operable
Keyboard Accessible
Make all functionality available from a keyboard
Enough Time
Provide users enough time to read and use content
Seizures
Do not design content in a way that is known to cause seizures
Navigable
Provide ways to help users navigate, find content, and determine where they are
understandable
Readable
pLaNeS Clip Each Other at O'HARE;
Make text content readable and understandable
Predictable
Make Web pages appear and operate in predictable ways
Input Assistance
Help users avoid and correct mistakes
compatible
Compatible
Maximize compatibility with current and future user agents, including assistive technologies
what’s wrong here?
What’s wrong with this?
https://www.google.ca/maps/place/Microsoft+Canada+Co/@43.612575,-79.753878,17z/data=!3m1!4b1!4m2!3m1!1s0x882b6a96cc399fdd:0x2091eb248a5a3848
achieving accessibility
WCAG 2.0 Guidelines
Guidelines!?!?
WCAG 2.0 Guidelines
A guideline is a statement by which to determine a course of action. A guideline aims to streamline particular processes according to a set routine or sound practice. By definition, following a guideline is never mandatory. Guidelines are not binding and are not enforced.
-Wikipedia
sharepoint experiments
Validating website accessibility Dozens of tools
available to validate website accessibility (source: W3C Web Accessibility Initiative).
Tools vary in scope of validation, levels of automated testing, reporting, accessibility guidelines tested, licensing and more.
SharePoint 2010 Experiment Scenario 1:
Out of the box publishing site
SharePoint 2010 Experiment 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 compliance100% WCAG Level AA compliance
HiSoftware® Cynthia Says™ 90% WCAG Level AA compliance
W3C Markup Validation Service 54 errors
Total Validator 97 errors, 8 warnings
SharePoint 2010 Experiment Scenario 1:
Out of the box team site
SharePoint 2010 Experiment 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 compliance100% 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
SharePoint 2010 WCAG 2.0 AA Compliance
79%
16%
5%
Out of the box
Reference: http://webbism.com/2012/07/24/sharepoint-2010-accessibility/
SharePoint 2013 Experiment Scenario 1:
Out of the box publishing site
SharePoint 2013 Experiment Issues
Achecker 13 known errors, 277 potential errors
PowerMapper 0 accessibility issues
AMP 63% WCAG Level A compliance66% 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
SharePoint 2013 Experiment Scenario 1:
Out of the box team site
SharePoint 2013 Experiment Issues
Achecker 32 known errors, 383 potential errors
PowerMapper 4 accessibility issues
AMP 68% WCAG Level A compliance66% 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
Why the differences? Qualitative vs. quantitative Automated (e.g. computer) vs. Manual
(e.g. CNIB) Server-generated pages vs. final viewable
pages Categorization of inconsistencies
sharepoint 2013 accessibility
SP 2013 Improvements Enhanced keyboard access to all
functionality including the ribbon interface
Changes to overcome technical conformance issues in master pages
Improved page reading sequences and representation of tabular data
“More Accessible Mode” “Single accessible platform” using similar
interfaces.
Issues Page structure: code generated by
master pages and web components can introduce accessibility issues (e.g. heading, lists, tables, reading order and field labels.)
Complex interfaces: some complex interfaces are not accessible (e.g. rich text editor, calendar control, people picker and the datasheet view control).
planning for accessibility
The importance of governance Identify which of the principles can be
addressed via technology and which via governance
Some accessibility can be achieved by combining technology and governance
Identify champions in an organization to implement and enforce accessibility-related governance and address concerns
Checking that any organization specific changes, content, and branding also meet accessibility requirements
Development Planning Minimize code changes to controls and
master pages. Instead, use control adapters or Javascript to meet accessibility.
Remove unused/hidden components to render pages with clean code and correct reading order
Consider accessibility from initial planning of a SharePoint implementation so that customizations can easily be incorporated. This minimizes any additional development effort required to address accessibility.
Accessibility Testing Planning Determine tools that will be used to test
for accessibility early on in the project Test frequently (with and without content) Use Window Eyes to test for Compatibility
and Adaptability
Governance Planning One of the most common reasons for
accessibility failure is content. This requires strict governance.
Use tools (e.g. Microsoft Office Accessibility Checker) to assist content authors to test new web content before they publish it. The accessibility checker detects common accessibility problems such as missing alternative text and the use of styles.
Create workflows in SharePoint to define document approval paths including accessibility checks.
Use proven set of templates, master pages, and web components
final thoughts
Final Thoughts Accessibility is here to stay (as long as
there are disabled people) WCAG 2.0 are guidelines to achieve AODA
compliance Include accessibility early on in technical
and governance planning and throughout the project
When possible, content validation should be excluded as it will often be out of control of the team building the site
Useful Links Accessibility for Ontarians with Disabilities Act,
2005www.e-laws.gov.on.ca/html/source/regs/english/2011/elaws_src_regs_r11191_e.ht
m
Web Content Accessibility Guidelines (WCAG) 2.0www.w3.org/WAI
Conformance statement AA-level for SharePoint Server 2013technet.microsoft.com/en-us/library/ff852107(v=office.15).aspx
CNIB Accessibility Serviceswww.cnib.ca/en/services/accessibilities/
Window-Eyeswww.windoweyesforoffice.com
SharePint Drake and Firkin aka “The Drake” 6982 Financial Drive, Unit B101
Connect. Collaborate. Share.
Toronto SharePoint Users Grouphttp://www.meetup.com/TorontoSPUG/
Toronto SharePoint Business Users Grouphttp://www.meetup.com/TSPBUG/
SharePoint Saturday Torontohttp://spbuzz.it/spstoyam
Don’t Miss the Prizes… Xbox One with Kinect Your favorite SharePoint books Training vouchers Office 365 Swag
(tweet #ShareSelfie #spstoronto to win) Vendor gifts and raffle
How did I do?
http://spbuzz.it/spsto14eval
Top Related