Tag Archives: accessibility

The 2016 MMWCon Mega Post

Hey friends,

Once again, it’s time for another one of my conference “mega posts,” this time from the 2016 UCLA Mobile & Modern Web Conference. This mega post links to the notes I took from almost every session I attended, and proves that I was here and learned something. Some of this¬†will be more useful than others…I drifted at times. There was some great work on display at this conference; I always meet awesome people and take away at least a couple gems that I didn’t know going in. As always, any mistakes, omissions or just plain crappy coverage are totally mine. Who knows, I may have even gotten something right ūüėČ Enjoy!

Wednesday, October 14

Thursday, October 15

Friday, October 16


Making Peoplesoft Accessible at the University of Minnesota

Presenter: Hendrix Bodden from GreyHeller

Project Overview

  • Campus views Disability as Diversity
  • Large Peoplesoft installation
  • Self-service was not accessible, but required high customization
  • Upgrade: new version splitting CS/HR databases; accessibility came in at the end; modifying PS pages in-house to make accessible too expensive!
  • Deque provided accessibility assessments
  • Intrasee provided UX

Access & Accessibility: Details

  • Use cases (there were TONS on student and HR)
  • Test User accounts
  • Environments
  • Test data
  • Collaboration tools

Platform-wide accessibility

  • Interaction: all functionality available from keyboard
  • Optimized UX: easy to use
  • Full-featured: parity with desktop use.

Product Demonstration

  • Transformation of the HTML provided by the out of the box Peoplesoft pages (it looks sooo much nicer).
  • Ran the page on an iPad with VoiceOver – this was a powerful demonstration of the proper use of markup.


  • Plug-in to PeopleSoft environment (on the PS web server)
  • Inherits from deployed PeopleSoft system: security rules, all business rules & audits, all calculations, all customizations and bolt-ons made by a customer, all database updates and access
  • Starting point is the PeopleSoft page
  • All back-end logic is the same

Semantic HTML

  • Ensures proper HTML structure: sequence, hierarchy, eliminates extraneous content, proper relationships & roles
  • Eliminates dependency on CSS for proper display
  • Showed a slide of audit of the enrollment shopping cart

Common PeopleSoft HTML Issues

  • Lightboxes
  • Prompt Dialogs
  • Set appropriate values for heading, subheadings, grids
  • Sets presentation mode attributes on read-only tables
  • Associates labels with form fields

Improves Navigation & Taxonomy

  • Sets Aria roles
  • Sets navigation role
  • Adds skip links
  • Tabs & tab structure
  • Links & buttons
  • Navigation menus and submenus

Improving End-User Interaction

  • Highlight content in focus
  • Remember scroll position on reloads, AJAX updates, and other processing

Lessons Learned: Challenges

  • High-level commitment to accessibility
  • Accessibility integrated from day one
  • Changing FTE commitments at U
  • Understanding of fuller picture
  • Immature U processes


The 2015 CSUN Mega Post

Hey there!

When¬†I come to the CSUN conference, I write about every¬†session I attend. ¬†When I’m all done with the conference, I make sure I gather up all my posts into one <echo>MEGA POST</echo>. ¬†In the past, I felt strongly¬†pulled toward the more technical¬†web track sessions, because I run a web development shop. ¬†This year, I sprinkled in¬†some legal and compliance sessions, because the technical stuff doesn’t exist in a vacuum. ¬†That, and I find myself being asked to weigh in on accessibility concerns in senior-level conversations more frequently these days.

I may be a glutton for punishment, but whenever I attend a busy conference that has lots of concurrent sessions throughout the day, I try to attend¬†as many as I can…with no breaks in between. ¬†This year, I got to 18 sessions, and it was pretty tiring. ¬†I think it matters that I get the most “bang for the buck” for attending, and¬†it’s important that I don’t keep what I learn¬†all to¬†myself. ¬†So I take notes. ¬†A LOT OF NOTES. ¬†This helps me stay¬†focused when my mind starts to wander, and it may be useful to others.

