Take the #NoMouse Challenge on Global Accessibility Awareness Day

On Thursday, May 19 — Global Accessibility Awareness Day (GAAD) — simply visit your department’s or your favorite website and try to navigate to important content and activate site links with just your keyboard.

The #NoMouse Challenge is a global effort to raise awareness about accessible Web design and offers an opportunity to experience challenges some people with disabilities have while using the Web.

During the challenge, if you were unable to navigate the site or activate site links, take a moment to add keyboard focus (or shortcuts) to the Web page and also inform the site’s webmaster of any challenges you experienced.

For more information about accessible Web design, see:

Remember the purpose of Global Accessibility Awareness Day is to get you talking, thinking and learning about digital (e.g., Web, software, mobile) accessibility and users with different disabilities.

Captioning Grant Available to NC State Faculty

NC State University has established a Captioning Grant to assist faculty in creating accessible videos.

This grant provides funds for faculty to obtain captions for instructional videos used in their online, blended, and face-to-face courses. In addition to providing content to people with hearing impairments, captions create a learning environment that supports Universal Design for Learning.  

Faculty members may apply for funding to caption videos:

  • when a student with a disability requiring an accommodation for captioning registers in a course that contains video, or
  • when proactively captioning videos to enhance the learning environment for all students.

Faculty using their own videos as a central part of their pedagogy are highly encouraged to apply for the grant.

To apply for the grant, complete the Captioning Grant Application Form. Applications to meet the needs of a student requiring this accommodation will be processed immediately. Those for proactive captioning will be processed on March 31 for summer, June 30 for fall, and Oct. 31 for spring courses.

For more information, see Multimedia Accessibility. You may also send your questions to accessibility@ncsu.edu.

Patterns in Higher Education Accessibility Complaints

In recent years there have been several notable legal actions concerning IT accessibility within higher education. When I say “legal action,” that can range from an action from the Office of Civil Rights or the Department of Justice, or it can be from an actual lawsuit.

I went back through the findings and/or settlements from several of the major cases to see what patterns are present to see how that might be helpful for pushing the accessibility conversation forward in higher education.

What this is not

This is not a blueprint for how to make your campus accessible. Simply addressing the issues raised here will only solve some of your problems. What I hope is that this can be a starting point for campuses who want to begin the conversation about creating an accessible IT environment. By starting to talk about these particular issues it can lead a campus to finding and implementing solutions that will deal with IT accessibility holistically.

In addition to helping campuses new to IT accessibility, I hope it can help inform and guide campuses who have been working on accessibility for some time. It’s always good to reexamine where you are and where you are going.

How this is organized

The way these points are organized do not necessarily reflect how any one settlement or finding is organized. Rather, it is organized into functional blocks that I feel make it easier to understand the larger picture being painted.

It also needs to be noted that the following issues do not necessarily reflect all of the issues raised in the settlements or findings. They simply reflect the patterns I found. Most complaints start as problems about very specific technologies in specific circumstances. The final settlement or findings often reflect larger accessibility problems that were uncovered during the investigation.

The Accommodation Process

  • Ensure that students receiving alternate formats for documents are receiving them in a timely manner and that they are accurate.
  • Ensure that the Disability Services office is part of the accommodation process when discussing what will meet the needs of the student in a particular class.

Course Content and Course Interactions

  • Ensure that the Learning Management Systems are accessible. This includes enterprise LMSes used by the whole campus but also systems, often from publishers, that might be used as a supplement to a textbook or a set of online tools. Often times these publisher-based LMSes are used by specific classes rather than the campus as a whole.
  • Do not require the use of a technology that is inaccessible when another more accessible technology or method may have been sufficient. Sometimes this comes down to how a particular technology is used in a particular setting. This problem seems to be cited most from software which facilitates collaboration or from classroom response systems (e.g. clickers).
  • Ensure that electronic documents (e.g. PDFs, PowerPoints) are accessible.
  • Ensure that videos have captions and that the captions are accurate.

