About the Knowledge Base

This shared space provides the City of Toronto's development, QA and UX communities a detailed and evolving set of standards, practices and techniques for ensuring digital with an evolving source of knowledge for ensuring the accessibility of City of Toronto websites and web applications.

The details within will be are useful for both remediating issues in existing applications , and adopting an Accessibility by Design approach during design and development.

The pages in the Knowledge Base are intended to:

• Provide

  provide concrete, code-based development techniques to improve accessibility in City web applications and content

  .

• Explain

  explain why an issue or technique is important to users

  .

• Identify

  identify the City’s

  standard

  recommended solutions for areas of confusion about WCAG requirements

  .

Please feel free to contact the AODA Compliance Public Facing project team Project Team at digital.accessibility@toronto.ca with any questions or comments.

...

Examples of when to use: 

• Providing a text alternative for an icon button like a magnifying glass/search button

• Providing text intended to help non-visual users understand the interface.

.sr-only-focusable

Bootstrap class name: .sr-only-focusable

...

Examples of when to use: 

• Skip links before content that a keyboard user may want to jump over, e.g. a page header or a section navigation.

Terminology

Visual and Non-Visual Users

...

We use the terms “visual user” and “non-visual user” (rather than, for example, “sighted” and “blind”) because a sighted user might be consuming a page in a non-visual way. For example, a sighted user with dyslexia might use a screen reader to help them understand content. The distinction is one of how a user is consuming the content, rather than making assumptions about why they are consuming it that way.

In This Space