skip to main content

NCDAE= The National Center on Disability and Access to Education

Enhancing the lives of people with disabilities
by promoting web accessibility in education

Should TEACH Act language appear in the Higher Education Act? NCDAE and WebAIM weigh in

NCDAE and WebAIM joined together on this position statement

Since their inception, both WebAIM and the National Center on Disability and Access to Education have worked together with higher education on the issue of web accessibility.  We believe that while accessibility is not easy to do it must be accomplished if individuals with disabilities are to participate fully in civil society.

Recently, important conversations of digital accessibility have emerged in U.S. higher education.  They were prompted by the inclusion of language from the bipartisian Technology, Education, and Accessibility in College and Higher Education (TEACH) Act into the proposed reauthorization of the Higher Education Act; known as the Higher Education Affordability Act (HEAA), see Section 931. As a result, position statements made by the American Council on Education and EDUCAUSE, along with a legal analysis provided for 6 education associations against the inclusion of TEACH language into HEAA, ignited a firestorm. This debate has been seen in news articles, commentary, blogs from groups, blogs from individuals, podcasts, and alternative position statements.

Both the National Center on Disability and Access to Education (NCDAE) and WebAIM would like to share our thoughts on this complex subject. Nobody at NCDAE or WebAIM is offering a legal opinion; rather, our thoughts come from working with institutions of higher education on matters of accessibility for 15 years.

TEACH Act, a primer (Or skip to What’s the controversy?)

Note: This TEACH Act should not be confused with a previous piece of legislation using the same acronym that deals with the use of copyrighted materials in distance education.

The current Technology, Education, and Accessibility in College and Higher Education (TEACH) Act had it’s origins in the previous Higher Education Opportunity Act of 2008, which established the Accessible Instructional Materials (AIM) Commission. The AIM Commission detailed recommendations to Congress and to the Secretary of Education in December of 2011.  One such recommendation influenced the creation of the TEACH Act. This proposal was introduced to the House by Representative Tom Petri (R-Wisconsin) in November of 2013 and introduced to the Senate by Senators Elizabeth Warren (D-Mass) and Orrin Hatch (R-Utah).  The bill had extraordinary bipartisan support, including 52 cosponsors of the bill across party lines. It was referred to committee February of 2014 and has yet to move out for a vote.

Because of the AIM Commission Recommendations, authors of the TEACH Act were able to respond to some issues plaguing accessibility in higher education. One issue is the fact that accessibility guidelines are not unified as campuses try to make content accessible (i.e., some conforming to Section 508, others to State guidelines or standards, others to differing versions of WCAG, and others who blend accessibility guidelines uniquely for their campus). This creates enormous headaches for vendors and for campuses seeking conformance to their own guidelines in a purchasing context; if you cannot purchase digital materials that follow your own technical standard it will be nearly impossible to reach your accessibility goals. Another issue is the enormous liability perceived by many in higher education for anyone who acknowledges that they need to work on digital accessibility.

The TEACH Act proposal provides a mechanism for unified accessibility guidelines to be created in harmony with national and international standards.  It authorizes the Access Board to be responsible for the work to establish and keep guidelines current (i.e., initial guidelines to be completed in 18 months, as well as reviews to be completed every 3 years). Those institutions that wish to embrace TEACH guidelines can do so, yet there is nothing in the Act that would compel them to do so. Since institutions are not required to conform to TEACH, they can continue to use their own set of guidelines if they wish. However, for those that choose to become a TEACH Act institution, they must implement the guidelines into every aspect of the campus digital architecture.

The voluntary nature of embracing TEACH comes from this language:

“Nothing in this Act shall be construed to require an institution of higher education to use electronic instructional materials or related information technologies that conform to the accessibility guidelines described in section 2 if the institution of higher education provides such materials or technologies, or an accommodation or modification, that would allow covered blind individuals and covered individuals with a disability to receive the educational benefits of such materials or technologies–

(1) in an equally effective and equally integrated manner as non-disabled or non-blind students; and

(2) with substantially equivalent ease of use of such materials or technologies.

Thus, an institution has the choice to embrace TEACH Act guidelines or to continue to do that which they are doing now to assure conformance to Section 504 of the Rehabilitation Act and the Americans with Disabilities Act.  One incentive for an institution to embrace the TEACH Act is the Safe-Harbor provision of the Act.  It protects those institutions that embrace TEACH by considering that they in fact conform to the non-discrimination provisions of Section 504 of the Rehabilitation Act and also the Americans and Disabilities Act where digital access is concerned.

So, in summary, the TEACH Act proposes to establish clarity of guidelines, provide market-driven solutions to challenges in accessibility, provide legal protections for those institutions who embrace TEACH, all the while being entirely voluntary for the higher education community.

What’s the controversy?

Those opposed to TEACH in HEAA generally cite at least one of 5 issues:

  1. This program exerts increased federal regulation that will overburden higher education
  2. This program will result in the demise of technology innovation on our nation’s campuses
  3. There is not a reason for TEACH Act provisions since we have existing laws that are sufficient to address the issues
  4. The language of TEACH Act creates a different legal standard for institutions who choose to not embrace the guidelines
  5. The Access Board is ill equipped to do the work

Federal Regulation

First and foremost, many in higher education shiver at the thought that increasing issues of compliance are put into reauthorizations of the Higher Education Act. Opponents to adding accessibility regulation into the HEAA indicate it is becoming a junkyard of federal oversight, where items are simply tossed in because they can be. Proponents to regulation being included for digital access indicate that this is a proper use of Federal oversight. The thinking is that if those in higher education did not want to be regulated on this issue, they have had nearly 20 years to get in front of it in a way that regulation is not needed. This is especially important considering the topic; that failure to provide access to electronic materials violates protections against discrimination for persons with disabilities and is an issue of civil rights. Also, proponents of TEACH language appearing in the latest HEAA draft indicate that it would make sense that something that came from the previous reauthorization of the Higher Education Act (i.e., the work of the AIM Commission) would return to inform a subsequent reauthorization of the Act.

Demise of technology innovation

