Web Services banner showing several students using various media (phone, tablet, laptop) to browse the web

Web Services

We provide solutions and support to members of the KCTCS community, through our public and internal web properties. 

The public web properties are managed within a content management system, Sitecore, which gives content experts the ability to edit their own content, quickly and easily, from any location and at any time of day. Our intranet solution, thePoint, helps make it easier for employees to collaborate across the state. 

We work together in an effort to provide the best user experience for all our audiences.  If you have questions or comments about our sites, please let us know!

Web Content Policies Summary  

We are committed to providing Web content that is both consistently branded and accessible to all users, irrespective of their differing abilities.

Web Services takes the lead in training content owners and subject matter experts in effective online communication. KCTCS content owners and experts may consult with us regarding specific compliance issues.

In general, we provide the following guidelines around branding standards and accessibility standards.

Branding standards

  • All KCTCS web properties should comply with the color palette, logo requirements and other relevant standards as described within the KCTCS Brand Guide.
  • Special considerations apply to mobile and dynamic versions of online content, where the delivery context may make certain, rigid requirements unsustainable. For example, abbreviated "initial letter" logos may be used for small screen delivery. Web site owners should consult the draft Mobile Branding Guidelines document, available from Web Services when considering mobile versions.
  • Branding and accessibility concerns go hand in hand. The use of non-standard, decorative fonts should be kept to a bare minimum and used for necessary display purposes only. When it is technically impossible to embed a font, alternative text must be provided.
  • A screen is not a printed page, and all design and content decisions must take into account the different delivery contexts of web information, which include not only small- and large-screen devices but also assistive technologies such as screen readers and braille outputs. Design elements must degrade well and provide an acceptable baseline experience for all users.

Accessibility standards

It is both legally necessary and practically important that web content is accessible to the fullest range of users and technologies. As a minimum, content producers should:

  • Write content as clearly and concisely as possible in order to get the message across. This includes front-loading important content at the top of a page or the beginning of a paragraph.
  • Use semantically correct HTML including
    • A logical hierarchy of headings. One "heading 1" (H1) on each page, followed (as necessary) by lower-level headings (H2, H3, etc.)
    • Textual equivalents to all media content including images and videos (where time-sequenced captions must be provided)
    • Labels for all form elements, titles for all hyperlinks, correctly formatted lists, and tables labeled correctly.
  • Use device-neutral language. Not all users have a mouse (think foot-operated devices, or touchscreens) so “clicking” is not an adequate instruction. Additionally, to a user with a screen reader, descriptions such as “top left” are meaningless. Always use neutral language (for example, “select” instead of click).
  • Avoid relying on color or other visual qualities to communicate meaning. A color-coded diagram is meaningless to many readers.

When there is doubt about compliance, content owners should consult the Web Content Accessibility Guidelines 2.0 document for guidance.