WEB ACCESSIBILITY TERMS
What is web accessibility?
‘a11y’ is a numeronym for the word ‘accessibility’.
A numeronym is a word where a number is used to form an abbreviation.
There are 13 letters in the word ‘accessibility’. Beginning with an ‘a’, followed by 11 letters, then ending with ‘y’, therefore ‘a11y’.
#a11yTO (#a11y Toronto)
#a11yTO, or A11y Toronto, is a meetup group and volunteer organization that brings together designers, developers, and other accessibility advocates to discuss best practices and case studies, and educate people new to accessibility on how to get started. Their programs also include a series of conferences, most notably #a11yTO Camp in the spring, and #a11yWeekTO every October.
Americans with Disabilities Act (ADA)
The Americans with Disabilities Act (ADA), is the legislation that defines accessibility standards at the federal level in the United States. ADA is also based on WCAG 2.0 standards. If you’re an organization based in the United States, it’s important to comply with these standards to avoid legal action under ADA or section 508 (defined below).
Related:WCAG 2.0 / WCAG 2.1 AODA Section 508
Accessibility for Ontarians with Disabilities Act (AODA)
The Accessibility for Ontarians with Disabilities Act (AODA) is Ontario’s version of accessibility legislation. Based on requiring compliance with WCAG 2.0, AODA has general compliance requirements that many organizations must meet by January 2021, specifically, government organizations, and all organizations with more than 50 employees operating in Canada.
It is strongly recommended that all organizations in Ontario work towards WCAG 2.0 AA compliance to meet AODA legislation in the future in order to ensure future compliance requirements and simply to improve website user experience for all users.
Related:WCAG 2.0 / WCAG 2.1 ADA Section 508
Accessible Rich Internet Application (ARIA) labels
ARIA labels, or Accessible Rich Internet Application labels, are a type of code attribute that allows developers to add descriptions and context to the elements on a webpage for users of screen readers.
ARIA labels can be used as labels for text fields, interactive widgets like accordion or slider controls, or as supplementary text for links and buttons.
If you have a number of similar links on a page, such as ‘learn more’ or ‘get started’ you would use an ARIA label to better identify the topic of these links, such as writing “Get started with accessibility today”.
Related:Automated accessibility checkers Alt tags WCAG 2.0 / WCAG 2.1 AODA ADA
Automated accessibility checkers
Automated accessibility checkers use WCAG accessibility standards to check your site’s code for accessibility issues, like missing alternative image descriptions, missing ARIA labels, or colour contrast issues.
Examples of these kinds of accessibility tools include Lighthouse, AxE, SiteImprove, Firefox Inspect, Microsoft Accessibility Insights, and many others. These tools are focused on code and technical compliance. They do not test for usability, inclusivity, or comprehensive screen reading capabilities.
Using automated accessibility checkers alone to improve your accessibility will not ensure a wonderful user experience. That’s why we developed the Essential Website Audit service.
Related:Screen readers ARIA Labels Alt tags WCAG 2.0 / WCAG 2.1 AODA ADA
CVAA (Communications and Video Accessibility Act)
CVAA or, The Twenty-First Century Communications and Video Accessibility Act, is American legislation passed in 2010 that governs the accessibility of video and other multimedia content, for online, television, and other distribution channels. For example, for TV shows that have aired on television, they are legally required to have captions when they are streamed online.
Related:WCAG 2.0 / WCAG 2.1 ADA Section 508
The term edge case is used to describe an atypical or less commonly encountered use case or user for a product or service. The traditional approach implies that the edge cases are more difficult to solve and serve fewer people and therefore are to be avoided. The long-held belief is that organizations can serve most of their addressable market without solving these tougher challenges.
As a result of this traditional approach, edge cases would often not be accommodated by a product or service, making it more difficult or even unusable in these cases.
For example, for a website, an edge case could be considered someone who would exclusively view the site in high contrast mode due to an uncommon vision impairment. However, this kind of consideration would be a common benefit for many users, not just those with a particular kind of vision impairment. Dismissing such a benefit because it may impact only a small percentage of users would be a detriment to the overall product and could require a significant effort to accommodate in the future.
As such, we know now that solving for the more difficult use cases first—particular when they lead to more ways to access content and engage with an organization—leads to much richer products or services that ultimately require less time and resources to capture market share.
Related:Inclusive design Product strategy Service design Universal design Usability Inclusive
The Equality Act (or EQA) is accessibility legislation passed in the United Kingdom in 2010. This legislation introduced much more comprehensive protections for people with disabilities and their rights when accessing digital products and services.
Most notably, it passed into law the requirement that websites in the United Kingdom must take reasonable steps to provide an equivalent online user experience for those with disabilities. It also makes it illegal to discriminate against those with disabilities in the United Kingdom, under which failure to provide accessibility accommodations is considered one form of discrimination.
Related:WCAG 2.0 / WCAG 2.1 AODA ADA Section 508
Form elements are any button, text box, checkbox or any other part of a form where a user can enter information. These elements need to be accessible not just by clicking or tapping them, but also by navigating to them with the keyboard.
If a certain form element must be responded to by the user, it needs to have an error state as well, where if the information required is invalid or not entered, a message is displayed and a symbol and colour change appears.
All pages on your website should use headings in the code to differentiate between the sections of content on the page. When coding a page, there should be one h1 (heading level 1) , and then h2s for each section within that. If a heading is needed in a section with an h2, an h3 should be used, and so on. If you skip heading levels, or omit headings entirely, you make it harder for users using screen readers to navigate though and jump between sections on the pages of your site.
Inclusive Design Research Centre (IDRC)
The Inclusive Design Research Centre, or IDRC, is a research organization based out of OCAD University in Toronto. Their work includes innovative research into accessibility, accessibility tools, inclusive design, and evolving and establishing inclusive design processes.
Founded by Jutta Treviranus (a professor at OCAD University) as the Adaptive Technology Resource Centre, IDRC has evolved to focus on inclusive design and a more holistic focus on inclusion in products, services, and spaces.
IDRC’s work spans user research, visual design, development, and user testing, for both new internal innovations and external partners, with a group of employees, volunteers, and advocates that come together to research and design inclusively. All are welcome to participate in this work through the Fluid Project Wiki.
Landmarks are snippets of code that—when placed in a web page—make it easier for screen readers to jump from section to section on the page. Pages are usually structured with a main landmark for the primary page content, a ‘Content Info’ landmark for footers, and a navigation landmark for the main menu items.
Additional complementary or region landmarks may be necessary if your site has sections on a page that aren’t part of the main content, or has an atypical way of structuring pages.
Screen readers describes software that allows users to listen to the content on a web page and navigate through a website without needing to view the visual content displayed on a screen. Some common examples are JAWS, NVDA, or VoiceOver.
Screen readers enable using a range of keyboard shortcuts or voice commands to allow users to jump from element to element on the page, take shortcuts to the content that matters most to them, and many other text reading and navigation options.
It’s important when you are developing a website to build in functionality like ARIA labels, landmarks, alt tags, and correct heading structures so that users of screen readers can access the content on your website as effectively as those who do not use screen readers.
Related:CVAA VoiceOver ARIA Labels Alt tags Landmarks WCAG 2.0 / WCAG 2.1 AODA ADA
Section 508 is American legislation that mandates all federal entities—and any private corporations that do business with federal agencies—make their digital platforms accessible to people with disabilities. This includes healthcare, legal, financial, and numerous other private sector organizations, in addition to public sector organizations.
Related:WCAG 2.0 / WCAG 2.1 AODA ADA
Transcripts are text-based versions of audio content that provide a word-for-word account of what is said in a video or audio file.
Transcripts allow people access to content even if they cannot or do not want to listen to audio. Transcripts are typically an accessibility requirement for improving access to audio or video content for people with hearing impairments, but they also serve many people who may be unable to turn on their volume, or may find it easier or faster to read rather than listen to audio.
When working with a video that has audio, it is best to use a service that provides a transcript as well as captions for the video.
VoiceOver is the built-in screen reading technology built into Apple’s operating systems, including macOS and iOS. VoiceOver allows users to have all of the written content in the operating system, app, or web browser read back to them.
This includes allowing users to navigate web pages and software through keyboard commands. VoiceOver also reads out alternative image descriptions, and indicates links and site headings, so that users know where they are in the page structure.
Related:Screen readers ARIA Labels Alt tags Landmarks WCAG 2.0 / WCAG 2.1
Web Content Accessibility Guidelines 2.0/2.1 (WCAG 2.0 / WCAG 2.1)
WCAG 2.0 / WCAG 2.1 represent the latest versions of the Web Content Accessibility Guidelines. These are the standards that the majority of national and sub-national (provincial, state, etc) legislation is based on, including ADA in the United States, and AODA in Ontario Canada.
WCAG standards include guidelines for content, code, and technical guidelines for how colour, interactivity, and more is handled on a website.
All organizations should be striving for a WCAG 2.0 AA rating for their website in order to meet general accessibility guidelines. A, AA, and AAA ratings define the measure of adherence to the standards presented by the WCAG guidelines.