Welcome and Logistics

Welcome to Global Accessibility Awareness Day at the University of Minnesota. We are grateful you are with us today, or watching the recording afterwards.

The event is through individual Zoom webinars and meetings. You will need to register for each session. Each session will be recorded. If you cannot attend the session, please do not register for it so others are able to attend.

Style Guide

Citations

Include 1–3 citations supporting our recommendations from our preferred sources:

Duplicating Content

Don’t repeat information like legal implications; link to Legal Obligations page instead.

Don’t include how-to instructions; link to our preferred sources instead (see how-to instructions below).

Headings

Make headings actionable and positive, especially on the Core Skills and similar pages: Not “Techniques for Text Emphasis” or “Never Use Color Alone to Show Emphasis,” but something like, “Use Color with Another Cue for Text Emphasis.”

Use headline style capitalization for all heading levels. The Accessible U Committee consulted the following sources, and decided that choosing a style and being consistent is the most important, so chose headline style capitalization.

  • WAI's style guide recommends headline style for most headings. However, they  recommend sentence case for "Tips" headings.
  • The Folwell Design System and University Relations style guide do not address this topic. University Relations staff use Associated Press sentence style headings for news stories, and headline style capitalization elsewhere except for some content like tips.
  • Knowledge editors in the Office of Information Technology use headline style in their how-to articles.

How-to Instructions

Include links to 1–3 step-by-step instructions for a particular technology: 

Language Relating to Disabilities

The Accessible U website uses a mix of person-first or people-first (“people with disabilities”) and identity-first language (“disabled people”).

Currently there is no consensus for using person-first or identity-first language among various disability cultures. There may be a broad consensus within a group about which version of language to use, but individuals may have a preference for the alternative. Our overall aim for this website is to be as inclusive as possible.

The American Psychological Association (APA) style guide disability page provides this guiding principle, by which we abide:

“The overall principle for using disability language is to maintain the integrity (worth and dignity) of all individuals as human beings.”

We consult the Employer Assistance and Resources Network on Disability Inclusion Person First and Identity First Language page, and also use these identity-first phrases:  

  • "autistic people"
  • "blind people"
  • "Deaf" (hearing-impaired is not acceptable to most Deaf people or hard-of-hearing people).

