Level A Flashcards
2.4.1 bypass blocks
“2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.”
This guideline emphasizes the importance of providing users with a way to bypass or skip repetitive content that appears on multiple web pages. It aims to improve the efficiency and usability of websites for individuals who may navigate through content using assistive technologies such as screen readers or keyboard shortcuts.
By including a mechanism to bypass blocks of content, users can quickly navigate to the main content of a web page without having to listen or interact with repetitive elements such as navigation menus, sidebars, or header/footer sections. This is particularly beneficial for individuals who may rely on alternative methods of accessing content, as it reduces the time and effort required to reach the desired information.
Examples of bypass mechanisms include skip links or “jump to content” links that allow users to directly skip to the main content area of a web page. These mechanisms should be easily identifiable and operable, ensuring that users can bypass repetitive content efficiently.
By following this guideline, content creators can enhance the accessibility and usability of their websites, making it easier for individuals with visual or hearing impairments to navigate and consume web content.
2.4.2-page titled
The full text of guideline 2.4.2 is as follows:
“2.4.2 Page Titled: Web pages have titles that describe topic or purpose.”
This guideline emphasizes the importance of having descriptive and meaningful titles for web pages. The title of a web page is typically displayed in the browser’s title bar or tab and is also used by screen readers to provide users with an understanding of the page’s topic or purpose.
A clear and descriptive page title helps users, including those with disabilities, to quickly identify and navigate to the content they are looking for. It provides context and helps users understand what the page is about before they even start reading or interacting with the content.
When creating web page titles, it is important to use concise and descriptive language that accurately reflects the content or purpose of the page. Titles should be unique for each page, avoiding generic or repetitive titles that may confuse users. Additionally, titles should not rely solely on visual cues or images but should be accessible and understandable to all users, including those who rely on assistive technologies.
By following this guideline, content creators can improve the accessibility and usability of their websites, ensuring that users, including those with disabilities, can easily identify and navigate to the desired content based on the page titles presented.
2.4.4 Link purpose
“2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.”
This guideline emphasizes the importance of using descriptive link text that clearly indicates the purpose or destination of the link. Users, including those with disabilities, rely on the link text to understand where a link will take them and whether it is relevant to their needs or interests.
To meet this guideline, content creators should ensure that link text is meaningful and provides enough information to determine the purpose or destination of the link. Avoid using generic phrases such as “click here” or “read more,” as these do not provide sufficient context. Instead, use descriptive text that accurately represents the content or action associated with the link.
In some cases, the link text alone may not provide enough information, especially when the link is out of context. In such cases, additional context should be provided programmatically, such as through the use of aria-label attributes or title attributes, to clarify the purpose of the link.
It is important to note that the purpose of the link should be clear to users in general. Avoid relying on assumptions or knowledge that may not be universally understood. For example, using acronyms or abbreviations without providing an explanation or using vague phrases that may not be clear to all users should be avoided.
By following this guideline, content creators can improve the accessibility and usability of their websites, ensuring that users, including those with disabilities, can understand the purpose and destination of links based on the link text provided.
Multiple ways 2.4.5
Guideline 2.4.5 is another specific guideline in the Web Content Accessibility Guidelines (WCAG) 2.1. This guideline focuses on allowing users to navigate and locate content easily, particularly for individuals with visual, cognitive, or mobility impairments.
The full text of guideline 2.4.5 is as follows:
“2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.”
This guideline emphasizes the importance of providing users with multiple ways to navigate and access different web pages within a website. This is particularly beneficial for users who may have difficulty using traditional navigation methods or who prefer alternative navigation options.
To meet this guideline, content creators should ensure that users have different options to find and access web pages. This can be achieved by implementing various navigation features such as menus, search functionality, sitemaps, and breadcrumbs. By providing multiple navigation options, users can choose the method that works best for them and easily locate the content they need.
However, it’s important to note that this guideline does not apply in cases where a specific web page is part of a process or sequence. For example, in a multi-step checkout process, it may be necessary for users to follow a specific sequence of pages to complete a transaction.
By following this guideline, content creators can enhance the accessibility and usability of their websites by offering alternative navigation methods. This allows users, including those with disabilities, to navigate and locate content more easily, improving their overall browsing experience.
2.4.6- Headings and labels
“2.4.6 Headings and Labels: Headings and labels describe topic or purpose.”
This guideline emphasizes the importance of using clear and descriptive headings and labels to provide users with an understanding of the topic or purpose of different sections and elements within a webpage.
To meet this guideline, content creators should ensure that headings accurately describe the content that follows. Headings should be hierarchical, meaning they should be structured in a logical order, with main headings (such as H1) representing the most important content and subheadings (such as H2, H3, etc.) organizing the content into smaller sections. This helps users, including those using assistive technologies, to navigate and understand the structure of the webpage.
Labels are also important for form fields, buttons, and other interactive elements. They should clearly indicate what information is expected or what action will be performed when interacting with the element. This helps users, particularly those using assistive technologies, to understand the purpose of each form field or interactive element and provide the correct input.
By following this guideline, content creators can improve the accessibility and usability of their websites by providing clear and consistent headings and labels. This allows users, including those with disabilities, to navigate and understand the content more easily, enhancing their overall browsing experience.
2.4.7- focus visible
“2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.”
This guideline highlights the importance of ensuring that keyboard-operable user interfaces have a visible focus indicator. A focus indicator is a visual cue that indicates which element on a webpage currently has keyboard focus. It is crucial for users who navigate using a keyboard or other assistive technologies.
To meet this guideline, content creators should ensure that there is a clear and visible indication of keyboard focus for all interactive elements on a webpage. This can be achieved by using techniques such as changing the color, size, or style of the focused element, adding a border or outline, or providing a custom focus indicator. The focus indicator should be distinct enough from the surrounding elements to be easily noticeable.
By providing a visible focus indicator, content creators improve the accessibility and usability of their websites for users who rely on keyboard navigation. It helps them understand which element they are currently interacting with, reducing confusion and improving their ability to navigate and interact with the content.
It’s important to note that the focus indicator should not be hidden or made invisible, as this would make it difficult for keyboard users to determine their current location within the webpage.
By following this guideline, content creators can enhance the accessibility and usability of their websites by ensuring that keyboard-operable elements have a visible focus indicator. This allows users, including those with disabilities, to navigate and interact with the content more easily, improving their overall browsing experience.
2.2.2-pause,stop,hide
This guideline emphasize that for any moving, blinking or scrolling content that starts automatically or last more than five second the users get opportunity to stop,pause,hide. 
The main goal of this guideline is to ab
avoid distractions . Contant such as motion, pictures, animation‘s or video games, and the screen reader users can cause problems if it’s updating automatically .
2.3.1-Three Flashes or Below Threshold
This guidelines emphasizes that webpages do not contain anything that flash more than three times in one second. Because it can cause the epileptic seizures to the users so it is best practice to avoid the flashing Contant, totally and achieve the same functionality using other development techniques. 
2.5.1-Multiple gestures
2.5.1 Pointer Gestures - (Level A): All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. Example of multipoint or path-based gestures is drag and drop feature, zoom in and zoom out feature. These operations are very convenient to perform if you use mouse and as per this guideline these operations should be operable using keyboard as well. Single pointer is nothing but keyboard. As an example, we can take a look at https://www.google.com/maps and you can test it out whether all the functionalities are working using single pointer like keyboard.Who Benefits:● Users with limited motor abilities would benefit with single pointer actions● Users with li
Label in name-2.5.3
Label In Name - (Level A): For user interface components with labels that include text or images of text, the name contains the text that is presented visually. A best practice is to have the text of the label at the start of the name.Imagine you are using the voice control feature in iPhone or Windows recognition software to see how they work. When you are trying to activate a link “Sign in” which you visibly see, the speech input software, software is not able to activate the link.You might be wondering why and try to solve the mystery. The answer lies in the code where the visible link text says “Sign in” but the aria-label says “Log in”. Now, let us put ourselves in the shoes of those who use a speech input users and understand how it would be frustrating if the speech input program is not able to activate user interface controls just because the visible label and the accessible name do not match.This guideline intends to bridge the gap between the visible label and the accessible name so that people with disabilities who use visible label can use the same label programmatically.Who benefits:● Speech input users – They can activate the controls without any surprises● Text to Speech users (Text-to-speech (TTS) is a type of assistive technology that reads digital text aloud) – Converted text label and the visual label are the same that prevents confusion.This will be a great guideline to test in mobile device. We can also use screen reader to test this guideline if we don’t have the Speech input softwares. (Dragon Professional is most widely used speech input
3.1.1- Languages of page
Readable: Make text content readable and understandable.● 3.1.1 Language of Page - (Level A): The default human language of each Web page can be programmatically determined.This success criterion requires that each web page of a site has its default human language programmatically defined. This, according to the Internationalization best practices plays a critical role in determining the default text-processing language. Apart from this, this is a key factor for screen readers to switch to the correct reading language, load correct pronunciation rules of language variations. Traditional browsers can render the text correctly and visual browsers can load characters and scripts appropriately. Thus language of page helps people with disabilities understand content in a better way.Points to Check:● Ensure each page of your web site has lang attribute● Ensure the language code is correct● Use appropriate language tokens in terms of language variations like lang=en-us” for English in US and lang=”en-uk” for English in Britain.This is a mandatory guideline. Every single website should have lang attributes.
3.2.1- on focus
WCAG - Level A - ContinueGuideline 3.2 - Predictable: Make Web pages appear and operate in predictable ways.● 3.2.1 On Focus - (Level A): When any user interface component receives focus, it does not initiate a change of context.The intent of this guideline is to make sure that any unwanted actions are not initiated when focus moves on to an element. It will impact the visually aid users.Test to ensure:● Links don’t open new page or new window when focused with mouse or keyboard.● Forms don’t submit automatically.● There are no pop-ups or modal windows opening on page load or focusing on an element.● Focus should not move automatically to another element where it confused the users.This is a optional guideline.
2.5.3- label in name
This guidelines emphasize that for user interface components with labels that include text or images of text the name content the text that is present visually. it’s important to have the text of the label at the state a start of the name .suppose if you’re trying to activate a link sign in,but in aria label says “log in” speech input software cannot understand and can’t active the link . this guideline intends to bridge the gap between the visible level and accessible name so that people with disabilities who use visual level can use the same level programmatically.
2.5.1- pointer gestures
These guidelines says that all the functionality that uses multi point for operation can be operate with a single point . It means that all the things that is used by the mouse should have operable using keyboard as well. It will help the motor the disabilities people also who have the cognitive disabilities also who use the assistive technology such as screen reader , so any function, such as zoom in zoom out , swipe is also accessible through keyboard..
2.2.1- timing adjust
 This guideline focuses that for each time limit is set by the content in the website it should have mechanisms available to turn off, adjust and extend the available in the website this guideline will helpful for the cognitive and other disabilities people who needs enough time to read and interact content so that they don’t feel rushed or overwhelmed.