The University’s Approach to Accessibility

  • Provide information to people about accessibility services for your campus and how to get help or request services. This includes providing this information to users through Web sites and print communications.
  • Ensure your campus’ grievance process is published and followed.
  • Have a person and/or governing body in charge of coordinating accessibility efforts.

Procurement

  • Establish processes to ensure all electronic and information technology which is procured is accessible.

Training

  • Provide sufficient training to faculty and producers of Web content on accessibility practices.

Web Content

  • Regularly audit Web sites for accessibility.
  • Define the standard by which Web accessibility will be measured. (Usually WCAG 2.0 Level AA is referenced in the findings and settlements.)

Non-Course Related Accessibility

  • Ensure accessibility of student information systems and all of the ways students may interact with them. (e.g. course registration system, scholarship information, paying a bill)
  • Ensure public videos are captioned and that the captions are accurate.
  • Ensure information conveyed through digital signage is available to all users in accessible formats.

Again, this list is not exhaustive of all of the issues raised in recent legal actions and it does not cover all aspects of accessibility on your campus, but hopefully it can be a conversation starter for your campus as you either begin implementing an accessibility plan or you are trying to make improvements to your existing plan.

Links to Findings and Settlements

Winners of the 3rd Annual NC State Global Accessibility Awareness Day Challenge

(EDIT: Because of a technical problem, the Ocean Observing and Modeling Group site was not originally scanned accurately. The results have now been updated.)

Congratulations to the winners of the 3rd Annual NC State Global Accessibility Awareness Day Challenge! Together we corrected over 125,000 accessibility errors over the past month!

There were two aspects to the contest: which sites could correct the largest percentage of their accessibility errors and which sites could provide a link from their home page to the Accessibility @ NC State site.

Sites correcting the largest percentage of their accessibility errors

Sites linking to the Accessibility @ NC State site

  • BTEC
  • Center for Family and Community Engagement
  • Communication
  • DELTA
  • English
  • Foreign Languages and Literatures
  • Horticultural Science
  • Interdisciplinary Studies
  • IT Accessibility
  • Lebanese Studies
  • Ocean Observing and Modeling Group
  • Philanthropy Journal
  • Psychology
  • Recycling
  • Social Work
  • Sociology and Anthropology
  • Student Media
  • Technology Transfer
  • Textiles

2015 Global Accessibility Day Website Accessibility Challenge

NC State University will be hosting our Third Annual Global Accessibility Awareness Day Website Accessibility Challenge. The purpose of the challenge is to

  • promote accessibility throughout the campus
  • improve the accessibility of our websites
  • teach developers and content creators how to build accessibility into their Websites

The contest runs from April 15 through May 20, and the winners will be announced on Global Accessibility Awareness Day, May 21. There are two competitions.

  1. Sites which can correct the largest percentage of their accessibility errors
  2. Sites which can include a link to the Accessibility @ NC State page

Sites which can correct the largest percentage of their accessibility errors

One competition is to see which websites can have the greatest percentage of errors corrected during the contest. Winners will be selected from

  • Large sites (1000 or more pages)
  • Medium sites (100-999 pages)
  • Small sites (less than 100 pages)

Sites which can correct at least 50% or 75% of their errors will also be recognized.

Sites which can include a link to the Accessibility @ NC State page

It is important to allow users to be able to easily find accessibility information about our campus, whether they are looking for accessibility services or are having problems interacting with online content. We have a central place where all campus accessibility information can be found, including contact information – the Accessibility at NC State site.

For the contest, websites which include a link to this site from their home page will be recognized. Including this link is often done by placing it in the footer of your page.

<a href=”http://accessibility.ncsu.edu/”>Accessibility</a>

Learning more about Accessibility

Throughout the contest there are a number of opportunities to learn about accessibility and how to make your websites more accessible. Note: All training events are in the Avent Ferry Technology Center, where there is plenty of parking.

Website Accessibility Tune-Ups (Lunch & Learn series)

Bring your lunch and your website for a free website accessibility evaluation from Greg Kraus, the IT Accessibility Coordinator. You will see how he evaluates sites for accessibility and you will go away with actionable items that you can start implementing in your site to improve your accessibility. You can signup in ClassMate with the following links.

Web Accessibility Testing and Techniques