Opponents to the addition of TEACH language in the HEAA indicate that when an institution chooses to adopt TEACH guidelines, this will be the end of technology innovation in higher education; that is because institutional technologies would need to conform to the guidelines. One example that has been seen in posts is the use of 3-D technologies in biology textbooks. Opponents indicate that the campus would be unable to use this innovation. Proponents see it differently. While they concede that in the short term some technologies would not be used as developed, they believe innovation overall is enhanced as entrepreneurs, visionaries, and vendors solve problems. This could drive greater technology innovation than ever before. The market-driven approach to innovation could not be created whatsoever if there were not a large playing field (i.e., a large swath of higher education entities) as potential new customers for these innovations that address electronic access. Proponents cite the rich innovations that have already been developed by individuals or groups whose focus is to address accessibility.  They express confidence that technology innovation will continue to enrich higher education in ways we can’t yet know. It is important to note that the language of the proposal allows for accommodations or modification as long as they are “equally effective . . . equally integrated . . .[and have] substantially equivalent ease of use”.

Existing laws are sufficient

Opponents to this action indicate that we have existing laws that are sufficient for today’s needs (i.e., Sections 504 and ADA).  They do not see a reason to create additional burdens for any institution. In cases where discrimination may be present, opponents to adding TEACH language into HEAA indicate that we have processes in place to address it (i.e., through OCR complaints, and the courts). Proponents consider the failure of higher education to become accessible over time to be one reason this action is needed now.  They cite the uptick in litigation and the failure of judgments to broadly influence the higher education system as another reason something new is needed. It is true that many institutions wait until they receive requests, or worse, until there is a formal complaint lodged before action is taken.  This creates an untenable position for individuals with disabilities who are always put in a position to have to request or complain, and usually put in a position to wait for that which they need. This creates lags in their educational experiences that affect outcomes.

Creates a different legal standard

If an institution chooses not to embrace TEACH guidelines, they must then provide materials and technologies (or accommodations and modifications), in an “equally effective and equally integrated manner as non-disabled or non-blind students; and with substantially equivalent ease of use of such materials or technologies.”  The current legal standard of Sections 504 and the ADA reference the use of reasonable accommodations or auxiliary aides and services that result in “effective communication” provided in a “timely” manner.  Opponents to adding TEACH language into HEAA believe that this could fundamentally shift the legal standard. We could not find an opinion from proponents on this specific point so it is not known if they agree or not.  There is discussion, however, that important differences in the language used in TEACH are the result of the need for institutions to be proactive, rather than reactive in their approach to accessibility.

The Access Board is ill equipped

Those opposed to adding TEACH language into the reauthorized HEAA cite that they are uncomfortable that the Access Board was named as the responsible federal agency.  They do not have confidence that the Access Board could complete the work as envisioned in TEACH; to create initial standards within 18 months and engage in cycles of review each 3 years. There is a reason for this concern—A refresh of Section 508 standards began in 2006 and has not yet been completed. Proponents feel they are the best equipped to address harmonization of the guidelines, and feel that if the Access Board is given resources to perform a statutory duty on a specific schedule, that they could accomplish the task.

Our position

Let us begin by stating that those in higher education want the very best outcomes for all their students. This is why they have gone into the field.  While we have read some harsh criticisms of individuals in the postsecondary community, NCDAE AND WebAIM respect the challenging work that goes into enterprise-wide web accessibility, and we acknowledge that this is often times a bumpy journey.

With that said, we have also heard many reasons why institutions choose not to tackle accessibility in a proactive manner.  Sometimes it is due to competing institutional priorities and shrinking budgets.  Other times accessibility is put off because there is a lack of accessible products.  (Moreover we have heard vendors remark that accessibility is not part of their development cycle because it’s not a feature request from their customers.) We have also heard institutional administrators quietly craft a strategy of waiting until there is a complaint sufficient to take action on accessibility writ large.  Taken together, there is a broad segment of the higher education community who has decided, consciously or not, to leave the important work of accessibility as an after-the-fact accommodation of a student’s request.  The model of post-hoc accommodations in the digital world could never be the long-term solution, it creates a false sense of protection for institutions that are under increasing legal peril, and it continues to plague those with disabilities today.

It is our opinion that the HEAA is an appropriate vehicle to place a regulatory issue of this importance. It would elevate the urgency to make intentional decisions on accessibility for each institution.  And, let us not forget, it is voluntary.

Market driven approaches were a brilliant strategy that helped the federal government as it implemented it’s own procurement policies under Section 508. If the lack of accessible products at the time, or the fear that it would stifle all innovation had been the reason not to move forward, we would not be where we are now; we currently have many accessible products and the attention of federal vendors. Bringing together a single harmonized standard that vendors would use in higher education would likewise create important innovation and product delivery. All journeys begin with a single step. We believe that innovation will not suffer, rather it will be enhanced as new energies go into thoughts about access for all.

We cannot comment on whether or not the TEACH language provides a different legal standard. While the spirit of it does not seem to do so, legal eyes are the best to weigh in on the issue.

While placing this work into the hands of the Access Board worries some, it is our belief that given appropriate resources and statutory authority, they are the best fit for the work.  We do think that 18 months to promulgate the guidelines may be too aggressive. It is more likely that the committee they will appoint would complete draft guidelines in 18 months, and then the work to promulgate rule would take another 18-24 months (or more if the Section 508 work is a peek into a typical process).

Finally, we see a gaping hole in the language inserted into the HEAA. When the ADA was passed into law, massive changes reverberated throughout our society not unlike that which will happen in higher education if this goes into effect.  The establishment of transition planning was a brilliant idea that should be considered here.  At the time, if you were a business trying to conform to the ADA and you were sticking to reasonable timelines of your own posted transition plan, you were held harmless for that period.  Some institutions of higher education may need the option of creating a transition period as they adopt the TEACH guidelines.  Of course all other existing laws would be in force (i.e., Section 504 and ADA), but the slow and arduous work will have begun; the work to ensure that accessibility of digital materials is in place for all in higher education.

Need a little motivation to kick off the year?

As another school year begins, those of us in the accessibility arena face a new year filled with opportunities and challenges. Can we get support at administrative levels? Will this be the year to finally get policy documents on web accessibility passed by the Academic Senate? Are faculties going to take advantage of training opportunities designed for them? How can we integrate web accessibility supports into existing campus-wide technology supports? Is it possible to get a system in place to monitor all our efforts so we know if we are making a difference? How can we get campus-wide web accessibility efforts a budget?

Each of these is a heavy lift. Yet, one theme present across these challenges is the issue of motivation, for administrators, key staff, faculties, and students. I have long thought that our motivation “personality” lies somewhere between being a cheerleader and a taxman. We know we cannot do this work alone, and as such we need to be cognizant of how we contribute to the motivation of individuals across specific groups. If we are to be successful this year, no matter our specific effort, we need to consider the role of motivation.

