General Website Info

The page title field is located within the Parameters section of the page in the CMS. Once the page is checked out, navigate to Properties or MultiEdit, and then select Parameters from the left side navigation.

Visit the CMS User Guide Search Engine Optimization (SEO) page for tips on writing page titles.

For example, the page is linked from the side navigation as well as another method, such as the main navigation drop down menu or via search.

Headings are used to create structure and organize content. Text on a page that is meant to be a heading should utilize the WYSIWYG editor's Blocks drop down menu.

Text pages in the CMS can use Headings 3-6, while Gallery pages can use Headings 2-6. When using headings, do not skip over levels (for example, Heading 3 followed by Heading 5). Heading levels can only be skipped when closing a subsection (for example, Heading 5 followed by Heading 3).

Headings should not be used to visually style text that is not a heading. Instead, consider using bold and italic to emphasize non-heading text.

Links should indicate to a user what will happen if they use the link. Do not use ambiguous phrases like "Click here".

How to write alt text can vary depending on the image and its context. Consider how you would describe the image to another person. Do not use phrases like "picture of" or "image of". However, a similar descriptor may be appropriate if the medium of the image is important to convey the image's content. For example, "illustration of" or "screenshot of".

Avoid having text in images if possible. If it cannot be avoided, include the text in the alt text.

Images with extensive amounts of text, such as infographics, still need to have the text available in a manner accessible to assistive technology. Use the alt text to provide a short description of the image along with directions to locate the rest of the image description. The full text should be included after the image or on a linked page.

When an image is linked, its alt text should indicate to a user what will happen if they use the link instead of describing the image. For example, an image of students that links to the tutoring services website should have alt text similar to "Tutoring services" instead of describing the students.

Regular text requires a contrast ratio of at least 4.5:1 for its foreground and background colors. Large text requires a contrast ratio of at least 3:1. Text is considered large if it is 14pt/18.5px and bold or larger, or if it is 18pt/24px or larger. Keep in mind that text in an image may not be as larger on smaller screens such as mobile devices. Also, if text is over a gradient or a background image, test where the contrast is lowest.

For example, USF Green (#006747) has a contrast ratio of 6.92:1 when paired with white. This passes for both regular and large text.

Note: These requirements do not apply if the text is incidental (decorative, "part of a picture that contains significant other visual content", etc.) or if the text is part of a logo or brand name.

Visit the CMS User Guide for tools to calculate contrast ratio.

Sensory characteristics include shape, color, size, location, orientation, and sound. Use text in addition to these to convey the necessary information.

For example, "click the green button at the bottom" would be inaccessible, but "click the green button at the bottom labeled 'Next'" would be accessible. 

Text and/or patterns can be used alongside to color to convey meaning. Also, consider presenting the data in an additional format, such as a table.

For example, a bar chart could use colors and different patterns, such as stripes and dots, to distinguish the bars.

Tables should not be used for layout or design.

Note: Table snippets include a caption by default.

Table captions function as a heading for the entire table. They can be enabled by right clicking within the table and selecting "Table properties". Then select the checkbox for "Show caption".

Note: Table snippets have a table header and table header cells by default. Columns added to a Table snippet will automatically have a table header cell.

The first row of a table can be transformed into a header by right clicking within the row and selecting "Row", followed by "Row Properties". Then change the "Row Type" from "Body" to "Header".

Then, change the data cells within the header into header cells. Right click within each cell and select "Cell", followed by "Cell Properties". Then change the "Cell Type" from "Cell" to "Header cell". Table header cells should not be left empty.

Note: Table snippets have scope applied to table header cells by default. However, the table header cells of columns added to a Table snippet do not have the scope automatically applied.

To associate a table header cell with the data cells in its column, right click within the header cell and select "Cell", followed by "Cell Properties".  The change the "Scope" from "None" to "Column".

All documents on a page, such as Word documents, Excel spreadsheets, PowerPoint presentations, and PDFs, need to be accessible.

Visit the CMS User Guide for resources regarding creating documents accessible.

Users must have the ability to pause or stop any content that automatically moves, blinks, or scrolls. For example, Hero videos and automatic rotators in the CMS have pause buttons.

Ensure there is nothing on your page "that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds."

Please review the WCAG 2.1 Success Criterion 2.3.1: Three Flashes or Below Threshold.

A transcript is required if the content can be understood without watching the screen. Captions are required if video is necessary for understanding alongside audio. Captions are also required for live audio when it is synchronized with another format, such as video.

Note: Captions are not required if the audio is provided entirely as an audio description for a video with no regular audio.

Captions should include dialogue, speaker identification, and meaningful sounds, as well as correct capitalization and punctuation when they affect understanding.

Automatic captions are an excellent starting point, but must be reviewed to ensure accuracy. 

Pre-recorded video that is synchronized with another format, such as audio, may need an audio description to ensure all information is conveyed. An audio description is not necessary if all the information presented in the video is already provided by the audio.

Please review the WCAG 2.1 Success Criterion 1.2.5: Audio Description (Prerecorded).