In this workshop you will learn about Web accessibility concepts, how to code for accessibility, and how to use common accessibility testing tools. You do not need to bring your own website for this workshop, but you can work on it if you want to.

Co-Working Day Drop-in Session

Every Friday several people from around campus gather in Avent Ferry Technology Center, Room 106 for a co-working event. A co-working event is just a place where people gather to work on their own stuff or collaborate with people who are in the room to help solve problems they are having. On May 1 and May 8 Greg Kraus will be at the Co-Working Day from 9 a.m. to 4 p.m. to answer any questions you may have about accessibility and work with you on the accessibility of your site. There is no sign up. Just drop on by.

The Incredible Accessible Modal Window, Version 3

I’ve made a few minor updates to the Incredible Accessible Modal Window.

  • removed the role=”document” from the contents of the window. This was originally inserted to deal with the way NVDA interacted with role=”dialog”, but that issue has since been resolved in NVDA.
  • made the close button an actual button instead of a link. I should have done this a long time ago and don’t know why I didn’t do it sooner.

View the Incredible Accessible Modal Window, version 3.

Previous versions of the Incredible Accessible Modal Window

Note: This is edited from the original post to reflect an error in the first bullet point where it originally said role=”dialog” instead of role=”document”.

 

Winners of the 2014 NC State Global Accessibility Awareness Day Website Challenge

Congratulations to all of the developers who participated in the 2014 NC State Global Accessibility Awareness Day Website Challenge. Together we corrected 905,082 accessibility errors!

For each of the size categories, the Web sites that corrected the largest percentage of their errors are

  • Large Sites (1000+ pages)
    • NCSU Libraries (84% of errors corrected)
  • Medium Sites (100-999 pages)
    • African American Cultural Center (66% of errors corrected)
  • Small Sites (1-99 pages)
    • Internal Audit (25% of errors corrected)

For the ARIA Landmark portion of the challenge we had 21 sites add the main landmark to at least 80% of their pages and 23 sites add the navigation landmark to at least 80% of their pages.

Just a  note, there are actually a lot more sites on campus using those two landmarks. Because of the way the scan was run, only those sites which requested a rescan during the contest were counted in these totals.

Skip Links Shouldn’t Be This Hard

I’ve been creating skip-to links for years, like “Skip to Main Content” or “Skip Navigation”, but I recently ran into a problem with them in HTML5 pages, notably in IE with JAWS. In this one particular case they simply were not working. I would click on the skip link and I wouldn’t go anywhere – I was still at the top of the page.

<a href=”#main”>Skip to Main Content</a>
<div>Navigation goes here</div>
<div id=”main”>
  <p>Main content goes here</p>
  <a href=”#”>a link in the main body</a>
</div>

It turns out Chrome has this problem too.

So I thought I discovered a significant bug with skip links, to then discover I didn’t really discover it at all. In fact, this issue appears to have been around since about 2000 in some form starting with Internet Explorer 5, and it affects all users in IE, not just screen reader users. Sometimes skip links would work and sometimes they wouldn’t. I had noticed this in testing for quite some time but assumed I had just messed up in testing. I mean, looking at the code it’s easy enough to verify that the coding is correct for a skip link and it’s pretty straight forward functionality, so what could go wrong?

The real catch here was the intermittent nature of the problem. IE didn’t consistently fail – it just failed sometimes. To make a real long story short, it turns out that IE handles targets of internal links differently depending on if certain elements have explicit layout properties set, like certain CSS properties. If those properties were not set on the target, when you tried to target the destination with an href, the link would fail. The address bar would update, but the focus in the page would not go to the target. If the properties were set, the link would work.

If you want to read more about the details here are some readings.

Chrome’s behavior is totaly unrelated to these reasons, but the solution proposed below solves the problem for both IE and Chrome.

The Solution: tabindex="-1"

If you read through the posts above there are various solutions offered from JavaScript patches to CSS hacks to additional HTML attributes. The one I have settled on is simply assigning tabindex=”-1” to the target.