If you want to provide feedback on the use of language on this site, please send a message to [email protected].

    Media

    • Caption images and videos and/or provide a direct link to videos
    • Link to YouTube videos because having multiple embedded videos in accordions caused all the videos to play at once for users on some browsers
    • Link to Kaltura videos because there isn’t an easyway to embed them

    Summary Content

    Include a Summary on each page; they are configured to appear in search results.

    Text

    • Spell out acronyms the first time they are used on a page or in a tabbed section, then use the acronym 
      • Google Doc instead of Google doc
      • Use shift + option on a Mac for m dashes (—) instead of a hyphen (-)
      • Use bulleted lists for more than two items and paragraphs for less than two
      • On core skills and similar pages, include a Do and Don’t heading level 4 under each specific accordion title styled as a heading 3. For the Don’t items, make sure each reads as a negative, such as “Don't use images just to fill a page.”

      ARIA

      Accessible Rich Internet Applications (ARIA) is a set of attributes that define  ways to make web content and applications (especially those with JavaScript) more accessible to people with disabilities. But native HTML elements have built-in keyboard accessibility, roles, and states.

      If you choose to use ARIA instead or in addition, you are responsible for mimicking the equivalent browser behavior in script. If you are not a developer, you will need one to implement ARIA.


      Impact

      ARIA tags can greatly enhance accessibility, usability, and navigability for screen reader and screen magnification users. Developers can use it to incorporate accessibility into both new and legacy pages.

      ARIA supplements HTML so that interactions and widgets commonly used in applications can be passed to assistive technologies when there is no other mechanism.

       

      Dos and Don'ts

      Dos and Don'ts

      Expand all

      Dos and Don'ts

      Use Native HTML When Possible

      HTML, when implemented correctly, conveys the semantic meaning of the content to people using assistive technology (such as screen readers) without any additional effort because it is already mapped to the accessibility APIs.

      Do

      Use HTML elements.

      Don't

      Don't use ARIA when an HTML element is available.

      Don't change native semantics unless it is essential.

      Make ARIA Controls Usable With a Keyboard

      ARIA overrides certain HTML attributes and functions. It also provides custom control semantics, but the control won't work as expected with a keyboard.

      Do

      Use ARIA and JavaScript to make custom controls accessible with a keyboard.

      Don't

      Don't use role="presentation" or aria-hidden="true" on a focusable element.

      The ARIA-hidden attribute is intended to hide the content or element from the accessibility APIs and the element that has ARIA-hidden set to true is not supposed to be interactive in any way. Defining either of these attributes on the visible focusable elements results in some users focusing on nothing.

      Include Accessible Names With Interactive Elements

      Interactive elements such as but not limited to the following must have accessible names:

      • Links
      • Buttons
      • Text fields
      • Combo boxes
      • Radio buttons
      • Checkboxes

      Without an accessible name, assistive technologies do not understand what the control does.

      Do

      Do use varying techniques to provide accessible names, which vary from control to control.

      Some Techniques for Providing Accessible Names
      Control Technique
      HTML links and buttons The link text or button value becomes the accessible name.
      Input text fields Associate a form control with its visible label either implicitly or explicitly.
      Custom widgets Use ARIA-label or ARIA-labelledby.

       

      Don't

      Don't include an interactive element with a visible label but no accessible name.

      What You Can Do

      Accessibility is everyone's everyday work. Whatever roles you play—faculty, staff, student, and more—you can help create a more inclusive University. Make a commitment to start small, and continue learning and practicing.

      Find Accessibility Resources

      You may also get information and support by attending or reviewing recordings of accessibility events.

      Results

      Displaying 11 - 20 of 112

      Filter Results
      Event Recording

      Accessible Social Media Event on

      Join the Accessibility Ambassadors for a presentation by Susan Hagen of University Relations about making social media more accessible.

      ...

      Event Recording

      All About Screen Readers Event on

      Join the Accessibility Ambassadors for a demonstration and discussion of screen readers by Accessibility Ambassador Khaled Musa from Academic...

      Accessible U Web Page

      Alternative Text

      Add alternative text, or “alt text,” to every meaningful image in digital content.

      Supporting Unit

      Bakken Center for Spirituality and Healing

      The Bakken Center enriches health and wellbeing by providing interprofessional education, delivering innovative engagement programs, and...

      Event Recording

      Campus Climate for Students with a Disability or Condition Event on

      The presentation will cover results from the most recent Student Experience in the Research University (SERU) survey, highlighting results from...

      Campus Climate for Students with a Disability or Condition recording (41:02)

      Additional slides were added to the presentation that reflect the student counts requested from the live audience.

      Event Recording

      Canvas Accessibility with UDOIT Event on

      Join the Accessibility Ambassadors on Thursday, May 28, for a presentation by accessibility ambassador Khaled Musa of Academic...

      Professional Development, Public Web Page or Site

      Canvas: Design an Accessible and Usable Course Site

      Learn about good practices for creating course sites that are both usable and accessible to the widest range of students, including...

      Event Recording

      Captioning Event on

      Videos and teleconferencing are part of everyone’s daily life in a (nearly!) post-pandemic world. But videos by themselves often leave a...

      Supporting Unit

      Center for Educational Innovation (CEI)

      CEI offers a variety of opportunities to deepen your learning and expand your practices on this topic and others. They include: ...

      Event Recording

      Centering Disabled Community Members Event on

      Join the Accessibility Ambassadors for a presentation by Jay Wilson and Corbett Laubignat of the Disability Resource Center.

      Corbett and...

      Expand all

      Authors, Designers, and Editors

      When you think about accessibility laws and related University policies, you might think they apply only to course and website content.

      But at the University of Minnesota, we create thousands of digital content products each day. These can be in a variety of formats, and should all be as accessible to the widest range of audiences as possible

      Instructors

      The more you make your course accessible, the fewer accommodation requests you may receive.

      In addition, more students will be able to better learn from and navigate your course materials and classroom experiences, even if they have different learning styles and abilities.

      Leaders and Managers

      Leaders can communicate a clear and achievable vision for digital accessibility within the organization.

      Managers can drive action by communicating a vision, establishing clear goals and expectations, and providing resources and training.

      Check out Promote Digital Accessibility for ideas.

      Presenters

      You can make your presentations and events you host more inclusive.

      For example:

      • Verbally describe your slides while presenting.
      • Include alternative text for images.
      • Provide captions, audio descriptions, and transcripts.

      Students

      When you produce digital assignments, apply the core skills and your instructors and the students you collaborate with will be better able to understand them, even if they use assistive technologies.

      Technology Purchasers

      Before a big purchase, the wise shopper gathers requirements, performs research, and reviews potential solutions.

      At the University, your digital technology pre-purchase checklist must include an evaluation of the extent to which a product is accessible and how a vendor meets accessibility standards.

      Web Developers

      From a developer's perspective, the goal is to code a website or web application that, at minimum, meets Web Content Accessibility Guidelines (WCAG) AA standards and follows the POUR guiding principles of accessible technology.

      Speaker Guidelines

      Live Captioning

      During the Global Accessibility Awareness Day conference, sessions will have live captioning. In order to improve the quality of this service, we ask everyone to speak slowly and clearly so the captioning service is able to accurately capture what you say.             

      Note: Do not use any built-in captioning options (such as Google Slides captioning or Microsoft Translator) while recording your presentation, as it will interfere with the automated captioning the conference will be using.                

      Community Agreement

      About Community Agreements

      Community agreements have many names: participation guidelines, community expectations, group contract, code of conduct, etc. Regardless of the title, these documents aim to set the tone, address inter-relational dynamics, and establish shared understandings between members of a workgroup.  In a learning community,  like ours,  these points of agreement provide the support needed to deepen our collective engagement and do the hard work.