Digital Accessibility Guides and Resources
If you haven't already checked out the Digital Accessibility Basics Training Series, please do so when you have a chance! This series will provide some context for any of the environment-specific how-to guides listed below.
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
If a resource must be published as a PDF, it requires a title, appropriate reading order, alternative text, and tag structure. Please keep in mind that Adobe Acrobat Pro is required in order to validate these elements and remediate any accessibility gaps.
- NCDAE: Adobe Acrobat XI Accessibility
- WebAIM: Converting Documents to PDF
- WebAIM: Acrobat and Accessibility
Though a great deal of content generated via Confluence is intended for internal distribution, there are definitely some help materials that are made available publicly. Regardless, content in this environment must also be accessible.
If you are a faculty member, please refer to the Office of Academic Innovation's faculty support web page for instruction and guidance in designing accessible instructional materials. For assistance in locating and using resources, see the Library's Services for Faculty.
Content editors responsible for their respective department's pdx.edu web space should reach out to the Office of University Communications with any questions related to accessible content building in the current and new Drupal spaces.
All students, faculty, and staff at PSU have access to Google's G Suite applications. Questions regarding how to use Google Apps or generate content may be answered in one of OIT's
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.. The following are specific resources for accessible design within Google apps:
Please note that content generated via Google apps will only be fully accessible under certain conditions:
- Google Docs must be designed with accessibility in mind and published as HTML prior to distribution as the original version will be difficult to navigate via adaptive technology.
- Google Docs does not currently allow for the generation of accessible tables. As much as possible, please avoid using this feature in published Docs.
- Google Sheets must be downloaded and distributed as accessible Excel files, as there is not yet an option for generating fully accessible Sheets.
- Google Slides must be downloaded and distributed as accessible PDF or PowerPoint files, as there is not yet an option for generating fully accessible Slides.
While a transcript is sufficient for archived audio, videos and live audio must have captions and an accompanying transcript. Captions should be synchronized, equivalent, and accessible. This means that automated speech recognition (or auto-generated captions) are not sufficient. Captioning can be generated or corrected with self-captioning tools like Amara, Subtitle Horse, and YouTube. Alternatively, captioning may be contracted to a third party at your expense. Contact firstname.lastname@example.org for details.
Microsoft content in Excel, PowerPoint, and Word can be designed and distributed accessibly with relative ease. The following are several resources for accessible design within Microsoft products:
- Microsoft: Make Your Content Accessible to Everyone
- NCDAE: Excel Accessibility (Windows and Mac)
- NCDAE: PowerPoint Accessibility (Mac)
- NCDAE: PowerPoint Accessibility (Windows)
- NCDAE: Word Accessibility (Mac)
- NCDAE: Word Accessibility (Windows)
- WebAIM: Microsoft Word Accessibility
- WebAIM: PowerPoint Accessibility