Category:Techniques
Subcategories
This category has the following 13 subcategories, out of 13 total.
Pages in category "Techniques"
The following 69 pages are in this category, out of 69 total.
A
- Allowing for Reflow
- Allowing for Spacing Override
- ARIA-edit: F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control
- ARIA-edit: F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link
- ARIA-edit: F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determined
F
- F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely
- F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order
- F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number
- Failure of 4.1.2 due to using Using Abstract Roles
P
T
U
- Unicode Character with an On-Screen Text Alternative
- Using a WAI-ARIA role to expose the role of a user interface component
- Using ARIA landmarks to bypass blocks of content, and provide programmatic structure.
- Using ARIA landmarks to identify regions of a page
- Using ARIA menus
- Using ARIA role of alert for Error Feedback in Forms
- Using ARIA role=dialog to implement a modal dialog box
- Using ARIA trees
- Using aria-activedescendant
- Using aria-activedescendant to allow changes in focus within widgets to be communicated to Assistive Technology
- Using aria-alertdialog to Identify Errors
- Using aria-describedby for link purpose
- Using aria-describedby for link purpose - May 2014
- Using aria-describedby to provide descriptions of images
- Using aria-expanded to indicate the state of a collapsible element
- Using aria-flowto
- Using aria-hidden="true" on Unicode characters that AT should ignore
- Using aria-hidden=true on an icon font that AT should ignore
- Using aria-label for 1.1.1
- Using aria-label for link purpose
- Using aria-label to provide an invisible label
- Using aria-label to provide an invisible label where a visible label cannot be used
- Using aria-label to provide labels for objects
- Using aria-labelledby for link purpose
- Using aria-labelledby to concatenate a label from several text nodes
- Using aria-labelledby to name regions and landmarks
- Using aria-labelledby to provide a name for user interface controls
- Using aria-labelledby to provide a text alternative for non-text content
- Using CSS Flexbox for Reflow
- Using grouping roles to identify related form controls
- Using role="heading" to identify headings
- Using role=heading to identify headings
- Using sufficient contrast for images that convey information
- Using the WAI-ARIA aria-expanded state to mark expandable and collapsible regions
- Using title for 1.1.1
- Using WAI-ARIA aria-checked=mixed
- Using WAI-ARIA range attributes for range widgets such as progressbar, scrollbar, slider, and spinbutton
- Using WAI-ARIA state and property attributes to expose the state of a user interface component
- Using WAI-ARIA states and properties to create a menu
- Using WAI-ARIA states and properties to create an interactive grid