Search results

Page title matches

• Category:Components
  3 members (0 subcategories, 0 files) - 21:50, 21 April 2018

Page text matches

• Category:WCAG 2. Operable
  User interface components and navigation must be operable.
  0 members (0 subcategories, 0 files) - 21:07, 29 July 2020
• Category:WCAG 1. Perceivable
  <blockquote>Information and user interface components must be presentable to users in ways they can  perceive.</blockquote>
  2 members (2 subcategories, 0 files) - 21:09, 29 July 2020
• Sliders
  [[Category: Components]]
  178 bytes (22 words) - 10:53, 24 May 2018
• Accordions
  ...s] by [[Scott O'Hara]] on his website. This covers not only how to use the components but also what the various screen readers and [[Accessibility Technology | a
  821 bytes (111 words) - 08:54, 13 April 2020
• Links vs Buttons
  ==What about links or buttons in larger components?== [[Category:Components]]
  5 KB (909 words) - 12:28, 2 April 2021
• Feedback Messaging
  ...egory can involve a number of different components – and can use different components at the same time.
  5 KB (793 words) - 15:32, 9 June 2021
• Category:Astronomy
  * [http://www.pbs.org/spacestation/station/components.htm Components of the Space Station] presumably the ISS.
  1 member (0 subcategories, 1 file) - 18:35, 4 August 2019
• Buttons
  [[Category: Components]] Buttons are components that allow users to navigate between states or actions. They're different t
  6 KB (930 words) - 13:43, 10 June 2022
• Category:Design
  == Design Containers and Components ==
  40 members (15 subcategories, 0 files) - 19:30, 19 August 2023
• Universal Design Principles
  * 7b. Make reach to all components comfortable for any seated or standing user.
  3 KB (455 words) - 16:22, 7 January 2021