|
You are here |
blog.danielna.com | ||
| | | | |
stephaniewalter.design
|
|
| | | | | A big list of resources, articles, blog posts, and checklists to help you, designers, get started on your "building more accessible products" journey. | |
| | | | |
raw.githack.com
|
|
| | | | | [AI summary] The provided text is a comprehensive draft of the Framework for Accessible Specification of Technologies (FAST), aimed at guiding web technology developers in creating accessible content. It outlines the need for web content to be perceivable, operable, understandable, and customizable for users with various disabilities. The document includes sections on user needs, functional needs, and ways to meet these needs through technology, author implementation, and user agent support. It also highlights the importance of color contrast, text alternatives, and user preferences in accessibility. The content is still in development and requires further refinement to align with the outlined user needs and meeting methods. | |
| | | | |
alistapart.com
|
|
| | | | | As an extension to our From URL to Interactive series, designer and front-end developer Melanie Richards takes a deep dive into how our content is accessed by a wide array of screen readers, which are highly customizable to users. Understanding the nuances of accessibility APIs, thorough testing approaches, and the wealth of resources available, site | |
| | | | |
www.24a11y.com
|
|
| | | Scott OHara returns, not with prose, but with a little history on the title attribute, its unintended misuse by developers, and where it can and should be used to improve the accessibility on your website. | ||