Articles by Jesse Hausler
- How to Describe Complex Designs for Users with Disabilities
• Providing sufficient information about identity, operation and state of user interface elements is essential for accessibility. This helps assistive technologies. • Identity refers to what the user is interacting with. Operation refers to how the user uses it. State refers to its current status. • Native controls like form elements are the best option for accessibility as they identify themselves and their state. They are familiar to users. • For complex interactions, consider using native elements behind the scenes to provide identity, operation and state to assistive technologies. • Follow WAI-ARIA best practices for UI patterns not natively available in HTML. This helps provide proper accessibility. • If no native element or ARIA guideline exists, provide information using hidden text and live regions. But this should be a last resort. • Use aria-describedby to associate hidden text to provide identity. Update live regions to provide operation and state. • User testing is needed when providing identity, operation and state on your own. • Providing identity, operation and state information helps make experiences accessible for all users, including those with disabilities.
- 7 Things Every Designer Needs to Know about Accessibility
Jesse's has 7 tips covered include: 1. Accessibility is not a barrier to innovation: 2. Don't use color as the only visual means of conveying information 3. Ensure sufficient contrast between text and its background. 4. Provide visual focus indication for keyboard focus. 5. Be careful with forms. 6. Avoid component identity crises. 7. Don’t make people hover to find things.