<a href=”#main”>Skip to Main Content</a>
<div>Navigation goes here</div>
<div id=”main” tabindex=”-1”>
  <p>Main content goes here</p>
  <a href=”#”>a link in the main body</a>
</div>

Or if you use the newer HTML5 elements

<a href=”#main”>Skip to Main Content</a>
<nav>Navigation goes here</nav>
<main id=”main” tabindex=”-1”>
  <p>Main content goes here</p>
  <a href=”#”>a link in the main body</a>
</main>

Once you do this everything works beautifully in Firefox, Chrome, Internet Explorer and Safari.

But this won’t work

I did some additional testing to see if the target of the skip link was already a focusable item, like a link with an ID, would the link would work correctly.

<a href=”#main”>Skip to Main Content</a>
<div>Navigation goes here</div>
<div>
  <a href=”#” id=”main”>a link in the main body</a>
  <p>Main content goes here</p>
</main>

In this case, Chrome will work, but neither IE nor Firefox will work.

The Pain of Accessible PDFs from MS Word on Mac – Test Results

I get asked this question every so often, so I did some tests to see what the current landscape is in terms of creating accessible PDFs from MS Word on Mac. I was primarily looking at the workflow for adding headings and alternative text into Word and having those features show up in a PDF generated from Word. There are other accessibility issues to contend with as well, but for this evaluation I was looking at these two very important aspects of PDF accessibility which have a high occurrence.

Anyone who has worked in this space already knows that PDF accessibility support from MS Word on Mac is non-existent, however, can we improve things by introducing LibreOffice or OpenOffice into the workflow? First, I’m going to assume that most Mac users who are already using MS Word are not going to abandon it and start using LibreOffice or OpenOffice as their principal authoring tool. However, we might be able to convince these users to at least generate the PDF from one of these two products, at least for accessibility considerations.

So what did I test?

  • Authoring a document in MS Word 2011 on Mac, using headings and providing text in both the title and description fields
  • Converting it to a PDF using LibreOffice 4.2.3.3 for Mac
  • Converting it to a PDF using OpenOffice 4.0.1 for Mac

Here is what I found.

LibreOffice

LibreOffice recognized all of the headings and image titles and descriptions entered into Word. When exporting it as a tagged PDF, the headings are preserved, but only the image titles are passed through as the alternate text for the images

OpenOffice

OpenOffice recognized the headings but did not import the image titles or descriptions. Therefore, when you create a PDF from OpenOffice, none of the images have alternative text. If you manually enter image titles and descriptions directly in OpenOffice, then the titles are passed through to the PDF alternative text.

The Word for Windows Conundrum

If that was the end of the story then we could tell users to simply use LibreOffice to convert their MS Word files to accessible PDFs on Mac. The problem is if you take that same Word document to Word 2013 for Windows and create an accessible PDF straight from Word 2013, it’s the image descriptions that get passed through to the PDF as the alternative text. This might not be a problem if you aren’t sharing documents between Mac and Windows users who both might be creating PDFs from it. However, I would really like to be able to give one piece of advice to all of my MS Word users.

Recommendations

Here is the best advice I can give MS Word for Mac users. If you are the only person who will be generating PDFs from a Word file and you know the PDF will always be generated from a Mac…

  1. enter the alternative text as the image title
  2. open your Word document in LibreOffice
  3. export a tagged PDF from LibreOffice (tagged export should be selected by default)

If this file will be shared between Windows and Mac users, I would decide on a standard way of denoting your alternative text – either as a title or a description, and then based on that, decide which platform you will use to generate the PDF.

  • alternative text in the description = Windows
  • alternative text in the title = Mac, using LibreOffice

I hesitate to recommend putting the alternative text in both fields because that just seems like bad form and seems like it might cause problems in the future. It would also be cumbersome for someone with a screen reader actually editing or reading the document in MS Word itself.

Again, this analysis only looked at heading and alternative text preservation in the Word to PDF workflow. You might have to consider other accessibility issues too like tables, document reading order for floating text boxes, and document language. Ensuring heading and alternative text are preserved just saves a lot of work in any additional accessibility retrofitting that might have to occur in Adobe Acrobat.

(EDIT) Testing Files