Do you need to display formulas on your web site? Are you dealing with Arabic, Cyrillic, or other alphabets where translation to the Web can be difficult? Come to this session to learn a few tools and techniques for displaying this content on the web, while at the same time ensuring your design meets accessibility standards.
Experience Level: Beginner - Assumes no prior knowledge of topic. Prerequisite Knowledge: Familiarity with a foreign language or math notation. The ability to add 2+2, at least most of the time. Skills/Knowledge Gained: Understanding of language tagging, benefits of basic Unicode, use of LaTEX in Drupal, and optimal equation formats for accessibility.
Usability has come a long way since the dark days before "Designing with Web Standards". Now nearly all companies see the value of UX in their digital designs. But despite heightened focus on the user and a growing awareness of accessibility concerns, implementation of accessibility standards have often fallen victim to time pressures and obsolete design practices. Disabled users struggle through sites missing alt tags, keyboard inputs or text alternatives. Enter devices like the iPhone & Android … and the iPad. With the proliferation of non-desktop devices and browsers like tablets and gestural smartphones, suddenly more people are finding that the web isn't as nice and clean as they remembered: broken formatting, too small text, hover functionality that doesn’t work, and entire swaths of the web rendered as Flash-based wastelands that millions can’t access. We've now discovered that by solving for many of the issues that iOS and other mobile users face, we can also solve for the most prevalent accessibility issues. Using side-by-side examples and case studies, I'll show how we can make sites more accessible and more usable by mobile devices. Through combinations of better markup, HTML5 and CSS3 functionality and better scripting, we can serve two masters at once. Better yet, in some cases, we can take advantage of the accessibility capabilities built into newer mobile devices to make the digital experience even better than they would get on the 'old web'.
Experience Level: Intermediate - Assumes basic knowledge of topic and some experience. Prerequisite Knowledge: Basic knowledge of accessibility, HTML and CSS preferable; some knowledge of the mobile design space would be beneficial. Skills/Knowledge Gained: 1. How do the needs of accessibility intersect with the needs of mobile users (particularly iOS)? 2. What can we do in the markup to address the needs of both? 3. How can I use media queries to selectively address the needs? 4. How can I improve my non-mobile sites to be more accessible? 5. How can we take advantage of the inherent accessibility functionality within mobile devices to enhance the experience.
Join us for an update on Penn State's Accessible Information Technology Initiative. This work is gaining a lot of traction and making quick progress. We'll talk about Hi Software, our new accessibility scanning software, the Triage approach to website remediation, and the many resources and trainings that are available to the Penn State web community. Who said web accessibility was hard? Bring your questions and comments and join the conversation.
One of the universal truths in the world of software and web development is that the less bugs in a system the more money is saved and more human resources can be applied to new development that adds value. The best way to reach the goal is to avoid the bugs in the first place – which typically requires testing the system regularly during the software development lifecycle. When it comes to accessibility testing it is often the case that testing is not performed on systems until after the system has been released to users. In such a scenario, an organization’s level of risk is at its highest, as people are using the system. Therefore the organization and its developers require sufficiently informative data output from the accessibility testing which is detailed, clear, and actionable. It doesn’t do the system’s owner any good to deliver a report filled with a bunch of accessibility violations unless that report also includes information to help them fix their problems. They need to know what their problems are, where their problems are, and how to fix them. There’s also an additional item they need to know: When to fix them. Experience Level:
Beginner - Assumes no prior knowledge of topic. Prerequisite Knowledge: Basic knowledge of web accessibility would be beneficial but not required. Skills/Knowledge Gained:
Attendees will come to understand the various concerns when determining how to manage the remediation of accessibility problems in websites and web-based applications to avoid unnecessary strain on budgets and resources while providing high positive impact for users with disabilities.
You have an accessibility policy in place. Your university has training and checklists to guide web developers, designers, editors and quality assurance testers. How do you know if you are making progress? How do you keep yourself and your colleagues motivated to make and maintain an accessible web? Glenda Sims will share gems from her 10+ years of experience as the accessibility goddess of the University of Texas at Austin, as well as insight she has gained from working with Fortune 500 companies as a consultant. Equip yourself with her DIY techniques for creating an accessible culture on your campus that includes an accessible web design process, competitions, leader boards, open campus reporting and rewards that light the accessibility fire within. Experience Level: Intermediate - Assumes basic knowledge of topic and some experience. Prerequisite Knowledge: This class will be most helpful to people who are already aware of web accessibility concepts. However, it can still be useful to people who are quite new to accessibility. Skills/Knowledge Gained: How to determine if you have all the foundational ingredients for a culture of accessibility. How to set priorities that are motivating, achievable and intrinsically satisfying. The accessible web design process. How to design a leader board and share it internally with your campus web makers. How to reward significant progress in accessibility.
Creating and delivering accessible content is easier than you might realize, and it is a must
Whether you are creating accessible web pages, interactive projects, web meeting, or PDF files, a little preparation goes a long way towards creating an accessible document. During this session, you will learn the foundation information you will need to create projects that meet various accessibility standards and see the tools you can employ to continually improve the accessible nature of the work you do. We discuss four topic areas:
Adobe Acrobat and PDF (30 min)
Creating and publishing accessible content in a PDF file
As a standard digital document, the PDF is an important part of any information sharing process. However, it is crucial to ensure that the information contained within the document is accessible to your entire audience—not just segments of it. During this session, you will learn how to create an accessible PDF in the first place, determine if a PDF is accessible, and to intervene in a PDF that lacks accessibility.
Adobe Dreamweaver CS5.5 and HTML—including HTML5 (30 min)
Ensuring the accessibility of your web content
HTML is one of the most common ways to deliver content today, and much if it is not accessible at all. With some basic shifts in thinking and a few workflow adjustments, you can better plan for and create accessible HTML. You will learn about the needs for HTML and the ways to create accessible HTML with Adobe Dreamweaver.
Adobe Flash Professional CS5.5 and the Flash platform (30 min)
Interactive projects that can be used by the entire community
It is a misconception that Flash is not accessible. Much like HTML, it depends on the way you create it—and how the project you create with Flash has been built. During this session you learn the 5 best-practice ways to create an accessible Flash project and the mistakes to avoid when creating a project that would make the project inaccessible to your audience.
Adobe Connect 8 (30 min)
eLearning from the perspective of accessible content
Any web conferencing solution will have a major need for accessibility. In the latest version of Connect, there are several features that allow people to take advantage of the content in your web meeting no matter who they are. You will see how to leverage that work with keyboard shortcuts, accessible content within Connect, and by adding Closed Captioning to your meetings.
Testing websites for accessibility with automated tools provides much useful information – especially with respect to conformance to technical standards. Unfortunately websites can conform to standards and still prove highly unusable for people with disabilities. This session proposes that for accessibility evaluations to be fully effective they should include contributions from three types of examination: (1) use of automated tools where appropriate, (2) human inspection of the underlying code used in the site, and (3) having examiners with disabilities do hands-on user testing of key portions of the site following a use-case oriented protocol. User testing by people with disabilities not only quickly identifies technical barriers but also surfaces significant usability issues resulting from errors of omission and points of ambiguity that will often be missed by automated testing and by human testing done by those not facing the challenges that users with disabilities must contend with. This session will discuss the critical importance of including skilled user testing when evaluation websites and web-based applications for accessibility.
Adobe CQ5 has been developed to maximize compliance with the Web Content Accessibility Guidelines 2.0 (WCAG) from the World Wide Web Consortium (W3C). This session will highlight and demonstrate some of these key accessibility features which enable compliance with regulations such as Section 508. In addition, best-practices and recommended implementation approaches with be presented.
Penn State now requires that videos that are available to the general public should be made accessible. You could pay $150 per hour of video to send it out to be captioned, or you can do it yourself for free using MovieCaptioner. MovieCaptioner is a cross-platform application that allows you to listen to the audio in short snippets and type what you hear. It will keep repeating the same snippet of the movie until you have what you hear typed. Then hitting the Return key will record the caption and the timecode associated with it and advance you to the next snippet of the movie. When you're all done typing in the captions, it's a simple matter of exporting to many different formats, including YouTube, JW Player, SCC (for iPods and broadcasting), Flash, STL and Adobe Encore for DVDs, and will export text transcripts as well. This session will be a demo of how to use the software and uploading captions to YouTube will be demonstrated as well. Each attendee can get a free copy of MovieCaptioner to use on their own computer. Experience Level: Beginner - Assumes no prior knowledge of topic. Prerequisite Knowledge:
No prerequisite knowledge needed. The software only requires some typing skills. Skills/Knowledge Gained:
Attendees will be able to use MovieCaptioner.