I was fortunate to participate in the day-long Accessibility Sprint, a meeting of accessibility personnel in higher education just prior to the AHEAD conference this summer. Participants spent a large part of the day in smaller working groups. Since I had been spending a lot of time thinking about the challenges of motivating others, I joined that group. We had amazing discussions on this issue. Each member brought ideas and concerns straight from their experiences to the discussion. As one of our group’s action items, we decided that we would co-author a series of short resources on motivation in higher education, and that we would post them to the NCDAE site.

This month we present motivation ideas for faculty and staff. In October we will offer ideas for technologists and procurement specialists. Then in December, we will finish the series with resources that cover motivating students and those in administration. Each resource is the product of the collective thinking of the group, and as such we all share credit if we provided you with a good idea, and we all warrant your criticism if we failed to do so. Of course, I would hope that if you have ideas we have missed, that you would present them here, so that others can use your ideas, experiences, or your cautionary advice.

The alphabetical listing of members of the 2014 Summer Accessibility Sprint cluster on Motivating Others in Higher Education include:

  • Joshua Hori, Student Disability Center Analyst, University of California Davis
  • Marc Montaser, IT Consultant, Cal State University Fullerton
  • Cyndi Rowland, Director, WebAIM and the National Center on Disability and Access to Education
  • Janet Sedgley, Accessible Technology Services Manager, University of Montana
  • Thad Selmants, Assistive Technology Specialist, Sierra College
  • Laurie Vasquez, Assistive Technologies Specialist, Santa Barbara City College

Will this be the year?

The end of February the field heard that the Access Board submitted a proposed rule to update the Section 508 technical standard. Many of us in the field have been waiting for this and other actions on the accessibility front for some time.  As we head into the CSUN Technology and Disability Conference, it got me thinking; “will this be the year”? We know that the battle for digital equity will be won in part with an equal measure of awareness of the problem and regulation to support it.

Right now in the U.S., there are a number of regulations just on the horizon that could positively affect digital accessibility; the field has been waiting a very long time for these legislative gems. They would bring with them both opportunities for broad awareness, and include the rule of law. These include (1) a refresh to the Section 508 standards, (2) the clarification of ADA with respect to web accessibility, and (3) other pieces of legislation where accessibility language could have a large, positive, impact.  Each is briefly described below:

Section 508 refresh

How many of us would have imagined that the Section 508 refresh would have taken so long? The process began with the Telecommunications and Electronic and Information Technology Advisory Committee (TEITAC) established in 2006. I was thrilled when NCDAE was invited to be a member of TEITAC and represent education entities in this process. The recommendations from that group were given to the Access Board in April of 2008; yes, that would be nearly 6 years ago.

Just a few weeks ago (February 23rd), the Access Board submitted their report to the Office of Management and Budget (OMB), who has 90 days to clear it, or take issue with its contents. Once it clears the OMB hurdle, it will be posted for public comment and replies to comments under a Notice of Proposed Rulemaking (NPRM) process for another prescribed period of time; this is typically another 90 days.

That means that it is possible that the earliest we would see the refresh is in about six to 8 months; which would mean the new standards could be out IN 2014. Although it is more likely that it will take longer.  Sadly, it also means that the time from the beginning of the refresh to rule would be at least a decade – or more if not finalized this year.  It feels that over the past 5 or so years, we have been hearing rumors that the refreshed standards will be out for comment in (today’s date + 4 months).  Chasing the rainbow for that pot-‘O-gold has been a tiring process for many.

ADA clarification

Another highly anticipated action by the federal government is their intent to clarify the “Accessibility of Web Information and Services Provided by Entities Covered by the ADA”.  The Department of Justice began this process in 2010 through an Advanced Notice of Proposed Rulemaking (ANPRM).  They sought public comment on their desire to revise ADA regulation to “…establish specific requirements for State and local governments and public accommodations to make their websites accessible to individuals with disabilities”. This would both codify the expectation of accessibility for covered entities engaged in covered services, and also provide the standard by which this could be accomplished (hmmmm, might it be the Section 508 standards?). The hope is that the ADA clarification would end confusion, and reduce litigation on the issue of web accessibility.

The ANPRM comment period was closed in January of 2011. After quite a long silence, and an extended period of speculation by many of us –yes, WebAIM/NCDAE included–, the field was energized by hearing that the Notice of Proposed Rulemaking (NPRM) would be published in July of 2013.  July came and went, as did the newly published dates of November 2013, and December 2013. After this time, the DOJ went silent on when we might see the NPRM.  Of course once it is published there will be a period of public comment, typically 60 days, and another period, typically 30 days, for reply comments. Then the Department will be in a position to deliver the report and order, which effectively promulgates the new rule. So could this also happen in 2014?  The math is certainly aligned, but the reality is anyone’s guess.

Other legislation

There are other pieces of legislation that are new or in the midst of a reauthorization. One example is the newly proposed Technology, Equality, and Accessibility in College and Higher Education (TEACH) Act. The field owes Wisconsin representative Tom Petri a great debt for introducing the bill (H.R. 3505). It would strengthen and clarify requirements for digital materials to be accessible to students with disabilities. Sadly, only about 11% of bills ever leave the committee to which it was assigned (House Education & the Workforce Committee), so it may never make it to a vote of Congress.  No matter the result of this Act, it may show the beginning of legislative attempts to solve a major problem in higher education today.

Another is the reauthorization of the Higher Education Act (HEA) itself.  Congress has begun this work, and there is speculation that accessibility may be included. This is because feedback is going into both the House and Senate Committees (e.g., some provided by NCDAE).  Both the House “Education & the Workforce Committee” and Senate “Health, Education, Labor and Pensions (HELP) Committee” have scheduled hearings on reauthorizing HEA and have already included hearings around some disability issues. Many disability communities are holding discussions on what should be included, and deciding the best ways to advocate during the process.  The HEA also includes regulation surrounding the accreditation communities; could this be the time the accreditors get involved in a substantive way?

If you would like to add your opinions to either the Teach Act or the HEA reauthorization, please contact members of those Congressional Committees. Of course it is more powerful if you live in the district of the committee member (i.e., either from the House or Senate).  Could this be the year that legislative language is put in place to help postsecondary accessibility efforts?  Might it forever clarify that after-the-fact accommodations should not be the frontline approach in providing access to all students?   We will wait and see.

No matter the exact timeline, those in the field are on pins and needles.  A cluster of potent high-profile federal regulation could just be the ticket. Will this be the year?  We will all stay tuned, crossing fingers and toes.

