Accessibility Implementation

Accessibility Implementation

Making bulk changes across your site
The separation of content and design in your CMS means you don’t need to change every element on every page – you can simply change the templates that govern elements across multiple pages, such as forms or list views that are shared across landing pages and search results.

Some jobs, however, like the addition of missing alt tags, still have to be done manually. But you can take a page out of the American Museum of Natural History (AMNH)’s book and crowdsource the additions you require. When AMNH needed to remediate its site that included over 30,000 images without alt tags, it set up Project Describe, inviting the public to help describe images with text that could then be imported in bulk back into its CMS.

First, it used an automated export process to pull images without alt tags out of its CMS and into Project Describe’s crowdsourcing system. Then it was able to bulk import the text back into its site into the appropriate alt tags – a task that would have been nearly unimaginable without a CMS in place.

Creating and applying code standards
When you create accessible templates for design elements like pop-ups and carousels, you’re creating code standards for your site that can be used over and over again. For example, whenever a content creator needs a pop-up item, they can simply select the template with code that has been formatted for accessibility, and enter their content into the form fields.

Templates can also enforce accessibility-friendly HTML conventions such as including “for” attributes for all form labels and implementing