Content Requirements

Headings

Heading 1 (h1)
It is mandatory that each page have one, and only one, heading 1 element.

Heading order

• You can nest headers but they must maintain a logical order.
• Heading 2, then heading 3, then heading 4, and so on.
• You can go back to a previous header but can not skip around.  For instance a heading 3 must be followed by a heading 2, or a heading 4.  You can not use a heading 2 and then a heading 4, it must be heading 2, then heading 3.

Learn about headings in OmniCMS

Learn about making headings accessible

Learn about making quality heading text

Links

• Link text is unique to each URL, the same text can not be used for different URLs
• Link text CANNOT be the URL.  Link text needs to be screen readible
• Link text should provide a clear understanding where users are being taken, elimiate words like "click here" or "learn more" as they convey no meaning.

Learn about making links in OmniCMS

Learn about making links accessible

Learn about making quality link text

iFrames

• iFrames (embedded content) need a title attribute and internal content.
• Internal content should tell them what was being presented, and could inform that iframes are required.
• A link can be added if you absolutely need the iframe source materials.

example:

<iframe title="required title">Internal content goes here, and will be displayed to the user when iframes are not supported</iframe>

Tables

• Tables are meant for tabular data, like a spreadsheet, and not for layout or design.
• Headers (th) are required for each column or row.
• They also require a summary, which in OmniCMS, can be found in the table properties as a checkbox.  It's an overview of the table, and not explaining each item within.

Table data must be consistent for each header.  If you have a field that is marked "contact info" with email addresses, you should not add phone numbers too.  It would be better to list them out as "contact email" and "contact phone" under two columns.

Lean about making tables in OmniCMS

Learn about making tables accessible

Online forms require that you use labels on your input elements.

• A label needs to be identified for each element and identify the purpose of  your input.
• When formatting your code, it's best to put the label text first, before the input, so screen readers inform the user of content before making them choose an option like a checkbox or radio button.
• If using a group of inputs, such as checkboxes or radio buttons make sure that you include them in a fieldset container.  This helps users group options and puts clarity on their association.

example:

<p><label for="txtFirstName">First Name: <input type="textbox" id="txtFirstName" /></label></p>

Learn more about accessible forms from WebAIMlink opens in a new window

Learn more about accessible form controls from WebAIMlink opens in a new window

PDF 

It is recommended to just create content as web pages. PDF documents have their use, but for the majority of users a web page will work better than a PDF document.

PDF documents come with a reading order which helps screen readers navigate the file. Verify that the reading order is correct after each time the document is modified.  Even a small change can alter.

PDF documents with images or info graphics are also required to have alternative text in the same document. This means if you use a mouse and highlight you can detect each letter.  Information posted within a graphic can not be read by screen readers.

Word, Excel, Powerpoint

When posting these types of pages online make sure that you have reviewed them for accessibility standards. Microsoft does contain acceesilbility tools within their products to help you verify that users who require assitive technology are able to use these files without issues

YouTube, Vimeo, any online media file

Its mandatory that you include close captions with videos. These can be auto generated but they also require that they are accurate, so review files if auto close captions are being used.  Names, specific titles, and locations are all vital information that can often be malformed by automated services and we want users to be able to get accurate information if they use the audio or not.

If you're using images, videos, or non-text content you need an alternative text based format.

• Text equivalent must be on the same page
• Equivalent means if image / video is removed same understanding is relayed to users
• Video captions must be accurate, review and correct before posting or after any edits/updates

Learn about making video / audio accessible