Institutional Guidelines on Captioning

Many would argue that the single most difficult issue of institutional web accessibility is captioning.  The issue presents a challenge, in part because there are so many people linking audio and video materials without regard to the need to have captions present. The ways in which institutions engage their faculties and staffs on this tough issue shows the maturity of the institution’s journey toward full web accessibility.

This past month, members of the Educause ITACCESS list had an interesting discussion on a topic I had not seen addressed before.  The thread began with a simple question, asking if anyone had captioning guidelines they would be willing to share. They were not talking about policy documents indicating THAT captioning needs to happen, nor were they talking about guidelines surrounding HOW to caption, but rather how others communicate to faculty and staff the expectations of WHAT to caption on their campuses. Implicit in the discussion was the notion that institutions need to have guidance they share with faculty and staff to help them understand their role.  In a way this guidance communicates the line in the sand for the institution on the captioning of digital materials.

As I read through this discussion and saw the rich resources being shared with one another, I was once again struck by the fabulous work that is happening across the country.  We all benefit from seeing how others proceed with tricky topics. As I digested the comments contained in this thread, I thought it might be a good idea to provide a summary of thoughts and a couple of resources to the work that others have done. If your campus does not have a guidance document for faculty and staff on the specific topic of captioning, now might be a great time to start drafting one for stakeholder feedback. This post represents content both extracted from the Educause ITACCESS thread and other material I uncovered as I looked around for myself.

The issue

Without specific guidance, faculty and staff will probably not understand their role and responsibility to caption. It is not enough to simply have a statement in policy that “all materials with audio content will be captioned”.  This does little to help them understand exactly what they are to do, and in what conditions they are expected to do it. Moreover, some interpret that “all materials” is actually limited to “all materials” they produce, and are not inclusive of those items secured through others (e.g., linking to others’ audio or video materials). Many institutions are producing guidance documents that walk faculty and staff through the issue of captioning, as well as their role in the process.

Remind me, why are we doing this?

You may benefit from reminding others of the important civil rights that are at play for students and community members who have disabilities.  Of course after-the-fact accommodations are no longer passing the giggle test and many are feeling the sting of legal challenges when digital materials are not available to their students and staff.

If your institution has tied accessibility to the Section 508 or WCAG 2.0 guidelines, you may also want to include this in the guidance document. Currently, the Section 508 standard states; “All training and information video and multimedia productions which support the agency’s mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captions”. The WCAG 2.0 Principal that all content must be “Perceivable” would come into play, as the audio component would be lost to anyone who lacks the ability to hear, or hear well (More specific information on WCAG 2.0 and captioning can be found by going to Guideline 1.2, or by viewing a WebAIM resource on this Guideline in WCAG 2.0)

When do you have to do it?

There are 3 categories of audio or video recommendations that I found. Each had slightly different requirements for faculties or staffs:

  1. Real time meetings or online courses in real time. Here the recommendations are mainly to contact the Disability Resource Office well ahead of the need to set up a real time captioning service if there is an individual who needs it, or if it will be archived online for more than one term.  There is also the important guidance to set it up and test it in the same environment before it will be used.
  2. Audio or video materials that faculty or staff produce and upload onto the institutional web (this includes courses). The prevailing wisdom is that if the faculty produce it themselves, they should also take responsibility for captioning; whether they do it themselves or not. Considering how easily this can be done in YouTube with a transcript and the synch captions feature, it is probably not too high a bar for someone who has the sophistication of producing the video in the first place.  Of course it requires that a transcript is available or produced.
  3. Audio or video materials that faculty or staff find for use (e.g., link or upload materials from other sources). On this point there seem to be differences across institutions around what faculty and staff members should do.  The section below details these differences.

Differences of context

The ways to deal with the captioning of outside content depends a great deal on context.  The following are some bits of guidance I collected across resources.  There were some definite trends.  Here is what I saw being shared with faculties and staffs:

  1. They have a responsibility to search for an already captioned version of the media item they would like to use (See resources provided for searching for captions).
  2. They must consider if they have any current user who requires captions.
    1. If yes, the media element must be captioned before it is placed onto the web without question.   They are instructed to see the Disability Resource Center immediately.
    2. If they are teaching a course and do not have any registered student who needs captioned material, they have 2 options here:
      1. If they will use the material for only the current term, they can use it.  (I did not see anywhere that faculties are required to fill out and submit a form stating exactly this?  It would certainly help communicate a good faith effort on the part of the institution if challenged at a later date.)
      2. If they plan to use this media element for more than one term, the resource must eventually be captioned. However, they are allowed to post the item now as long as they also submit the materials for captioning. I assume that this work is then put into a queue and produced over the term so that the next time it is needed, it is captioned.
  3. If faculty or staff are putting content up on the public side of the institution’s web (i.e., not behind the login of a course for which a student will be a registered user), it must be captioned, as it is a reasonable expectation to assume that some future user would need captioning.

Captioning methods

There were differences across institutional expectation of faculty who are working to get material captioned, if that source material is not theirs. Here are the three top trends:

  1. The institution outsources the entire captioning work. Faculties and staffs need only provide the desired link or media and it will be returned in a captioned form. It is unclear to me if this goes through a central institutional process or if the faculty or staff member contacts the approved vendor themself.
  2. The institution completes all captions internally. As above, a faculty or staff member’s responsibility is to provide the campus entity with the link or the uncaptioned media that would be uploaded. Once complete, captioned work is returned.
  3. The faculty or staff members are required to submit both a transcript and the media for synching. So this would mean that the individual submitting it for synching, is the one to create or secure the transcript.

Resources to share

Below are two resources offered by the Educause ITACCESS members during this thread. If readers of this resource blog have others to share, please do so.  It will help others who are working on this tough issue.

Beloit College
Using Video in Your Course

To ensure equivalent access for students with hearing impairments, all videos must be captioned. Many  already come captioned, but it must be “turned on” when you show it to the class. If captioning does not exist,  contact the IT office well in advance in order to get it captioned before you use it. IT contracts an outside  company for this service and will need 3 weeks between the request of the item to be transcribed and when it is needed. Please contact IT Support if you would like to request this service.

Portland Community College

Resource: Audio and Video Accessibility

Voices from the Field: How Local IT Support Can Help Faculty