I hope you find it useful.

Wednesday, March 4 Session Notes

  1. The Implementation of PDF/UA and Standardized Access to PDF Content
  2. Digital Accessibility: 2015 Annual Legal Update
  3. Accessibility at the BBC
  4. Do We Need to Changes the Web Accessibility Game Plan (Redux)?
  5. Real-Time Conversations:  From TTY to Real-Time Text (RTT)
  6. Aiming for Excellence at a Fortune 50 Company (aka TARGET)

Thursday, March 5 Session Notes

  1. CSS, Accessibility and You
  2. Scaling Web Accessibility From Specialist Niche to Business-As-Usual
  3. Web Compliance Evaluation Strategies – All In One
  4. Accessibility in the Web Project Lifecycle
  5. Accessibility in an Agile World
  6. Revised Maturity Model: Case Study of the CIA

Friday, March 6 Session Notes

  1. Choosing an Accessible UI Framework
  2. Evaluating the Accessibility of Your Website:  New Resources and Tools
  3. 7 Lessons from Developing an Accessible HTML5 Video Player
  4. The Digital Accessibility Maturity Model for Measuring Program Success
  5. A Digitally Inclusive Future for Canada’s National Broadcaster
  6. Purchasing Accessible EIT Products:  A Suggested Campus Procurement Process

Purchasing Accessible EIT Products: A Suggested Campus Procurement Process

Presenters:  Cheryl Pruitt and Dawn Futrell from California State University, CSU Office of the Chancellor, Tom Siechert from California State University, Fresno, Susan Cullen from California State University, Northridge

@seichert | @cullensus

This was my sixth¬†session and final session at the CSUN conference on Friday, March 6. ¬†Showing some love to my CSU people before heading home. ¬† I should be able to avoid some of the San Diego – Los Angeles traffic, but not all of it ūüôĀ ¬†Anyway,¬†procurement is a great place to start when ensuring that you’re meeting accessibility requirements; the CSU has made a commitment to ensuring that everything it buys is accessible.

Controlling Purchasing can be a Daunting Task

  • Implementing accessibility into the purchasing process for a 23-campus system is tough…
  • Every campus implements accessible procurement differently: ¬†different forms, processes and evaluation techniques
  • We Wanted to Break Down the Problem
  • Document the process that can be adopted and adapted by every campus
  • Expectations: ¬†buy the most accessibile products, create a plan for providing accommodations, promote a culture of accessibility,¬†institution wide ever, speak with one voice
  • We have¬†7 people/campuses on the ATI standardization team

Findings and recommendations

  • Keys to implementing accessible procurement: ¬†strong sustainable executive level support, roles and responsibilities, shared responsibility across the campus
  • It’s not JUST an ATI process or JUST a procurement process
  • Roles: ¬†ATI designee or other designees, purchase requester, admin support staff, buyer, vendor, IT support staff, disability services staff, executive sponsor

4-step Process for Campuses

Documentation of the steps below can be found here:  http://teachingcommons.cdl.edu/access/procurement_process/index.shtml

  1. Gather information
  2. Review information
  3. Review product
  4. Place order

Equally Effective Alternative Access Process (aka “EEAAP”)

  • Sometimes a product cannot meet everyone’s needs. ¬†The EEAAP is how accommodations will be met for people who cannot be served by the product.


  • Reqs often don’t include critical info: ¬†what are we buying, how will it be used, who will use it, end users reqd to use product, what are future plans for product use
  • Need for speed (RUSH orders)
  • Large numbers of IT purchases
  • Over 1,600 IT items in 2014 were¬†ordered! ¬†About 203 were reviewed for a11y
  • Of those 203, almost 100 were for “smart classrooms,” 44 were for Multi Function Devices, 54 were for departments and colleges, 8 were for students

Procurement + Accessibility

  • Integrate accessibility into the existing procurement process
  • Integration types: ¬†one-size fits all (aka shotgun approach)
  • Impact-based process and intelligent workflow

