Accessibility HELPS: Structure

Structure includes all the technical tagging needed to make content accessible to assistive technology. Most of this is integrated into systems supporting campus communications, like the main website template and Canvas. If you encounter issues with a template, it is likely there for security or accessibility reasons. Consider reaching out to the web team to find a better solution.

A note for using non-standard CMS (Content Management Systems)

CSULB tests its common Content Management Systems such as Drupal for the public website, and Canvas for course content to ensure the system is as accessible as possible. If you are unsure if the system you are using passes accessibility standards, please reach out to the ATI Compliance team to verify. If you are using a custom CMS, it is your responsibility to ensure your CMS is compliant. Our legal requirement is WCAG 2.1 level AA, and the ATI-Compliance team can assist in reviewing custom code to ensure your product fundamentally meets this standard.

Tables

Tables require proper structure, including table header cells with scope and table captions. Tables are complex to design and read and should only contain table data. For additional information on setting up tables for HTML, see W3C: Tables Tutorial or WebAIM: Creating Accessible Tables.

Some content creation systems, like Microsoft Word, have limitations regarding table complexity. Please see the appropriate Content Creation page to understand these limitations or reach out to ATI Compliance for additional support.

Layout Tables 

Authors should not use tables for layout purposes. Instead of putting an image with associated text into a table, use a two-column layout or other proper structural layout. This approach provides a better reading experience on both assistive technology and different screen sizes, such as phones, tablets, or windowed browsers.

Accordions, columns, etc.

Columns, Accordions and other complex content layouts must be developed to be accessible, so the implementation must be tested with accessibility in mind. Using the templates as implemented is generally safe on an accessible website like the CSULB Drupal environment. If you are creating this content in a different CMS, you must ensure proper read order, keyboard functionality and reflow.

Forms

Forms are very complex. The best practice is to use a form creator, such as Qualtrics or Microsoft Forms. Forms are available in the Drupal environment as well, please contact WDC for help creating accessible forms for the website.

Custom apps

According to the ADA, all web and mobile apps must be fully compliant with WCAG 2.1 level AA. This means if you are developing a custom app, you must meet all WCAG 2.1 criteria. While ATI Compliance can support accessibility testing, it is your responsibility to ensure you request this review prior to making this content public.