Last month we profiled the experience of a faculty member in the midst of changing her professional practices to include accessibility. This month, we are sharing the experiences of the IT support staff for the same department. Below he shares thoughts about working across a dozen faculty members to help them learn to create accessible materials for their online courses and the online elements for their campus-based courses.


 

By Karl Smith

The Department of Special Education and Rehabilitation at Utah State University recently began the process of making all of its course materials accessible.  I was happy to learn of this initiative as I believe not only should my department be compliant with accessibility standards, but that it has a responsibility to set an example in this regard.

While we do have some specific needs for current students which must be met, we also wanted to educate our entire faculty on best practices, and raise the quality of their teaching in general. As the department Technology Specialist, I have tried to offer my knowledge and assistance wherever I can.

As the IT support person, I get called whenever someone tries to do something unfamiliar with technology.  And while there are plenty of direct answers to questions regarding accessibility tweaks (most covered by materials developed by GOALS) I’ve also found myself giving the following answers with relative frequency.

“All students should have substantively the same experience”

It’s amazing how quickly people can lose sight of the big picture, and probably not too surprising that they lose track of this one.  When you’re teaching someone to make a Word document or PowerPoint presentation accessible the big picture isn’t really relevant; you’re teaching them features of Word or PowerPoint.  But once that faculty member takes those lessons back to their office and starts tweaking their own course materials, they seem to lose track of “Why?”,  and an hour or two later I inevitably get a call.  After they try to explain how they’re jumping backward through hoops mangling their document, “Why?” is ultimately the question I have to ask them.  And generally, it’s because they’ve lost sight of this one simple principle.

Designing accessible materials does not mean you can’t teach your class the same way you always have.  You can still communicate with students in the same ways.  You can still teach as you always have.  But a bit of design breadth when creating course materials makes those materials usable by students in multiple ways.  A Word document with proper heading structure looks the same when printed, but is also navigable by screen readers, or even parse-able by document restructuring tools (like something that may make a website out of it).  The goal is not to change the look of your documents, nor do you need to make multiple versions of your materials for students with various disabilities.  The goal is to make your normal documents and methods more broadly accessible, so all students have as similar an experience as possible.

“We’re doing this over 3 years”

Cyndi Rowland has consulted with us several times during this process, and one of her early pieces of advice was not to rework everything at the same time.  It’s painful, it’s frustrating, and people don’t have the time to DO it.  Rather, make the commitment that everything developed from this moment forward will be developed accessibly.  This way, no one has that annoyance of reworking something, and in a few years the vast majority of your materials will have converted naturally.  You should probably also pick a completion date, and as that date approaches you may have to deliberately rework documents that won’t be replaced naturally.  But that will be a LOT less frustrating.

We really liked Cyndi’s advice, and the department has committed to a 3-year turnover schedule.  Of course, there are some materials that need to be reworked more aggressively for students currently in our programs who have disabilities.  But in general, this is our plan.  Unfortunately, it’s difficult to learn these techniques and processes without a document to practice on.  So the first document any faculty member works on will generally be a rework of materials they already developed.  And this seems to set up an internal “I need to rework all my existing materials” expectation which was not intended.

“The Disability Resource Center is not always the answer.  But it’s a good resource!”

Okay, this might take a bit of history.  As recognition of the needs of people with disabilities has evolved through the past several decades, many institutions developed some form of central disability services office.  Frequently on campuses, this is called a Disability Resource Center (DRC).  As these were primarily developed in an age where wheelchair ramps or other physical accessibility issues were the most recognized problems; these services focused on accommodating the needs of a person with a disability in the moment.

More recently, especially with developing focus on e-learning, this accommodation model is proving insufficient to the needs of students.  When an entire campus tries to meet their accessible course material needs through the DRC, the DRC tends to have insufficient resources.  As this problem grows, the principle of “similar experience” become difficult to maintain, and sometimes impossible.  When this breaks completely, students have begun bringing lawsuits against institutions, which they are increasingly winning.  Laws are changing to help define the needs of persons with disabilities; but this is an evolving area.

What I have found is faculty often expect the past accommodation model to be sufficient.  I explain the problems with the current model, and how faculty can better meet the needs of their students.  But this is not to disparage the local DRC!  Disability Resource Centers also recognize these problems, and are working to develop solutions.   This may be anything from centralizing efforts to make PDFs accessible to captioning services for videos to converting your handouts into braille.

The particular things I’ve needed to point out to faculty are:

  •  “If you ask the DRC to rework a document as you are developing your course materials, it only has to be done once.  If materials are reworked for each student as you teach the course, the work will be repeated every time you have a student with a disability.  Simple conservation of labor makes submitting the document up front a better solution.”
  • “Having the DRC rework a document takes time.  If documents are submitted as needed by a student, this prevents that student from having materials in a timely manner, preventing them from taking part in class discussions and possibly holding up exams.  Not only does this violate the principle of similar experiences, it makes more work for you.”

Contact your DRC, and find out what resources they have.  As an educator, you can take advantage of their capabilities as you develop course materials.  They’ll appreciate that you are being proactive, and saving them both repetitive work, and being pressured by students who need documents immediately.

“Yes, you can still do ______”

After the first workshop with faculty, and thus after we had explained the difficulties with poor visual contrast, I saw a sudden push among some faculty to make all their PowerPoint’s black on white.  Some were going for pure Arial.  While it was good to see the awareness and concern, it was also saddening that our faculty felt their creativity needed to be stifled.  Some quite colorful slides were “cleansed” –   backgrounds were stripped and aesthetics ransacked.  This is not necessary.  Try to watch for faculty who are gutting their course materials.  Make sure they understand, they CAN do that neat thing they want.  They CAN be creative.  They just need to be conscious of a few things when doing so.  Honestly, some of these “how can I do this” conversations have been challenging, fun, and strangely enlightening.  Sometimes I’ve had to reach for outside ideas and assistance.  But I’ve yet to find something that cannot be done.

“Alt text is very, VERY subjective.  What did you intend to convey with this graphic/chart?”

This usually comes up during workshops, as every document that can include charts or images now has a tool to add ALT text to said chart or image.  Unfortunately, there is not always one right answer for what should go in that field, or even if anything should.  And now that programs like PowerPoint or Acrobat include an “Accessibility Checker,” I always try to stress it can only check for the presence of ALT text, and cannot evaluate its quality or need.

