Your SlideShare is downloading. ×
0
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Enterprise Web Accessibility: Unified Accessible Design & Accessible Code Frameworks #CSUN13

191

Published on

Presentation at #CSUN13 Conference on Enterprise Web Accessibility. Co-presented with State Farm Insurance Company, who offers their perspective on the topic, along with IBM's.

Presentation at #CSUN13 Conference on Enterprise Web Accessibility. Co-presented with State Farm Insurance Company, who offers their perspective on the topic, along with IBM's.

Published in: Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
191
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • SF Background
    International workforce = greater understanding of need for a11y, as a11y is already required in many countries outside of the US
    State Farm has a strong understanding of accommodations needs for employees, agents and agent staff. However, accommodations are not the same as a11y.
  • State Farm did not ignore a11y in the past, but like many other companies, we were going about it the wrong way. SF has had an a11y team for several years, but the way we approached a11y made it difficult for projects to implement accessible products. Now this is not unique to SF—so many other organizations do or have done the same thing. Some of the roadblocks we faced were…
  • Confusion about what a11y really is—many believed SF accommodations policy covered a11y needs—more a11y team’s fault than theirs (while related, accommodations and a11y are not the same).
    A11y not part of project development life cycle
    Infrastructure
    Lack of formalized policy
    Lack of tools that support a11y (e.g., authoring and testing tools)
    A11y training for all involved in the UI (e.g., content authors, designers, developers, testers)
    (Listed roadblocks are all industry-wide problems)
  • (Listed roadblocks are all industry-wide problems)
    A11y was thought of as only a developer issue
    A11y wasn’t included in project planning. So when asked to include a11y, projects (rightly so) considered it an added feature and questioned its value.
    Some projects did consider a11y, but logging and tracking identified issues was difficult.
    Even when projects understood the importance of a11y, the experts were typically contacted just before the product went to production. By then, it was too late.
    Statefarm.com and statefarm.ca are huge. Where to start? And…
  • How were two people going to make it happen? I’ll share with you what we did to get to the point we’re at with a11y. But, first, I want to make something perfectly clear.
  • Contrary to what you may have heard, a11y is not easy. It’s true that there are ways to resolve a11y issues easily in design and development. But, a11y is so much more than design and development.
  • So many areas are involved in creating an a11y product.
  • Building relationships isn’t easy and takes time, but is key to getting your message out there.
    Be the go-to guy/gal: Become the one people know to come to when they need help—not just a11y help. <Talk about lead dev. experience before joining a11y team—contacts made, skills gained, and how knowledge used to help projects that asked for a11y help>
    Don’t wait for them to come to you: Accessibility road show <Talk about how many didn’t know our team existed until we started getting out there talking to them and giving lots of presos.>
    Offer solutions, not roadblocks: Give projects ways to resolve a11y issues. Don’t just tell them their product isn’t a11y.
    Become an advocate: Be willing to stick your neck out for your allies to help them on their road to a11y. (e.g., talk to PM, sponsor, etc. on why product should be delayed to resolve a11y issues)
    Don’t ignore “little guys”: You may be surprised at how effective lower-level folks can be as allies.
    Grass roots efforts: A strong grass roots efforts can be very effective in getting leadership support.
    Allies in area owning statefarm.com and statefarm.ca helped us achieve our first big win on the road to a11y.
  • AODA
    The area supporting statefarm.ca wanted to know if State Farm Canada conformed to WCAG 2.0 Level A and AA success criteria per AODA Integrated A11y Standards requirements.
    The accessibility team partnered with the business area responsible for statefarm.ca.
    Lack of internal a11y resources required us to hire a11y specialists from outside State Farm to audit dotca.
    Audit findings helped us start the process to make a11y an Enterprise-level requirement
  • We used the statefarm.ca audit results to help build our business case.
    Our allies helped us reach folks in key areas who then helped us refine the business case.
    AODA Integrated Accessibility Standards compliance issues helped us escalate the business case to executive-level leadership quickly.
    While executive-level leadership agreed AODA compliance issues were important, the reason heard most often for approving the business case was that a11y would offer a better customer experience.
  • Business case approval was just a first step. Getting enough executive-level buy-in was a bit of a challenge.
    First of all, confusion still existed about what a11y was, what work needed to be done, and why SF needed to do the work. Multiple meetings helped to clear up the confusion.
    We soon realized that one executive-level advocate / champion was not enough. There were just too many areas involved, and it was imperative to get buy-in from each area in order for a11y work to go smoothly.
    We finally got the executive-level support needed to go forward.
  • There was so much involved, we knew we couldn’t do this on our own, so we hired an a11y firm to help
    Identify the current state of a11y at SF
    Resolve immediate issues
    Identify next steps
    Education about the need of a11y continues as new leadership becomes involved.
    Ongoing discussions on who should “own” a11y. Should it be the business side, the technical side, or a combination of the two?
  • New a11y roles were identified and will be implemented in the near future.
  • It’s still just the two of us, but there is hope in sight. The work will become much more manageable when the a11y PMO, Focal Points, etc. are implemented.
  • QA and fix recommendations alone will not improve WA. When guidance is combined with accessible web components (design standards, templates, widgets), the number of WA defects can be dramatically reduced.

    Web Standards, Templates & Components:
    Develop, maintain integrated web standards (incl. accessibility)
    Develop, test, maintain accessible templates and template generator
    Develop, test, maintain accessible common components

    Ongoing Web Development:
    Develop, test maintain intranet sites conforming to integrated web standards (incl. accessibility)
    Develop, test maintain ibm.com sites conforming to integrated web standards (incl. accessibility)
    Develop, test maintain media / content conforming to integrated web standards (incl. accessibility)

    Monitoring & Periodic, Regular Auditing:
    Rational Policy Tester® Dashboard
    Business Transformation Management System (BTMS)


  • Dojo is a JavaScript® library that provides reusable widgets for building diverse user interfaces.
    Dojo normalizes the idiosyncrasies of developing applications for multiple browsers into a single, write-once, run-on-many-browsers API.
    Dojo enables developers to seamlessly transfer their skills to different projects.
    Because accessibility is built into the Dojo Toolkit core widget library (Dijit), these widgets provide accessibility without additional coding effort.
    Most of the widgets you see on pages are Dojo Dijit widgets: form fields, dropdowns, date pickers, checkboxes, radio buttons, tool tips – all accessible.
  • Dojo is a JavaScript® library that provides reusable widgets for building diverse user interfaces.
    Dojo normalizes the idiosyncrasies of developing applications for multiple browsers into a single, write-once, run-on-many-browsers API.
    Dojo enables developers to seamlessly transfer their skills to different projects.
    Because accessibility is built into the Dojo Toolkit core widget library (Dijit), these widgets provide accessibility without additional coding effort.
    Most of the widgets you see on pages are Dojo Dijit widgets: form fields, dropdowns, date pickers, checkboxes, radio buttons, tool tips – all accessible.
  • BTMT record created – “in production” status
    Web site designed using the accessible template
    Project Tracking Tool (PTT) submission to Global Web Production Services (GWPS)
    GWPS codes Web content
    Test / Regression and return for approval – GWPS testing includes Rational Policy Tester, manual test and JAWS and Return for approval
    Application owner approves
    Application owner enters compliance details in Asset Database via BTMT.
    If non-compliant a CMAD approval and plan required
    Deployed live
    RPT Periodic Audit
    CIO Dashboard provide compliance statistics
  • Transcript

    • 1. What’s Your Message? Enterprise Web Accessibility (WEB-086) Unified Accessible Design & Accessible Code Frameworks Bill Curtis-Davidson, IBM Julie Romanowski, State Farm CSUN Annual International Technology & Persons with Disabilities Conference 1 March 2013 Bill Curtis-Davidson, IBM Human Ability & Accessibility Center Julie Romanowski, State Farm
    • 2. Session Objectives • Provide brief market context for web accessibility • Communicate web accessibility challenges large enterprises have • Share two large enterprise web accessibility case studies: – State Farm® – IBM® • Provide helpful resources related to enterprise web accessibility Slide 2 #CSUN13 – Enterprise Web Accessibility (WEB-086) Unified Accessible Design & Accessible Code Frameworks
    • 3. Market Context Marketplace competitiveness depends on satisfying demands for products and services that meet diverse requirements. Customer expectations are changing: customers expect products to work seamlessly across devices. The world has shifted from paper-based, human- produced, brick-and-mortar market to one where users understand the benefits of and embrace truly connected services. To enable PWDs to use your products, and to meet government regulatory requirements, enterprises must incorporate accessibility into their products, and maintain / report product compliance status. Slide 3 #CSUN13 – Enterprise Web Accessibility (WEB-086) Unified Accessible Design & Accessible Code Frameworks
    • 4. Large Enterprise Web Accessibility Challenges Slide 4 #CSUN13 – Enterprise Web Accessibility (WEB-086) Unified Accessible Design & Accessible Code Frameworks Develop or source a range of complex software products and services Lack of mature process for web accessibility (including documenting of standards conformance) makes it difficult to respond to customer accessibility questions It is not practical for each team to implement its own version of accessibility, track accessibility status and generate accessibility status reports. Large number of development efforts / product offerings makes it difficult / costly for each organization to implement accessibility
    • 5. #CSUN13 – Enterprise Web Accessibility (WEB-086) Unified Accessible Design & Accessible Code Frameworks To Address These Challenges… Slide 5 #CSUN13 – Enterprise Web Accessibility (WEB-086) Unified Accessible Design & Accessible Code Frameworks … an enterprise accessibility process, which includes governance, procedures, development, testing, tracking and reporting is needed.
    • 6. State Farm® Case Study #CSUN13 – Enterprise Web Accessibility (WEB-086) Unified Accessible Design & Accessible Code Frameworks
    • 7. State Farm Accessibility Team Tim Harshbarger • 23 years at State Farm • 19 years on SF A11y Team Julie Romanowski • 12 years at State Farm • 5 years on SF A11y Team • 15 years developer experience 7#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 8. State Farm Background • Mutual company owned by its policyholders • Ranked No. 43 on the 2012 Fortune 500 list of largest companies • 17,800 agents • 65,000 employees • 81 million policies and accounts –79 million auto, home, life and health policies in the United States and Canada –2 million bank accounts 8#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 9. State Farm Background • Located in Bloomington, IL • Diverse workforce • Customer focus and ongoing initiatives to improve user experience • Established accommodations policies –Employees –Agents –Agents Staff 9#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 10. State Farm Case Study Past Experiences 10#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 11. Common Accessibility Roadblocks • Confusion about accessibility • Lack of accessibility infrastructure –Policy & procedure not formalized –Not part of process –Lack of tools –Lack of formal training –Lack of skilled specialists 11#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 12. Common Accessibility Roadblocks • Focused on the code • A feature, not a requirement • No consistent way for projects to log and track issues • Accessibility team contacted too late • Institutional Complexity 12#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 13. Just the Two of Us 13#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 14. Accessibility IS NOT Easy! 14#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 15. Accessibility – 7 Key Areas • Integration – Strategy, Policies, Standards – Methodology – Digital Foundations – Accessibility Tool Standards – Life Cycle Consulting • Resources – Staffing – Materials & Tools • Knowledge – Training & Education – Awareness Communications – External Skills Building • Quality – Web Accessibility Standards Conformance Quality – Customer Care Quality • Reporting – Web Accessibility Standards Conformance Reporting – Accessibility Program Status & Progress Reporting • Procurement – Accessibility Procurement Guidance – Standard Contract Language • Operations – Organization Change Management – Risk Management 15#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 16. How We Started – First Steps State Farm Case Study 16#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 17. Building Relationships • Be the go-to guy/gal • Don’t wait for them to come to you • Offer solutions, not roadblocks • Become an advocate • Grass roots efforts can be very effective • Don’t ignore the “little guys/gals” 17#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 18. AODA & statefarm.ca • Integrated Accessibility Standards • Partnered with area supporting statefarm.ca • Hired outside a11y specialists • Detailed audit of statefarm.ca –Identified WCAG 2.0 Level A and AA conformance issues –Started the process to make accessibility an Enterprise-level requirement 18#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 19. Building a Business Case • Audit results helped build business case • Allies helped reach folks in key areas • Key areas helped to refine business case • AODA compliance issues helped escalate business case to the executive level • Better customer experience sealed the deal 19#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 20. Getting Executive Buy-in • Business case approval just a first step • Confusion still existed –What work needs to be done and why –Many still did not understand a11y • One executive-level advocate is not enough –Too many areas involved –Buy-in required from each area 20#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 21. State Farm Case Study Current Accessibility Efforts 21#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 22. Current Accessibility Work • Hired outside accessibility firm to help –Identify current state –Resolve immediate issues –Identify next steps • Continue to educate areas about need • Ownership – Business side, Technical side or both? 22#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 23. State Farm Case Study Near Future 23#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 24. Next Steps – Accessibility PMO • “Stand-Up” Accessibility PMO with recommended processes and organization to support wide-scale accessibility integrations across all development centers • Develop initial, basic compliance collection and reporting mechanism to meet AODA regulatory obligations • Continue accessibility push, test tooling and process deployment, compliance process are key 24#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 25. Next Steps – Focal Point Plan • Provide an approach to address accessibility staffing resources for development centers • Serve as a foundation for Focal Points to use in order to build detailed plans for their development centers • Focal Point staffing according to needs of each development center 25#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 26. Next Steps – Accessibility Training • Develop training program and training deployment method • Deploy wide-scale training across development center teams • General accessibility and role-specific training required for AODA compliance 26#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 27. Next Steps – Accessibility Roles • Program Leader • Enterprise Liaison • Compliance Leader • Project Management • Technical Integration Leader • Training Developer • Training Delivery Specialist • Development Center Focal Point 27#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 28. Still Just the Two of Us 28#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 29. Contact Info Tim Harshbarger, 309-766-0154 tim.harshbarger.cqwg@statefarm.com Julie Romanowski 309-735-5248 julie.romanowski.l87g@statefarm.com 29#CSUN13 WEB-086 – Enterprise Web Accessibility – 1 March 2013
    • 30. IBM® Case Study #CSUN13 – Enterprise Web Accessibility (WEB-086) Unified Accessible Design & Accessible Code Frameworks
    • 31. Slide 31 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Topics – IBM Case Study • Accessibility Governance in IBM • Web Accessibility @ IBM – Approach – Accessibility Standards – Accessible Templates & Common Components – Accessibility in Ongoing Web Development – Standard Accessibility Testing Tools – Regular Accessibility Audits & Monitoring • Helping Clients Operationalize Web Accessibility
    • 32. Slide 32 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Accessibility Governance in IBM Office of the CIO I/T Governance (Enterprise-Wide Corporate Policy CI-162, Compliance/Audit Tools, etc.) Human Resources Employment, Accommodations & Development Policies (Policy: ADA, DDA, etc.) Human Ability & Accessibility Center Accessibility Rules / SME (Checklists, Training, Advice)
    • 33. Slide 33 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study IBM Web Accessibility Approach • Web Accessibility Compliance led by CIO Team, Supported by Human Ability & Accessibility Center – Transformation executive with overall compliance responsibility – Chief Accessibility Architect (Senior Technical Staff Member) – Accessibility Development & Testing SMEs (HA&AC & CIO) • Deployed sites must follow global design standard (v17), templates and use common components where possible – External (ibm.com) and intranet (w3) web standards merged – Accessibility standards conformance “built-in” • Standards conformance automated and integrated – IBM Rational Policy Tester® used to verify conformance where possible – Assistive technology and expert manual inspections completed as well – Integrated with business transformation management systems
    • 34. Slide 34 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Web Accessibility: Integrated Processes Web Standards, Templates & Components Ongoing Web Development Monitoring & Periodic, Regular Auditing Common Accessible ComponentLibrary Media & Content Libraries Ibm.com websites (external) w3.ibm.com intranet sites Model Monitor Manage Automated Tool Testing & Dashboards Business Transformation Management System (BTMS)
    • 35. Slide 35 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Integrated Web Design Standard Includes Accessibility • Include consideration for web accessibility • Links to accessible web templates and components • Links to online communities Compliance must be easy, repeatable, and built-in
    • 36. Slide 36 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Accessible Web Templates / Template Generator • Core templates designed to include web accessibility support (e.g. ARIA landmarks, navigation, masthead/footer, etc.) • Template generator helps propagate accessibility standards-conforming templates across enterprise Compliance must be easy, repeatable, and built-in
    • 37. Slide 37 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Accessible Common Web Components • Common Dojo multi-browser widgets deployed enterprise-wide, with WA built in. • Reusable widget code helps developers build diverse, consistent, user interfaces. • Because accessibility is built into the Dojo Toolkit core widget library (Dijit), these widgets provide accessibility without additional coding effort. • Combined with accessible templates, helps reduce the number of WA defects. Compliance must be easy, repeatable, and built-in
    • 38. Slide 38 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Accessible Component Example: Navigation • Many users cannot use a mouse, so websites should be keyboard accessible – Previously that meant being able to tab through the entire page. • Navigation menus are a key area where keyboard access is critical – Drop-down menus can be problematic, keyboard users often have to TAB through every single link in menus – IBM built-in keyboard access to navigation components – Users TAB into navigation menu, use ARROW KEYS to navigate around links inside menu - OR - skip them.
    • 39. Slide 39 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Ongoing (Accessible) Web Development • Internal and external web teams adhere to unified design standard, use accessible template generator and common components where possible • Designers and developers follow accessibility guidance from Human Ability & Accessibility Center for custom, 3rd party components • Content management teams produce accessible content / media • Testers perform accessibility verification testing to verify conformance to web accessibility standards w3 Intranet Ibm.com media
    • 40. Slide 40 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Iterative Web Design, Templating, Content Dev, Coding & Testing FAIL Example Web Development Process (ibm.com) Create BTMS* Record Web Design GWPS** Templates & Widgets GWPS** Coding & Content Accessible Template Generator & Widgets Accessibility Developer Checklists GWPS** Testing Accessibility Testing Checklists & Tools App Owner Approval Enter into Web Asset Database Web A11y Pre-Deploy Testing Accessibility Testing Checklists & Tools DEFECTS DEFECTS PASS Deploy into Production Periodic Audit BTMS Dashboard Monitoring Automated Accessibility Testing Tools Including Accessibility * BTMS = Business Transformation Management System ** GWPS = Global Web Production System
    • 41. Slide 41 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Regular Accessibility Auditing Approach • Two prong approach helps IBM address both quality and accountability for web accessibility. Bottom Up Top Down  Scheduled website crawler and analysis – Rational Policy Tester®  Reporting to business units – By Project, by Page, by Error – Each unit manages fix process  Reported in CIO Dashboard  BTMs Analysis – CI162 (IBM WA Policy) Status – Exceptions in Place (Not Expired) – Exceptions Expired  Reporting to business units – By project – Unit manages fix process  Reported in CIO Dashboard
    • 42. Slide 42 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Accessibility Tools: Rational Policy Tester® • Automated Web testing tool • Used for both pre-deployment testing and periodic automated audits • Improves reliability of enterprise web applications • Uses automated error prevention technology: – Including critical checks for conformance to Web accessibility standards such as WCAG 2.0 – Rulesets can be customized to check only for violations to accessibility standards that are reliably checkable with automated tool • Deployed across IBM enterprise-wide • Improves efficiency, saves time, reduces cost
    • 43. Slide 43 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Accessibility Tools: Rational Policy Tester®
    • 44. Slide 44 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Business Transformation Management System (BTMS) & Accessibility • All app owners maintain a BTMS record • BTMS records are linked to an Asset Accessibility DB • Asset Accessibility DB stores completed accessibility verification test (standards conformance) info • Assets which do not conform to accessibility standards require exception – Executive sign-off required on all exceptions – Exceptions not approved without a firm plan to become standards conforming • Consistent mechanism saves time, improves quality of conformance tracking
    • 45. Slide 45 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study CIO Digital Systems Dashboard • Web-based CIO Dashboard includes automated compliance reports on the top 2000 pages by traffic • Draws from Rational Policy Tester® automated audits Accessibility (CI162)
    • 46. Slide 46 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study CIO Digital Systems Dashboard (2)
    • 47. Slide 47 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study IBM Can Help Clients Operationalize Web Accessibility • Strategic Accessibility Services – Discovery Workshop – Strategy and Roadmap Planning – Governance and Policy Formation – Core Design and/or Development Framework Accessibility Assessment • Accessibility Integration Services – Accessibility Assessments – Accessible Web and Application Design – I/T Accessibility Development & Test Integration – I/T Accessibility Operational Model & Plan – Accessibility Training Modules & Services – I/T Accessibility Marketing & Communications – Rich Digital Media Captioning Services • Accessibility Compliance Management Services – Compliance Monitoring and Tracking Services – I.T. Accessibility Outsourced Staffing Services
    • 48. Slide 48 © 2013 IBM Corporation #CSUN13 – WEB-086 – Enterprise Web Accessibility: IBM Case Study Contact Information • Bill Curtis-Davidson Business Development & Solutions Leader IBM Human Ability & Accessibility Center http://www.ibm.com/able/ • Email: wacurtis@us.ibm.com Twitter: @BCurtisDavidson IBM Accessibility IBMAccess IBM Accessibility
    • 49. Q&A and Resources #CSUN13 – Enterprise Web Accessibility (WEB-086) Unified Accessible Design & Accessible Code Frameworks IBM Human Ability & Accessibility Center, “Accessibility At IBM: An Integrated Approach to Accessibility,” http://www.ibm.com/able/access_ibm/exec brief.html Groves, Karl. “Managing Web Accessibility in the Enterprise”, March 2011, CSUN Presentation: http://www.karlgroves.com/2011/03/23/ma naging-accessibility-compliance-in-the- enterprise/ Loiacono, Eleanor T., Nicholas C. Romano, Jr., Scott McCoy; “The state of corporate website accessibility”, Communications of the ACM, Vol 52 Iss 9, Sept 2009 , http://dl.acm.org/citation.cfm?id=1562197 W3C, “Developing a Web Accessibility Business Case for Your Organization”, http://www.w3.org/WAI/bcase/

    ×