SharePoint Usability and Accesibility Best Practices Including 508 Compliance - EPC group


Published on

SharePoint Usability and Accesibility Best Practices Including 508 Compliance - EPC Group - Errin O'Connor and the EPC Group team of experts, we cover 508 compliance and a wide variety of usability best practices (limiting clicks and developing a best practices hierarchy)

Published in: Technology, Design
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Any OS/browser/device doesn’t mean pixel perfect
  • ARIA: ribbon, dialogs, controls
  • SharePoint Usability and Accesibility Best Practices Including 508 Compliance - EPC group

    1. 1. EPC Group’s Overview ofSharePoint 2010: Web Standards, Accessibility and Usability<br />SharePoint Server 2010 - Web Content Management and Usability Standards Best Practices<br />By: EPC<br />
    2. 2. About EPC Group<br />SharePoint 2010 and Project Server 2010 Offerings Include:<br />Enterprise Content Management Systems based on Microsoft SharePoint Server 2010<br />SharePoint 2010 (SharePoint Server 2010 SharePoint Foundation 2010) DoD Compliance Systems<br />Intranet and Internet facing implementations & Health Check and Assessments<br />SharePoint Support Contracts for Organizations throughout the U.S.<br />Custom Application, Web Part, Security Models and Workflow Development<br />Migration initiatives for SharePoint 2007 to 2010 or LiveLink, Documentum, FileNet to SP 2010<br />Tailored SharePoint Training (either onsite or remote)<br />SharePoint Roadmap development: 6, 12, 18, and 24 months<br />Enterprise Metadata Design Retention Schedule Development – True Records Management Experts<br />
    3. 3.
    4. 4. EPC Group Facts<br />Founded in 1999- The Nation’s Oldest and Most Experienced SharePoint Integration Firm (Headquartered in Houston, Texas)<br />Microsoft Gold Certified Partner<br />Member of Microsoft SharePoint and Project Server TAP 2007 & 2010 Beta Test Programs<br />Currently Executed over 640 SharePoint Engagements throughout the Globe<br />History of executing largest SharePoint Deployments in the history of Microsoft SharePoint<br />Patent Pending SharePoint Implementation Methodologies<br />Microsoft SharePoint Foundation 2010 Inside Out Dive in to Microsoft® SharePoint® Foundation 2010<br />Windows® SharePoint® Services 3.0 Inside Out <br />
    5. 5. Founder & CEO: Errin O’Connor<br /><ul><li>Founder of EPC
    6. 6. One of the nation’s leading SharePoint implementation and custom .NET development firms
    7. 7. Currently writing Microsoft SharePoint Foundation 2010 – Inside Out
    8. 8. Author of Windows SharePoint Services 3.0 Inside & Out by Microsoft Press
    9. 9. Has completed 130+ SharePoint Implementations in the Past 8 years
    10. 10. Has worked on some of the largest SharePoint deployments to date (200,000+ Users)
    11. 11. Speaking at the SharePoint Conference 2009 in Las Vegas on SharePoint 2010 Governance and Your Future SharePoint Roadmap</li></li></ul><li>Presentation Objectives<br />You will get to know the most common web standards and accessibility issues users and administrators have with SharePoint Server 2010 as well as SharePoint Foundation 2010<br />You will understand the difference between and the importance of web standards and accessibility (Including 508 Compliance)<br />Note: EPC Group has an upcoming Webinar in JanuaryFebruary 2012 on detailed 508 Compliance as well as PHI and PII data. This webinar will be conducted by Errin O’Connor and EPC Group’s full time legal counsel who is an expert in this field.<br />You will be able to explain the web standards and accessibility investments and ROI of SharePoint 2010<br />6<br />
    12. 12. SharePoint 2010 Accessibility<br />A way to guarantee interoperabilityof the website<br />SharePoint 2010 Supports any Operating System<br />Any browser across multiple platforms, (I.E., Safari, Firefox, Chrome, etc.<br />Any edge device (iPad, etc.)<br />Standards<br />WCAG 1.0/2.0<br />Section 508 (US) HIPPS Related<br />PII and PHI: (Personal Identifiable Information) and (Personal Health Information )<br />Accessibility Levels, Best Practices AD Group, SP Security Groups<br />7<br />
    13. 13. SharePoint 2010 Web standards & Accessibility Best Practices<br />Standards<br />Well-formed XHTML 1.0 Strict<br />WCAG 2.0 Level (Double A)<br />Implemented in SharePoint Foundation 2010<br />Except for<br />Central Administration<br />Settings User Interface<br />Note: The Central Administration and Settings interfaces can also be modified to meet corporate standards<br />
    14. 14. Well-formed vs. Valid XHTML<br />Well-formed XHTML<br />Lower-case tags<br />Self-closing elements<br />Attributes’ values wrapped in quotes<br />In-line elements wrapped in block elements<br />Doctypes everywhere<br />SharePoint 2010 supports<br />Markup for Accessible Rich Internet Applications<br />Not in XHTML DTD!<br />9<br />
    15. 15. Web Standards & SharePoint 2010<br />Grammatical correctness of markup<br />Standards types<br />HTML 4.01<br />XHTML 1.0/1.1<br />Standards levels<br />Transitional<br />Strict<br />Frameset<br />Quirks mode<br />10<br />
    16. 16. Accessibility in SharePoint 2010<br />SharePoint aims at WCAG 2.0 AA<br />WAI:ARIA<br />Accessible Rich Internet Applications<br />Supported by the latest browsers<br />This includes IE 9, Chrome, Firefox, etc.<br />Implemented across the whole platform<br />SharePoint 2010 should always be inplemented with a “SharePoint as a Platform” and “SharePoint as a Service methodology in mind.”<br />11<br />
    17. 17. SharePoint Validation Problem Areas – Best Practices<br />Legacy markups & Customizations can become a major issues in SharePoint 2007 to SharePoint 2010 Branding Migration efforts<br />Silverlight Web Part(s) and where Microsoft is headed technologically (phasing Silverlight out)<br />WebPartZone specified to SharePoint 2010<br />WebPartPage specified to SharePoint 2010<br />ImageField specified to SharePoint 2010<br />Rich Text Editor specified to SharePoint 2010<br />12<br />
    18. 18. Silverlight Plugin Generator<br />Problem<br />SLPG doesn’t escape JavaScript code<br />SLPG uses iframe to solve caching issue with Safari <br />Solution<br />Add comments before loading the JavaScript<br /><script type="text/javascript"><br />//<![CDATA[<br />//]]><br /></script><br />This is meant to phase out the iFrame<br />13<br />
    19. 19. WebPartZones & SharePoint 2010<br />Problem<br />Renders tables around Web Parts<br />Adds non-existing attributes toWeb Part’s div(HasPers, allowDelete, etc.)<br />Solution<br />Custom Control Adapter<br />Override the rendering<br />Drawbacks<br />Breaks WPSC<br />14<br />
    20. 20. WebPartPages and SharePoint<br />Problem<br />Renders hidden Web Part Zone using hidden input fields<br />Input fields directly in the page insteadof wrapped in a div<br />Solution<br />Custom Page Adapter<br />Wrap the contents in a div<br />15<br />
    21. 21. ImageField and SharePoint 2010<br />Problem<br />Uses HTML 4.01 to store the image value<br />Solution<br />In code: retrieve the value asImageFieldValue and write theimg tag yourself<br />In XSLT: This is a more advanced area for skilled SharePoint Subject Matter Experts<br />16<br />
    22. 22. CSS Styles and SharePoint 2010<br />Problem<br />CSS validation returns errors<br />Solution<br />Replacing with your own CSS (Corporately Approved)<br />Drawbacks<br />Requires some serious customization and configuraton<br />17<br />
    23. 23. In-line Styles SharePoint 2010<br />Problem<br />Using style attribute is not allowed<br />Solution<br />Custom Page Adapter<br />Regex replace<br />Drawbacks<br />Very expensive<br />Might loose branding/functionality<br />18<br />
    24. 24. Rich Text Editor SharePoint 2010<br />Problem<br />WAI:ARIA markup not in XHTML DTD<br />Solution<br />Custom Control Adapter<br />Regex replace<br />Drawbacks<br />Expensive on large pages<br />19<br />
    25. 25. JavaScript links<br />Problem<br />Links with href="javascript:"<br />Solution<br />Custom Page Adapter<br />Regex rewrite of links<br />Drawbacks<br />Very expensive<br />Might loose functionality<br />20<br />
    26. 26. Key Lessons Learned<br />Implementing web standards and accessibility in SharePoint 2010 is easier than in SharePoint (MOSS) 2007<br />Plan for accessibility from the begining of the project<br />Accessible branding is the key to success<br />Be careful what you promise<br />Accessibility on the Internet doesmatter<br />21<br />