There are various rules for how ALT text is structured (no “picture of” for example).  But when explaining how to decide what content to put in the field, I usually ask why the image or chart is there to begin with.  A chart may only be included so the viewer can tell that a trend line increases over time, so “Chart showing increase in X over Y time” may be appropriate.  Or you may intend the viewer to get a few specific details, so you need to specify those details.  If you wanted really complex data analysis, it’s likely better to incorporate a navigable table in some way.  But in some contexts, even a complex chart may be decorative.

We had one discussion during a workshop about a graphic which the faculty member had included simply to amuse their students.  It was only tenuously related to the topic, and was just included to lighten the mood.  Different faculty thought it should be removed, left but not tagged, or tagged in detail with an attempt to describe the joke.  Any of these options could have been right; and I think the discussion helped them see how difficult it is to create rules regarding ALT text.

Ultimately, you need to help your faculty see this process as beneficial.  Not only will their efforts help their students with disabilities engage equitably in their classes, it may also help them to reflect on the purpose and message of their materials, improving the quality of learning for everyone.  If your faculty can embrace rather than resent accessibility initiatives, they can do some amazing things which will reach more students than ever before.

Views of a Faculty Member: Accessibility from where I stand

We invited Kimberly Snow from The Department of Special Education and Rehabilitation at Utah State University to write a guest blog post. She wrote on her her experiences with accessibility as a faculty member.


 

During my summer break I was asked to spearhead a project for our department. I was given the charge to figure out how to make the courses taught by our faculty accessible to all students. The idea was that, over the summer, I would make my own courses accessible first, then help other faculty members do the same to their courses when the Fall term began. Our department not only recognizes the fact that we are “encouraged” to prohibit discrimination by the Rehabilitation Act of 1973 and the Department of Justice by making our courses accessible to all students, but more importantly it acknowledged this is the RIGHT thing to do.

I was initially excited because I am fortunate enough to work in a department with caring faculty members who are advocates for all individuals with disabilities. I thought this would be a great project for me to tackle, and shouldn’t be that difficult. As it turns out I was partly correct in this assumption. Here is my four step process:

Step One: Get informed

I feverishly began my research on exactly what it means to make course materials accessible and how to go about it. I was directed to two different websites that soon became my go-to sites for information and answers. One site I visit often is WebAIM (Web Accessibility in Mind). Even though this website is directed more technically towards making websites accessible, I found it helpful in giving me important background.

Here is some content I found helpful:

  • what is accessibility
  • who benefits from making websites (and materials) accessible
  • what individuals, who require accessible sites, are saying about their own experience(s) with accessibility
  • tips to implement when making websites accessible
  • what the law says about accessibility
  • what we need to do to comply with the law

After reading much of the information on this website, I began thinking this was going to be a little more daunting than I had thought originally. For me, it was information overload. I needed to be reigned in at this point. The second website I visited did exactly that. The National Center on Disability and Access to Education (NCDAE.org) currently has a project, Gaining Online Accessible Learning through Self-Study (GOALS). This website provided me with valuable information from articles and access to “cheat sheets” that assisted me in honing in my thoughts and addressing the important components in making a course accessible. These cheat sheets were developed specifically for “less-technical” individuals such as myself. I found my direction outline using the cheat sheets and was now ready to implement.

The cheat sheets cover the following accessibility topics:

  • Microsoft Word 2011 (Mac)
  • Microsoft PowerPoint 2011 (Mac)
  • Microsoft Word 2007/2010 (Windows)
  • Microsoft PowerPoint 2007/2010 (Windows)
  • PDF Conversion in Microsoft Word/PowerPoint 2007/2010 (Windows)
  • Adobe Acrobat XI
  • Adobe Acrobat X
  • Adobe InDesign CS5.5
  • Creating Accessible Electronic Content
  • Identifying Web Accessibility Issues
  • Captioning YouTube Videos

Step two: Make my own content accessible

Now I was ready to make my own courses accessible. To begin, I tried to apply all I had learned into making one of my courses accessible all at the same time (i.e., whatever was in week one, I tried to make accessible). It proved to be too much at once! Since my goal was to have one course that could be used as a model course for the faculty by the end of my summer, I realized I could take a different path. I knew I wanted to experience all the accessibility topics before I actually presented them to the faculty, but I decided to tackle only one type of accessibility fix across my course at a time. This means I made all of my PowerPoint presentations for the entire course accessible at the same time, then all Word documents, then all my pages on our course management system, then converted all of the PDF readings (52) to ensure they were accessible, as well as added transcripts to all of my videos and YouTube videos (16+) and added closed captioning.

With this experience of retrofitting for accessibility, I came up with a better plan for my faculty and how they should go about their own course accessibility. Instead of retrofitting one entire course to be accessible at a time, I suggested they just begin where they were. As they create/revise a PowerPoint, make it accessible; when they post a reading for students they make it accessible too; as they add a video to their assignments, be sure it is accessible. This is a much easier plan and not as overwhelming for faculty as the notion of retrofitting everything.

Step three: Decide on a sequence for faculty

At this point I felt I had enough background information and preparation to begin training our faculty on how they can go about making their courses accessible. Using my own experience I decided on the order of topics to be addressed.

  1. PowerPoint
    I began with PowerPoint because my experience with it was less daunting and it was a more easily understood topic. I wanted to ease them into this process without scaring them away. Also, at the beginning of the semester faculty members are preparing their lectures and could use this information in their preparations.
  2. Word Documents
    I had the most fun with Word documents, so I thought this would be a good second choice. My initial learning for accessibility took quite a bit of time, but once I had it figured out I had fun with it and used styles with everything I created. This helped me with both accessibility and non-accessibility features (e.g., auto generated table of contents are great).
  3. PDF
    PDFs would be the third topic, yet they were a little more difficult for me to embrace, let alone train other faculty members to make accessible. I increased my understanding of how they look to a screen reader and the process it takes to make them accessible. I needed, and will continue to need, additional support to make this happen. Thankfully, I have technical support in my department that can help me when needed. However, I am more aware of what I need to look when selecting articles, readings, and other items that are only available online as a PDF.
  4. External Websites
    Next, I presented a way for faculty to evaluate the accessibility of the external websites they might select for students to use in their classes. I showed them how to use the WAVE tool to detect problems and be a sort of weather vane for accessibility . This process was interesting and fairly simple. It took very little time to learn. Yet because you have no control of an external website you do not have to worry about adding time to make corrections; unless you notify the creators of the website that their site is inaccessible or could be more accessible. However, if found to be inaccessible, it might take more time to find a suitable alternative.
  5. Videos
    The video topic was put last on the list because other university staff and I were still trying to figure out this issue. Many of the videos I personally select for my courses are not ones I produce or upload. If I owned them and put them onto YouTube for example, getting them captioned is a pretty straightforward process. Getting a procedure to add closed captioning to the videos of other people was very tricky, not as simple as originally thought. So good luck if what you want to use is on YouTube and you are not the owner of the media file. Copyright issues come into play, deciding on the most efficient procedure to accomplish this, as well as other unforeseen issues were all considered. I will still need additional assistance to make some of my videos accessible. Sad to say, I don’t have a lot of positive information I can share with faculty.

