This checklist uses The Web Content Accessibility Guidelines (WCAG) as a reference point. The WCAG is a shared standard for web content accessibility for individuals, organizations, and governments. A: Essential If this isn’t met, assistive technology may not be able to read, understand, or fully operate the page or view. AA: Ideal Support Required for multiple government and public body websites. Organizations should strive for AA compliance. AAA: Specialized Support This is typically reserved for parts of websites and web apps that serve a specialized audience. This checklist ..read more

Easy to understand Information and the operation of a user interface must be understandable: Users must be able to understand the information as well as the operation of the user interface. Under this principle you will find guidelines relating but not limited to: Readable: Make text content readable and understandable. Predictable: Make Web pages appear and operate in predictable ways. Input Assistance: Help users avoid and correct mistakes. Let’s see how to apply the guidelines to our products 3.1. Make text easy to understand 3.1.1 Language of page  Identify the language that th ..read more

Easy to operate User interface components and navigation must be operable: The interface cannot require interaction that a user cannot perform. Under this principle you will find guidelines relating but not limited to: Keyboard Accessible: Make all functionality available from a keyboard. Enough Time: Provide users enough time to read and use content. Seizures and Physical Reactions: Do not design content in a way that is known to cause seizures or physical reactions. Navigable: Provide ways to help users navigate, find content, and determine where they are. Input Modalities: Make it eas ..read more

Easy to perceive Information and user interface components must be presentable to users in ways they can perceive: A website is perceivable when a user can use their sense(s) of sight, sound, and touch to identify and process the information presented. Under this principle you will find guidelines relating but not limited to: Using media content like video, audio and images Use of text alternatives through things like captioning and sign language The approach to the sequencing of content and layout The handling of color and contrast The control of text size and audio controls The handling con ..read more

Accessibility Conferences, Meet-ups and Webinars Accessibility conferences, meetup and webinars are a great way too deepen your accessibility knowledge and meet with other industry professionals. Some of these conferences, meetups and webinars also contribute for IAAP CAEC (Continuing Accessibility Education Credit) which help renew IAAP certifications like CPACC, WAS and ADS. Conferences Meet-Ups Webinars #a11yWeekTO#a11yTO actively promotes digital inclusion for the design and development communities in and around the Greater Toronto Area (GTA). We welcome people of all abilities and e ..read more

Table Of Contents Introduction Why are CAPTCHAs problematic? First analysis: CAPTCHAs and users Second analysis: CAPTCHA and security What are the alternatives to CAPTCHAs? Recommended solutions HoneyPot and Time measuring, two simple techniques to put in place to identify bots Anti-spam and blacklist solutions to remove bot requests A logical or mathematical test, also called textual CAPTCHA An email, SMS or phone verification for reinforced security Summary Related Articles Introduction A CAPTCHA (“Completely Automated Public Turing-test to tell Computers and Humans Apart”) is ..read more

Lang attribute makes sure that screen readers automatically use the correct speech libraries for accent and pronunciation. When listening, correct pronunciation helps understanding. For users of assistive technologies such as screen readers it is particularly important, as some have different speech synthesizers for different languages. For example, “chat” means something different when using English pronunciation rather than French. Lang BookmarkletLang Bookmarklet for Accessibility Testing The lang attribute bookmarklet will identify if there is lang attribute set to the page and language of ..read more

Landmark roles (or “landmarks”) programmatically identify sections of a page. Landmarks help assistive technology (AT) users orient themselves to a page and help them navigate easily to various sections of a page. They also provide an easy way for users of assistive technology to skip over blocks of content that are repeated on multiple pages and notify them of programmatic structure of a page. Landmark BookmarkletLandmarks Bookmarklet for Accessibility Testing Highlights all ARIA landmarks, including HTML5 tags that are interpreted as landmarks Landmarks Bookmarklet Code See the Pen Landmark ..read more

Aria-label is used to provide accessible name for the interactive elements, when aria-label or aria-labelledby is used extensively on a web page the aria-label bookmarklet will come in handy to check if the accessible name provided for the interactive elements is descriptive and sufficient. ARIA-Label Bookmarklet for Accessibility Testing If an element has an aria-label, it should get a yellow background and the label displayed in red. If an element has an aria-labelledby attribute, it should have a pink background and the object it is pointing to will be displayed in green. ARIA-Label Bookm ..read more

Easy to work with different Web browsers and Technologies Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies: As technologies and user agents evolve, the content should remain accessible. Under this principle you will find guidelines relating but not limited to: Maximize compatibility with current and future user agents by writing semantic HTML Use the W3C validator to validate code and identify errors Specify the purpose of non-standard user interface components using name, role and value  I ..read more