Creating Accessible Content in MyFacilities Building Event Notices

Creating Accessible Content in MyFacilities Building Event Notices

Content Creation 
Language
Font
Titles and Subject Lines
Headings
Headers and Footers 
Lists
Spreadsheets
Tables
Check Your Accessibility
Things To Look Out For
Resources
When developing any content, it is crucial to ensure accessibility for all users, including those who rely on assistive technologies. This guide provides a summary of best practices for creating accessible content that follow Web Content Accessibility Guidelines (WCAG) and Washington State University (WSU) standards.
Note: many applications feature accessibility checkers and provide detailed documentation for addressing more advanced accessibility issues.

Content Creation

Language

  • Use plain language appropriate for the intended audience.

  • When using abbreviations or acronyms, they must be defined early on.

    • For example: Washington State University (WSU) is in Pullman, Washington (WA).

  • Avoid using sensory characteristics, references to shape, size, sound, color, and location, when providing instructions.

    • Use: Select the link that says Understanding Sensory Characteristics for more information.

    • Not: Select the link at the bottom of the section for more information.

Understanding Sensory Characteristics

Font

While Web Content Accessibility Guidelines (WCAG) require that you use a plain easy to read font, WSU has several recommended fonts. Note: some of these fonts may not be available for all applications.
For Print and Digital:
Proxima Nova
FreightBig Pro
For Web:
Montserrat
Microsoft Office:
Corbel
Arial
Baskerville Old Face
While it is tempting to use a "fun" font, they can be difficult to read.Font size should be a minimum of 12 points.Outside of titles and headings, text should be in the "normal" style.
Understanding Accessible Fonts and Topography for Section 508 Compliance

Titles and Subject Lines

Saved documents (such as PDF or Microsoft Word documents) require document titles so that a screen reader will be able to scan and read it. Some applications, like Microsoft Word, add a title when the document is saved but others, like Adobe Acrobat, require a title to be manually added in the document properties. Accessibility checkers in the document creation application should indicate if the title needs to be added.
A document title or email subject line should clearly communicate the purpose, provide a summary of the content, and be easily searchable.
Titles in Documents
Tips For Writing Accessible Emails: Subject Lines

Headings

Documents with segmented information should follow the Heading 1, 2, 3, format so that a screen reader can determine which order information is scanned.
Example:

Chapter 1

Section 1

Section 2

Subsection 1


This hierarchy helps a screen reader determine that Section 1 and 2 are under Chapter 1 and that Subsection 1 is under Section 2.
WSU Digital Accessibility Core Concepts - Headings

Headers and Footers

Screen readers do not automatically read information in headers and footers. Important information must also be duplicated at or near the start of the main content area, and never just in the header or footer.
Accessibility Oz: Headers, Footers, and Table of Contents

Lists

When creating lists of information, use the built-in list bullets or numbering feature in the application. These features are designed to work with accessibility devices and applications.
WSU Digital Accessibility Core Concepts - Lists

Spreadsheets

  • Ensure that you have text in cell A1, this can be the title of the document or the first table.

  • Give all worksheets unique names and remove blank worksheets.

  • Visually scan your workbook to see which cells and ranges would benefit from having a name.

  • If you cannot avoid a blank cell, column, or row, enter text explaining that it is blank. For example, type N/A or Intentionally Blank.

Section 508: Create Accessible Spreadsheets

Tables

  • Tables should not be used as layout or style content on a page.

  • When adding a table to a document, build the table using the application tools. Do not use a screenshot or image of the table.

  • Tables need clear structures so they can be scanned by a screen reader. The simpler the tables, the easier a screen reader can scan them.

  • Table information should read from left to right instead of downward.

  • Information in Table Headers cannot be identified by some screen readers.

  • Avoid merged or split cells when designing your table.

  • Avoid fixed width tables.

  • Table cells need to contain the same type of data. Do not use empty cells to provide captions, footnotes, and endnotes.

  • When including hyperlinks in your table, ensure the link text is meaningful and does not break mid-sentence.

  • Add an alt text description to each table.

  • When creating multiple tables, strive to make the tables consistent, keeping a similar number of rows and columns when possible.

  • Avoid placing two or more tables side by side or top to bottom to allow navigation by keyboard users.

Accessible Example:
Enrollment for sample class

Day of the Week

Time

Number of Students

Tuesday

9 am

5 students

Wednesday

1 pm

3 students

Thursday

11 am

7 students

Friday

3 pm

2 students


Inaccessible Example:
Enrollment for sample class

 

Week 1

 

Week 2

 

Day of the Week

Tuesday

Thursday

Wednesday

Friday

Time

9 am

11 am

1 pm

3 pm

Number of Students

5

7

3

2


WSU Digital Accessibility Core Concepts - Tables

Check Your Accessibility

Many applications have a built-in accessibility checker. These checkers may not catch all accessibility issues. However, many application companies provide additional information in their help/training centers online.
Easy Checks – A First Review of Web Accessibility
Manual Testing for Accessibility
How to Determine if a Document is Accessible

Things To Look Out For

  • While PDF documents serve specific purposes, they are generally less accessible compared to other document formats. For web content, it is advisable to avoid using PDFs. Instead, HTML is recommended to ensure better accessibility and user experience.

  • For longer documents, provide a table of contents.

  • Content must be navigable using only a keyboard.

  • Attachments

    • All attachments must have unique and descriptive file names.

    • Attach as a copy instead of to a cloud link.

  • When creating a specific type of document, it is better to use an application designed for that particular document creation. For example, create a form in Microsoft Forms versus in Excel.

  • Navigate the content with the up, down, right, left arrow keys to ensure that it matches a visual/logical reading order.

  • Avoid using apps, plugins, widgets, or JavaScript techniques that set traps when navigating with a keyboard. Users should be able to get in and out of interactive elements with ease. One exception is a modal dialog, where keystrokes are expected to be trapped within the dialog until the dialog is dismissed.

  • Use multiple navigation options such as a navigation menu, a search feature, and/or a site map.

  • Make sure to use the available style and formatting tools provided within the application.

  • Ensure that your content is accessible on a variety of devices.

Resources

WSU Digital Accessibility Resources
WSU Digital Accessibility Guides
Ncdae.org: National Center on Disability and Access to Education - Digital Accessibility Cheat sheets
Section 508 Content Creation
Section 508 Training Video Library