Step four: Let the process begin!

Once I determined the topics and the order of presentation I was ready for the process to begin. Following is the schedule of training:

  • Faculty Retreat– During a faculty retreat, held before the start of the school year, I took 20 minutes to present to the faculty the agenda for the school year in regards to making their courses accessible. During this presentation I spent time getting understanding and buy-in from faculty; although our Department Head was mandating it regardless. I gave examples of accessibility and what students with disabilities encountered in regards to materials and resources in courses taught. Then I presented the plan for our Department and an agenda for the year on how we could address these issues and make our courses accessible over time.
  • Faculty Meeting– During each faculty meeting, held monthly, I presented one topic (listed above). During these meetings I took approximately 15 minutes to introduce the accessibility topic and gave examples of how we go about addressing the accessibility issues involved with the topic. I gave them the corresponding “cheat sheet” and encouraged them to “play around” with what they had learned before our next meeting.
  • Workshops– Two weeks following the faculty meeting I held a workshop for faculty on the topic discussed in the faculty meeting. The workshop lasted one to two hours depending on questions and involvement. Faculty was encouraged to bring their own computer, “cheat sheet”, and be ready to create or edit a project/materials/resources they have or use. During the workshop, I reviewed the topic introduced in faculty meeting, worked through an example using the information presented on the “cheat sheet”, then allowed faculty time to practice what they learned using their own materials/resources.

Through this entire process I had the assistance from our Systems Administrator to answer additional questions and to provide technical assistance when needed. His service was invaluable and this would not have happened without his assistance.

We are still working through this process and our Department Head has not yet determined how he will evaluate conformance to his decision, or evaluate the training and technical assistance that I am providing. My guess is at some magic moment, he’ll ask everyone to submit sample accessible materials from across their courses. We’ll see.

Reflections

Our faculty has been very receptive to making the courses they teach accessible to all students. We understand the need and the responsibility to deliver materials and resources in an accessible format. Initially, it was imperative that the tasks be broken down into small steps and that we had the right technical support in place. Without these, any faculty may be overwhelmed and afraid to tackle accessibility. However with support and understanding, this necessary project can bring some new professional skills. I was personally excited that it was not as daunting as I initially thought. Time will tell, but I think our outcomes will be positive and helpful in creating more accessible web content.

Reflections on accessibility expectations: Faculty are expected to do what?

At NCDAE, we have long been a proponent of putting the responsibility for accessibility in the hands of those who are closest to creation of web content and products. In higher education this would mean technical individuals must produce markup that conforms to the chosen accessibility standard; vendors must deliver an LMS that conforms to the standard; faculty must create accessible content before it is loaded into the LMS (e.g., PowerPoint); and staff must create accessible documents that might end up on a website (e.g., PDF or Word docs).

While it is intuitive that the locus of control and performance expectation should reside closest to the source, it is critical that all accessibility committees and managers examine their expectations, to see if they are reasonable. If deemed reasonable, training and support structures must be present to make these expectations a reality. If they are deemed to be unreasonable, a plan must be put in place to accomplish the same task, perhaps with different individuals taking on different roles, or an overall different plan of attack. For example, an individual skilled at tagging PDF’s may be responsible for retrofitting complex PDF’s for faculty in a specific college or department. At the end of the day, the institution must deliver content that meets their accessibility standard. How this is accomplished, and who accomplishes it is the tricky part. It is a challenge to determine how best to share the responsibility for accessibility while also recognizing that limitations do exist, and then plan for it.

I am reminded of an old saying, “Don’t blame people for disappointing you, blame yourself for expecting too much” (unknown). In this past year, our GOALS experiences have caused us to reflect on just where the line in the sand should be in our expectations for non-technical individuals.

Here are a few examples of what we mean:

  1. Most agree that faculty & staff should use styles native in Word to help create semantic structure when they create a document. This includes items such as heading levels and lists.
    • Do you think they should be responsible to create an accessible document if complex tables were involved in a Word document? Frankly, given the limitations of Word (e.g., inability to tag column and row headers in a table), the next best solution is to either convert to HTML or save as PDF and then tag the tables. If you believe they should produce this content accessibly, they must understand what to do, or to whom they should turn to for help.
  2. Most agree that faculty & staff should provide alternative text for non-text images in PowerPoint.
    • Do you think they should also provide alternatives for complex charts, graphs, maps and other images that typically convey complex content? We agree that the content creator is the best to convey what should be conveyed, but the question is how should they convey it? If you have provided them with guidance that alternative text should be succinct, how (and where) do they provide these longer descriptions?
  3. Most agree that faculty & staff should be able to search for captioned media to embed into their course and even use the YouTube feature to upload a transcript and caption media they own.
    • Do you think they should be responsible for captioning all YouTube media they want to use in their course, even when they are not the owner of the video file? What about other media they find on the web?
  4. Most agree that faculty and staff should be able to export to PDF in accessible ways, tagging clear heading structure and reading order.
    • Do you think they should also be responsible for tagging PDF files with complex tables, a complex layout, or multiple form fields? Is there a difference in asking faculty and staff to create an accessible PDF from the ground up versus retrofitting a PDF? Are there lines where the PDF being retrofitted is so complex you would not expect them to have the skills to do so? These are important parameters to understand.
  5. Most agree that faculty and staff should only link to accessible web content if they require that the user go to other web pages (e.g., students must go to outside links to complete an assignment).
    • Do you think they should have the skills to evaluate the technical accessibility of that web content? If not, they would be unable to identify what conforms to the institution’s accessibility standard and what does not. If you think they should, how is this task possible when evaluations are technical in nature and many require manual checks (e.g., accessibility of JavaScript elements). Remember these are by-in-large staff that are not technical.

Notice these examples all center on non-technical individuals. Readers of our blog likely agree that technical personnel should produce accessible products without question. However, in a time when much web content is produced and delivered by nontechnical individuals, what are the most reasonable expectations?

