Website resources


Content accessibility 

Content editors are responsible for their content's compliance with federal and state accessibility laws. Below are instructions for content editors at UW Bothell on how to make your web pages accessible when using Kentico. Content editors can also download the accessibility checklist to get more details on what elements of your content need to be accessible and why.


The documentation below is intended to only support the editor in learning how to make their content accessible. A list of documentation on how to use the editor toolbar in Kentico is also available.

  • Headings should be in semantic order:  page title will always be marked as a "Heading 1" but within the content areas, content editors can choose between the headings "Heading 2" through "Heading 5". 
    • Headings should related to each other on a page. Headings 2-5 should related to Heading 1. Think of headings like buckets of information and how they each relate to each other.
  • Images need alternative text: A screen reader will land on the image and say "Graphic of..." and read whatever alternative text has been added into the field. If an image doesn't load on a page, it will also display the alternative text.
  • Tables need table headers and captions: Table headers are different from content headings. They denote the difference between the information in the table cells from the information in the table headers.
  • Meaningful Link Text means text that is hyperlinked should be able to stand alone independently of its context. For example, links like “click here” and “more” are meaningless out of context but "download the accessibility checklist" or "read about our degree options" are descriptive and allow the end-user to better anticipate what they're selecting.
  • Videos should always have closed captioning and YouTube auto-generated does not count as a final product but is a great place to start for manual updates. There are other free and fee-based options as well.
  • Electronic Documents (PDFs, Word Docs, etc.) need to be accessible. How you make it accessible depends on the format (.pdf, .docx, etc.).
  • External applications need to be checked for accessibility prior to procuring it. The university is liable for inaccessible software, programs, etc.; the vendor is not liable. Sometimes need to get certain verbiage in contracts as well to ensure products accessibility. 

Communities of practice

Join the AccessibleWeb@U mailing list to hear from a community of UW web designers, developers, and other interested individuals who discuss and share ideas on accessible web design.