Description
Information and user interface components must be presentable to users in ways they can perceive.
Questions & Answers
How do I write instructions that don’t rely on sensory characteristics?
In web accessibility, what are sensory characteristics? How do I write instructions that don't rely on sensory characteristics?
- sensory characteristics
- user experience
Should inputs and buttons have the same focus state?
Should text input text focus state be the same as buttons keyboard focus state?
- buttons
- color contrast
- focus
- text input
How do I know whether an image of text is decorative?
Success Criterion 1.4.9: Images of Text (No Exception) states that text “used for pure decoration” is one of the few allowed uses for images of text. How do I know whether text is decorative?
- decorative images
- images
- text
Can I hide content while maintaining web accessibility?
How can I hide content while still maintaining web accessibility?
- aria
- CSS
- hidden content
How do I make my podcast accessible?
How do I make my podcast accessible to people with disabilities?
- audio
- audio controls
How do I prevent user errors on my website?
How do I prevent user errors on my website?
- errors
- forms
- labels
- user experience
What is ARIA?
What is ARIA? I know it's related to web accessibility, but what does it do?
- aria
- aria attributes
Is it okay to have multiple navigation landmarks?
I'm building some new pages and am not sure if it is okay to have multiple navigation landmarks?
- landmarks
- navigation
Are running headers in a PDF accessible?
My question is about a pdf. Should a running header be read by a screen reader? If it should be read, should the screen reader describe it as a running header? Or is reading it as is ok?
- running header
How do autocomplete attributes affect web accessibility?
How do autocomplete attributes in a form affect web accessibility?
- autocomplete
- form
- form fields