Faculty and staff should not be expected to achieve accessibility alone, yet they should still be held responsible for the accessibility of their content. This seeming contradiction is best solved when there are explicit expectations, training, and just-in-time supports. If faculty and staff understand what is expected to be their responsibility–and when the task should fall into more technically skilled hands–they will be more likely to participate with the institution’s efforts. When creating accessible content goes beyond what would be expected of them, they should know whom to contact, where they take it, and specifics on the turnaround time. In my many years teaching, I must admit that I would complete class materials and PowerPoint presentations just in time for each class. If I were required to provide materials a week ahead of when I needed it, I might be in trouble.

It goes without saying that training specific to what faculty and staff are asked to do must be delivered to them. But, another critical aspect is the support they are offered. When a staff member has a question, whom do they call? What are the times available for staff members to make these calls? Not many institutions have included accessibility supports into their faculty help desks, but perhaps the time is right for this solution. Faculty members who receive just-in-time supports improve their knowledge and skills. Having these discussions at your institution will help you create the best solutions so content creators can assume responsibility for the accessibility of their content.


Note: Next month you will be hearing directly from a faculty member who implemented accessibility across her classes. She will describe her own experience with the items she could implement and those she could not. She received individual training and support, which is not common in postsecondary settings. Her experiences illustrate an emerging challenge in our web accessibility efforts. We hope you will read her guest blog, and that it helps provide perspective, and fodder for discussion at your institution.

Faculty member says “HELP – I can’t tag my PDF articles”

From time to time I am reminded of the complexities and nuances inherent in web accessibility. This happens most often when talking to someone new to the effort. I recently visited with a faculty member who is just beginning to address accessibility in her courses. She knows that PDF’s need to be properly tagged to be accessible and she was enthusiastic about doing it, even when it involved retrofitting accessibility elements into her PDF’s. But she was quickly at a stalemate for articles in her course CMS. When this happened she assumed she was doing something wrong, rather than identifying that what was wrong was the document itself. The experience made me reflect on the fact that while we often talk with faculty members about making sure that they have PDF’s that are accessible, we might not provide them with a good enough starting point.

Readers of this blog who are familiar with PDF accessibility know that to start to address accessibility of an existing PDF document, you must have a PDF that was properly created. However, many faculty members don’t create the PDF’s they end up with. If the document is not composed of true text, you must use Optical Character Recognition (OCR) on the document before other accessibility information can be added. While this step is less common all the time (thank heavens), it is important that we help faculty or staff understand how they can tell if PDF’s contain true text to begin with.

This was the step that eluded the faculty member with whom I was talking. She did not know that she needed to determine if her PDF was a scanned image or not. Because of this she assumed that her first step would be the tagging of the document itself. Of course she could not do this because it was in fact an image. Then she assumed she was doing something wrong.

There are many ways for non-technical people to determine if the PDF they wish to make accessible contains true text. Here are two ideas I shared with her and both were easy for her to implement. First, I asked her to see if she could select and copy some portion of text, and second I told her to try to search for some text element on the page. Both were successful strategies for her to determine which pages she could, and could not tag. Getting focus directly onto the text is critical if you will add an element to it (e.g., Header, ordered list).

If you are working with faculty on accessibility issues, or are a faculty or staff member yourself working on accessibility, you may be privy to similar situations in accessibility –- where a simple step was overlooked that proved significant for the person trying to create accessible content. We are very interested in hearing your experiences and sharing them with others. Please consider sharing your tips and experiences here.

Summertime, the perfect time to reflect on accessibility

Summertime for many in higher education is a time to catch up on tasks not completed during the academic year. It is also a time when the seeds are sown for new initiatives and priorities that will be fleshed out and approved in the coming year.  Many individuals, who work on web accessibility for their institution, work beyond the typical nine-month academic calendar. This combination of events makes summer the perfect time to reflect on initiatives for, and outcomes of, the institution’s web accessibility efforts.

Of course when we talk about “web accessibility” we are talking about two things. It is both the process on campus created to improve web accessibility as well as the product of those efforts (i.e., the accessibility of your web content).  We have written about this important coupling before (See Assessing your Institution’s Web Accessibility Efforts; Part 1: Evaluating the Process; Part 2: Evaluating the Product).

I am hopeful this summer you will ask yourself if your campus is ready for an increased focus on web accessibility this coming year.  Some of you are just beginning the process of institution-wide web accessibility efforts –you may be crafting plans to secure administrative support or identifying the best team to guide the campus-wide plans.  Others of you are in the midst of writing draft policies or crafting implementation plans.  Finally, there are others of you who have these in place and are working through the issues to make sure your planned efforts are receiving the resources and supports necessary for success, and will begin a round of assessment by looking at the actual accessibility of pages.

With any of these efforts, knowledge of your institution’s culture of change is vital; is it top-down, or does it require grass roots support?  Knowing this can streamline the support of those in administrative positions who can make sure you have not only the support necessary to complete the work, but also the administrative muscle, to work around the roadblocks that inevitably impede the path. Also critical is your knowledge of other institutional priorities such as increasing diversity at your campus or beginning a cycle of reaffirmation with your regional accreditation commission.  These are times when you might want to reach out to those whose role it is to engage in those priorities and have a conversation about the many outcomes that are indeed shared ones. Often reaching out to coworkers with these shared priorities can be more effective than attempting to tackle accessibility on your own.

So, if your answer is “Yes, I would like to help my campus increase our web accessibility efforts next year”, take the time needed to commit those ideas to paper and reflect on the best strategies to meet your goals.  For some of you it may be time to engage in another round of the GOALS Benchmarking and Planning tool. If you create a new cycle before benchmarking again, you can compare your progress to date.  You may benefit from looking at where you have already made progress to determine next steps.

From all of us at Project GOALS, have a wonderful summer, enjoy some vacation time, and start making plans now for the academic year to come.  Fall always comes sooner than we want.

Budgeting for Web Accessibility

For many units in higher education, April is budget month; these budget requests detail expenditures for the coming fiscal year that will begin July 1. Of course, those line items must be a good fit for the implementation planned in the coming year. To that end we have written a resource for those who are creating budget requests to support web accessibility. It is only through the process of securing an adequate budget that your efforts can succeed.

Joe Biden once famously said; “Don’t tell me what you value, show me your budget, and I’ll tell you what you value.”  If you have budget stories, ideas, or successful strategies to share with others to help with their budget process, please share them here. I look forward to seeing how creative others have become to secure the budget that is needed for web accessibility efforts.