Review Process

  • Minimum reqs: ¬†needs to work for both reactive and proactive review requests, and needs to work regardless of funding source (i.e. gifts, auxiliaries, etc.)
  • Successful adoption: ¬†easy for end-users, isn’t heavy
  • Tom reviewed a workflow diagram and the CSU online requisition form

Campus Impact Policy – We’re Moving Away from Dollar Thresholds When Reviewing

  • Litigation does not consider product $ amount or if it is free
  • Consideration of level of accessibility and business need
  • We do a functional analysis to determine the overall value of the product. ¬†Sometimes the most accessible product is not the best one.
  • Targeted: ¬†software, applications, devices, copy-scan-fax
  • Not targeted: ¬†servers, security systems, wires & plugs, software for individuals
  • The big cultural change is that people need to start thinking about this when they start thinking about buying the product

Language is the Key to Communications

We need to make sure that the language we’re using makes sense to people who just want to make the right choices.

  • 1194.21 & 22 = modern web applications, software
  • 1194.24 = video, multimedia, YouTube
  • 1194.25 = iPads, Phones, Copy-Scan-fax
  • 1194.31 = usable to individuals with different abilities
  • 1194.41 = documentation for use for individuals with different abilities

Campus Department Requests

  • Bulk purchase and commonly purchased items (i.e. Dell, HP, Lenovo computers)
  • VPAT forms

Universal Design Center Evaluation Categories

  • Alt Descriptions
  • Multimedia
  • Structure
  • Comprehensive Visual Display
  • User Interface
  • Navigation




A Digitally Inclusive Future for Canada’s National Broadcaster

Presenters:  Patrick Dunphy accessibility specialist from the CBC

@PatrickDunphy | Co-lead #a11yTO with George Zamfir (@goodwally) and Billy Gregory (@thebillygregory)

This was my fifth¬†session at the CSUN conference on Friday, March 6. ¬†I’m always interested in hearing about how very large – particularly media companies – approach their accessibility remediation efforts.

What is CBC?

  • We’re a publicly funded Canadian radio, tv, online

2020 Strategy

  • Intensify relationship with citizens with disabilities
  • 13.7% of Canadians self-identify as having a disability (3.8 million)
  • However, no captions for recent olympic coverage
  • Silver tsunami is coming…

We’ve Been Busy!

  • Launched¬†cbc.ca/accessibility to gather feedback on what’s wrong
  • GAAD: ¬†Global Accessibility Awareness Day
  • 4-part learning series
  • Accessibility inquiry form for intake
  • Developing an internal knowledge base (Confluence)
  • Accessibility task force (July 2014) got everyone involved: ¬†IA, design, SME, QA, PM, Apps, Architect, Content, UX, management
  • Jumped into agile in a big way (which was not without it’s bumps)

In October 2014, We Committed to a 4-year Rollout Plan

  • We will make our digital content meet WCAG 2.0 AA standards by April¬†2018. ¬†Digital operations is leading this effort, with 8 product teams using agile methodology.
  • We completed a gap analysis with The Paciello Group
  • Identified training needs
  • WCAG2.0 training for devs, designers, and QA analysts
  • Accessibility requirements identified for 3rd party vendors

Gap Analysis

  • Task force meets weekly
  • First, we reviewed 25 cbc.ca screens across CBC, CBCNews, CBCSports, CBCRadio, Network
  • Summary of gap analysis identified a range of issues likely to significantly affect the ability to interact with CBC.ca; lots of work had been done, and moderate level of effort would be required to get it up to scratch.
  • Screen reader training

Learning & Development Initiatives

  • Lots of checkpoints to think about what we want to get to, and narrowed it down into what was feasible
  • Onboarding process
  • Q&A¬†webinars
  • Moderated forums
  • Printable cheat sheets
  • Code samples
  • Bi-annual training
  • External assistance