13 Matching Annotations
  1. May 2021
    1. However, since we’re using tables purely for structural purposes, we need screen readers to ignore those tables. This is where ARIA roles can help us out. By applying the role="presentation" attribute to a table, we can instruct the screen reader to skip over those elements and move straight into the content.
  2. Oct 2020
  3. react-spectrum.adobe.com react-spectrum.adobe.com
    1. Sometimes you might need to use an element other than a native <button>. useButton supports this via the elementType prop. When used with an element other than a native button, useButton automatically applies the necessary ARIA roles and attributes to ensure that the element is exposed to assistive technology as a button.
  4. Sep 2020
  5. Nov 2019
    1. A mixed-state checkbox for React based on the WAI-ARIA Authoring Practices's tri-state checkbox.
    2. The current state is passed as the prop aria-checked, which can be either true, false or 'mixed'.
  6. Jul 2018
  7. May 2018
  8. Dec 2017
  9. May 2017
    1. WAI-ARIA provides Web authors with the following:

      This is a summary of the main types of additional information which may need to be added to a page to make it accessible, which can be done by adding ARIA attributes to elements.

    2. For example, with WAI-ARIA, developers can identify regions of pages and enable keyboard users to easily move among regions, rather than having to press Tab many times.
    3. For example, if the content of a Web page changes in response to user actions or time- or event-based updates, that new content may not be available to some people, such as people who are blind or people with cognitive disabilities who use a screen reader.