Access U Conference Summary


Published on

Summary of "Access U" Conference Report

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

  • Be the first to like this

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

No notes for slide

Access U Conference Summary

  1. 1. Access U Conference Summary Andrea Hill - May 2007
  2. 2. Overview <ul><li>In early May, I attended “Access U” in Austin, Texas. There were numerous sessions running at the same time, but there were not official ‘tracks’ per se. As a result, I changed my course selection numerous times leading up to the event. </li></ul><ul><li>I would place the sessions I went to into a few different categories: </li></ul><ul><li>Organizational Change/Management Level </li></ul><ul><ul><li>Enterprise Accessibility Compliance Concepts </li></ul></ul><ul><ul><li>Moving Large Organizations Towards Accessibility and Standards </li></ul></ul><ul><li>Users Experiences </li></ul><ul><ul><li>How We Use The Web </li></ul></ul><ul><ul><li>Crystal Vision – Freedom Scientific </li></ul></ul><ul><li>Coding Practices </li></ul><ul><ul><li>Accessible Forms </li></ul></ul><ul><ul><li>Designing for Accessibility: Beauty Secrets of the CSS Masters </li></ul></ul><ul><li>General Accessibility Concepts </li></ul><ul><ul><li>Accessibility- What NOT to do. </li></ul></ul><ul><ul><li>Accessibility Forum </li></ul></ul><ul><li>Testing </li></ul><ul><ul><li>Testing for Web Accessibility </li></ul></ul>
  3. 3. Organizational Change/Management (1) <ul><li>There was much reference to the WebAIM 8-Step Implementation Model , which is as follows: </li></ul><ul><li>Gather baseline information </li></ul><ul><li>Gain top-level support </li></ul><ul><li>Organize a web accessibility committee </li></ul><ul><li>Define a standard </li></ul><ul><li>Create an implementation plan </li></ul><ul><li>Provide training and technical support </li></ul><ul><li>Monitor conformance </li></ul><ul><li>Remain flexible through the changes </li></ul><ul><li>I was really interested in the question of “who owns accessibility” within the organization. In one session, it was divided between content authors, testers and management. </li></ul><ul><li>The other session didn’t mention specific groups or individuals, but spoken of the environment, and many different roles were part of that: </li></ul><ul><ul><li>Public presence: marketing, sales, corporate image/branding, public relations, investor relations, legal </li></ul></ul><ul><ul><li>Internal presence: information sharing/management, internal communications, employee development/relations, team building, business tools </li></ul></ul><ul><ul><li>Content sources: web developers, authors </li></ul></ul><ul><ul><li>Content managers: information resources (IR/IT), webmasters, department managers, PR, contractors </li></ul></ul><ul><ul><li>Content diversity: static pages, dynamic pages, web apps, Flash/audio/MM, PDF </li></ul></ul><ul><ul><li>Technological diversity: CMS, WYSIWYG, AJAX, Server and DB technologies </li></ul></ul><ul><ul><li>Other concerns: security, resource management, productivity/efficiency, customer satisfaction, cost control </li></ul></ul>
  4. 4. Organizational Change/Management (2) <ul><li>The session on “Moving Large Organizations Towards Accessibility and Standards“ was very interesting as it spoke of framing accessibility not as an altruistic or sales-motivated action, but rather one of QA. Working within established standards would facilitate testing and increase overall product quality. Looking at it this way can help sell accessibility to a company, with tangible returns. </li></ul><ul><li>We can’t expect everything to be compliant overnight, must prioritize. For example: </li></ul><ul><ul><li>Compliant (immediately, no excuses) : All new or revised pages, top 10% visited pages, critical pages </li></ul></ul><ul><ul><li>Compliant by (date) : legacy resources (encourages archive of old/outdated pages) </li></ul></ul><ul><li>Overall, I came out of these sessions with a better understanding of how I could ‘sell’ accessibility within my organization. As I told one of the presenters, his single session had justified my attendance at Access U. </li></ul><ul><li>Soon after returning to work, I presented the ‘8-Step Implementation Model’ with notes as to the current status of my organization to management, it was well-received. </li></ul>
  5. 5. Users Experiences <ul><li>These were very interesting sessions. I would say I gained the most personal insights from these. Blind users showed us how they used the JAWS screen readers to surf the web. I used this opportunity to ask specific questions about accesskeys and changing user settings to optimize the use of a specific web application. </li></ul><ul><li>The results were different than what I had heard in the past. These users were willing to make changes to their settings, looking for the most effective way to work. In contrast, I had heard that users did not change from the default settings. The information I received from the users allowed me to consider ways we could leverage the power of assistive technologies. </li></ul><ul><li>For example, evidently there is a way for users to set ‘custom labels’ on input fields. This is a way for users to deal with poorly coded sites, but I saw it as the opportunity for us to offer supplemental information. Although these labels are set by the user, there is a way to export them, to share with others. So therefore it would be possible to set custom labels across a product, then export this file and offer it to users “to optimize your product use”. Yes, it would require some overhead, and I am not sure how exactly they are tied to the specific input fields and what would happen if a page changed at all, but it was still an idea that got me thinking. </li></ul><ul><li>The one challenge, of course, is needing to remember that “optimizing for blind JAWS users” is not the same as making a product accessible.. </li></ul>
  6. 6. Coding Practices <ul><li>I attended two sessions related to specific coding practices for achieving accessibility on the web. Most of our products are forms and we have definitely had some challenges so I was really looking forward to the forms session. I was less excited about the CSS session. </li></ul><ul><li>The forms session was well organized, with plenty of examples for us to go through. Unfortunately, I found that the level of complexity of the forms we are trying to build is above what we would go over in class. It was, however, a good opportunity for me to confirm that we have the basics (labels, etc) down. </li></ul><ul><li>The CSS session was actually quite good. The speaker went through an enormous amount of material, thankfully captured on the 10sharpdesign website . I will admit I had an “oops” moment when she talked about using links with background images, and how with CSS and images turned off, the user gets nothing. I guess we should stop doing that… </li></ul><ul><li>Although the forms session disappointed a bit, I felt both would have been great for people who were a bit less familiar with coding for accessibility. </li></ul>
  7. 7. General Accessibility <ul><li>I wasn’t sure about these ‘general accessibility sessions’ but in the end, they were great for simply getting my mind going. Glenda Sims presented the “ Accessibility – What NOT to do ” session and I really enjoyed just hearing her stance as someone actively working in the field. The biggest take-away message I got was that the field and our understanding of it and the best practices and techniques are ever-evolving. We shouldn’t be so afraid of not doing something exactly right that we don’t do anything at all. She spoke specifically of ‘skip-nav’. This is probably the first aspect of ‘how to make a site accessible’ that people learn about. Yet Glenda introduced an article she’d written that basically showed that skip-nav is no longer as necessary for users of assistive technologies. </li></ul><ul><li>Something she mentioned really floored me - they ran user testing and the users of assistive technology were able to perform the tasks quicker than sighted users: they were not distracted by the visuals. This is in stark contrast to what we’ve seen in testing, but it gives me hope! </li></ul><ul><li>One thing that was mentioned again and again, was ‘ask the users’. We can only assume so much. This is also an issue of working towards making something actually accessible and usable, rather than compliant. She also mentioned an article by Shawn Lawton Henry about user testing: Just Ask ! </li></ul>
  8. 8. Testing <ul><li>My last session of the conference was Testing for Web Accessibility by Jim Thatcher. I’ll admit, I was a bit awed to hear him speak. The session was well-run, we had a survey to fill out before and after the session, on how much of the WCAG guidelines were able to be tested automatically, about which version of the various types of guidelines and standards were most easily tested, etc. It helped frame the talk. </li></ul><ul><li>Jim went over a number of different testing tools, and basically showed how automated testing really isn’t very effective. He cited an article by Gez Lemon that showed how many free tools aren’t worth their price ;) He also did a review of some different tools, with the results at his site . I took notes all through the presentation and still missed capturing so much of it: </li></ul><ul><li>Ultimately I suppose the main thing to keep in mind is that although it is a daunting task, we have to test, and we can’t rely on automation. IBM managed to get it down to three minutes per page to test. </li></ul>
  9. 9. Summary <ul><li>I am really thankful to have had the opportunity to attend Access U. As much as the sessions were useful, I was also grateful for the opportunity to meet with other attendees as well as the presenters. It was great to hear so many people speaking about their passion. My only regret is that I live so far away and will unlikely attend ‘Access U’ in the future. Not only did I learn new valuable information to bring back to my workplace, I have a renewed energy and dedication to the field! </li></ul>