Frontend Dogma

“accessibility” Archive (3)

  1. A Quick Guide to Reviewing a VPAT ACR (by) · · , ,
  2. CSS-Only Widgets Are Inaccessible (by) · ·
  3. The “search” Element (by) · · ,
  4. What We’ve Learned About Designing for Accessibility From Our Users (by/via) · ·
  5. Accessible but Never Boring: Rebranding the Wise Design System for Everyone II (by/via) · · ,
  6. Certifications Should Be Hard (by) · · ,
  7. When Is “:focus-visible” Visible? (by) · · ,
  8. Visually Hidden Content Is a Hack That Needs to Be Resolved, Not Enshrined (by) · · , , ,
  9. Annotating Designs for Accessibility (by/via) · · ,
  10. How Screen Readers Read Special Characters: An Update (by/via) · · , , , ,
  11. Hijacking Screenreaders With CSS (by/via) · · , , , ,
  12. Foundations: Pointer Gestures (by/via) · ·
  13. Accessibility and Design Systems: The Deep-Dive Q&A (by+/via) · · ,
  14. Accessibility Beyond Code Compliance (by) · ·
  15. It’s About Time CAPTCHAs Become Accessible (via) · ·
  16. The H1 Conundrum: Understanding the Challenges of Heading Level One (by/via) · · , ,
  17. Fix Color Contrast—Web Accessibility for Text and UI Design (by) · · ,
  18. Making Calendars With Accessibility and Internationalization in Mind (by/via) · · ,
  19. Best Practices for Structuring Accessibility Testing (by/via) · · ,
  20. We Don’t Need “.visually-hidden” (by/via) · · , ,
  21. “content” Is Your Content? (by/via) · · , , ,
  22. My Ideal Accessible Components Resource Is Holistic, Well Tested and Easy to Use (by) · ·
  23. ARIA Live Regions for JavaScript Frameworks (by/via) · · , , ,
  24. 50.1% Empty Links (by) · · , , ,
  25. Are You Making These Five Mistakes When Writing Alt Text? (by/via) · · , ,
  26. Toolkit Tuesday: Using YouTube for Captions and Transcripts (via) · · , ,
  27. A Native “Visually Hidden” in CSS? Yes Please! (by/via) · · , , ,
  28. The WebAIM Strategic Accessibility Framework (via) · ·
  29. Accessible but Never Boring: Rebranding the Wise Design System for Everyone (by/via) · · ,
  30. The Web Needs a Native “.visually-hidden” (by) · ·
  31. A Beginner’s Guide to Manual Accessibility Testing (via) · · ,
  32. How People Read Online (by/via) · · , ,
  33. Without Accessibility, There Is No Privacy or Security (via) · · ,
  34. Conformance and Accessibility (by) · · ,
  35. A Guide to Accessible Form Validation (by/via) · · , , ,
  36. How to Style Your Alt Text (by) · · , ,
  37. Successful Teams Ensure 100% of Their Members Understand Keyboard Accessibility (via) ·
  38. How Shadow DOM and Accessibility Are in Conflict (by/via) · · ,
  39. The Importance of Adding Accessibility Design Reviews to the Design Process (by/via) · · ,
  40. Open Captions vs. Closed Captions: What’s the Difference? (via) · · ,
  41. Automatic Captions: Our Experiments and Best Practices (via) · · , ,
  42. Understanding the Cost of Not Being Accessible (by) · ·
  43. Not Everyone Uses a Computer in the Same Way That You Do (by/via) · ·
  44. ARIA vs. HTML (by) · · , , ,
  45. Keys to an Accessibility Mindset (by/via) · ·
  46. Ideas for Making Accessibility and Equity a Core Part of the Software Development Lifecycle (by) · · ,
  47. Avoid Spanning Table Headers (by) · · , ,
  48. A Step-by-Step Guide to Building Accessible Carousels (by/via) · · , , ,
  49. If You’re Going to Do a Job, Do It Properly (by) · ·
  50. Software Accessibility for Users With Attention Deficit Disorder (ADHD) (via) ·
  51. Buttons, Links, and Focus (by) · · , , ,
  52. Screen Readers Don’t Convey the Semantics of “strong” and “em” (by) · · , , , ,
  53. Scaling Accessibility Through Design Systems (by+/via) · · , ,
  54. A Practical Approach to Automated Accessibility (by) · · ,
  55. Automation Is Not the Enemy (by) · · ,
  56. Automated Testing Won’t Solve Web Accessibility (by) · · ,
  57. Foundations: Introduction to WAI-ARIA (by/via) · · ,
  58. The Troublesome Life and Lamentable Death of Success Criterion 4.1.1 · · , ,
  59. How to Build Accessible Main Navigation? (by/via) · · ,
  60. Focus Appearance Thoughts (by) · · ,
  61. Testing Colour Accessibility With Dev Tools (by/via) · · , , ,
  62. Non-Text Content Contrast Also Matters (by) · · ,
  63. WCAG 2.2 Update: It’s Time to Say Goodbye to the Parsing Criterion (by) · · ,
  64. External Links: In or Out (by/via) · · , ,
  65. Understanding Color and Accessibility (by) · ·
  66. Setting Expectations for Asking ChatGPT Web Accessibility Questions (by) · ·
  67. Léonie Watson on Accessibility (by+/via) · · ,
  68. New WCAG 2.2 Features Rated (by) · · ,
  69. Accessible Hamburger Buttons Without JavaScript · · ,
  70. Use the Dialog Element (Reasonably) (by) · · ,
  71. Musing Upon an “[alt]” Text Badge on Images (by) · · ,
  72. Are We There Yet? WCAG 2.2 Is at the Candidate Recommendation Stage Again (by/via) · · ,
  73. A Simple Custom (by) · · , ,
  74. If You Need a Link, Don’t Use a Button (by) · · , , ,
  75. Creating a Community That Values Accessibility (via) · ·
  76. Be a Digital Ally: Further Exploration of WCAG 2.2 (via) · · ,
  77. Web Accessibility Global Usage Survey · ·
  78. Comparing Level Access Automated Tools to Manual Accessibility Testing (by) · · , ,
  79. Comparing Manual and Free Automated WCAG Reviews (by) · · , ,
  80. Accessible Writing Is Just Good Writing (via) · ·
  81. Blind News Audiences Are Being Left Behind in the data Visualisation Revolution: Here’s How We Fix That (by/via) · ·
  82. Foundations: Visible Focus Styles (by/via) · · ,
  83. Manual Accessibility Testing (via) · ·
  84. The Main Areas of WAI-ARIA (by) · ·
  85. Closed Captions and Subtitles UX (by/via) · · ,
  86. 2023 Design Trends From an Accessibility Perspective (via) · · ,
  87. Stock Photos of People With Disabilities (by/via) · · ,
  88. A New Accessibility Strategy for the GOV.UK Design System (by+/via) · · ,
  89. JAWS, NVDA, and VoiceOver Braille Viewers (by) · · , , , , , ,
  90. WAI–Adapt Explainer (by+/via) ·
  91. Quick Thoughts on Typeface and Font Accessibility (by) · · ,
  92. Carry On Testing 2023 (by/via) · ·
  93. A Beginner’s Guide to Link and Text Accessibility (via) · · , ,
  94. Overlapping Interactive Areas (by) · ·
  95. User Stylesheets Are Still Pretty Great and Should Be More Widely Supported (by/via) · · ,
  96. What Is the Difference Between Alternative Text, Long Description, and Caption? (by) ·
  97. Aligning Jakob Nielsen’s 10 Usability Heuristics With the WCAG 2.1 (by) · · , ,
  98. Top 10 Accessibility News of 2022 (via) · ·
  99. Obscure CSS: Restoring Visibility (by) · ·
  100. An Inclusive and Planet-Friendly Digital Style Guide (by/via) · · , , ,
  101. The Intended Consequence of Inaccessible Digital Ads (by+/via) · · ,
  102. Quick Start for Evaluating and Testing Web Accessibility (by+/via) · · ,
  103. Building an Accessible Theme Picker With HTML, CSS, and JavaScript (by) · · , , ,
  104. Accessibility Convincing (by/via) · · , ,
  105. Useful Accessibility and Usability Examples to Help Improve Your Designs (via) · · ,
  106. Foundations: Target Sizes (by/via) · ·
  107. Bad Performance Is Bad Accessibility (by) · ·
  108. Prevent Focused Elements From Being Obscured by Sticky Headers (by/via) · · , ,
  109. 5 HTML Elements, and a Partridge in a Despair Tree · · ,
  110. How to Find and Fix the Top 3 Accessibility Issues (via) · · , ,
  111. Accessibility Starts With an Organisation’s Culture (by/via) · ·
  112. A Guide for Making Apps Accessible · ·
  113. Top 5 Accessibility Issues in 2022 (by/via) · ·
  114. State of A11Y (via) · ·
  115. Federal Web Accessibility Focus Has Private Sector on Notice (by/via) · ·
  116. Five Myths About Digital Accessibility (by) · · ,
  117. WCAG 3.0: Are We There Yet? (by/via) · · ,
  118. WCAG—Priority of Constituencies (by) · · ,
  119. Meaningful Labels Using ARIA—or Not (by) · · , ,
  120. W3C Publishes WCAG Testers Consistency List (by/via) · · ,
  121. Accessible Front-End Patterns for Responsive Tables (by/via) · · ,
  122. Accessibility: The Land That “Time to Interactive” Forgot (by/via) · · ,
  123. Reading the Meter (by) · · ,
  124. Swearing and Automatic Captions (by) · · ,
  125. Website Accessibility Is Not an Afterthought ·
  126. The 411 on 4.1.1 (by) · · ,
  127. Brief Note on Description List Support (by) · · , , ,
  128. Landmarks and Where to Put Them (by) · · , ,
  129. You Don’t Need ARIA for That (by) · · ,
  130. Accessibility and MVPs (by) · ·
  131. Which Images Need Descriptive Text? (by) · ·
  132. Making Microservices Accessible (by) · ·
  133. HTML Semantics and Accessibility Cheat Sheet (via) · · , ,
  134. Shadow DOM and Accessibility: The Trouble With ARIA (by) · · , , ,
  135. Making Accessibility Simpler in Higher Education and Beyond (by) · ·
  136. Addressing Concerns About CSS Speech (by) · ·
  137. Positioning Notification Messages With Accessibility in Mind (by) · ·
  138. Setting Up a Screen Reader Testing Environment on Your Computer (by) · · , , ,
  139. Preparing for WCAG 2.2 (by+/via) · · ,
  140. Accessibility and Inclusive Design Systems (by/via) · · , ,
  141. Page Title Conventions (by) · · ,
  142. The Value of Accessibility (by+/via) · · ,
  143. Incorporating Accessible Design Elements Into Your Web Site (by/via) · ·
  144. Analyzing the Top 100 Retailers for Digital Accessibility (via) · · ,
  145. A Guide to Keyboard Accessibility: JavaScript (by/via) · · , ,
  146. DOJ and Congressional Updates on Digital Accessibility (via) · ·
  147. Brief Note on “aria-readonly” Support (by) · · , , ,
  148. 5 Insider Tips to Make Accessibility Part of Workflow (by/via) · · ,
  149. Using Automated Test Results to Improve Accessibility (by+/via) · · ,
  150. Accessibility Is in Style—Styles and Style Guides (by/via) · · , , ,
  151. Significant Improvements for Screen Readers Now in Nightly Firefox (by/via) · · , , , ,
  152. A Guide to Keyboard Accessibility: HTML and CSS (by/via) · · , , ,
  153. Your Accessibility Claims Are Wrong, Unless… (by) · ·
  154. Don’t Disable the Zoom Functionality (by) ·
  155. The Anatomy of “visually-hidden” (by/via) · ·
  156. What’s New in WCAG 2.2 (by/via) · · , ,
  157. Are You Using an Accessibility Overlay to Help Disabled Users? Don’t! (by/via) · · ,
  158. Designing for People Who Use a Mouse (by/via) · ·
  159. Accessfuturism: Digital Accessibility in 2032 (by/via) · · ,
  160. Accessibility Contrast Requirements Explained and How to Fix 5 Common Low-Contrast Issues (via) · · ,
  161. Dialogs, Modality, and Popovers Seem Similar—How Are They Different? (by) · · , , ,
  162. What Designers Can Learn From Apple’s New Accessibility Features (via) · · ,
  163. Responsive Accessibility Using “visibility: hidden” (by) · ·
  164. Why You Need to Monitor and Report on Accessibility—All the Time (via) · · , ,
  165. A Simpler Approach to Document and Web Accessibility (via) ·
  166. 5 Takeaways From Screen Reader Usability Interviews (by) · · , ,
  167. Accessibility “Gaps” in MVPs (by) ·
  168. Caring About the World Wide Web (by/via) · · , ,
  169. Progress Over Perfection: A Better Way to Accessibility (by) · ·
  170. A Deep Dive Into Accessible Notifications (by/via) · · ,
  171. Why You Need to Involve Deaf and Hard of Hearing People in Research and Testing (by/via) · ·
  172. A Testing Strategy for Accessibility in New Apps (by) · ·
  173. 7 Tactics That Benefit Both Accessibility and SEO (via) · ·
  174. Next Steps for the W3C Web Accessibility Initiative (by/via) · · ,
  175. Complexity and Caution (by) · · ,
  176. “aria-label” Is a Code Smell (by) · · ,
  177. Do We Need an Interop for Assistive Technologies? (by) · · , , ,
  178. 5 Visual Treatments that Improve Accessibility (via) · ·
  179. Why You Should Never Use “px” to Set “font-size” in CSS (by) · ·
  180. Getting WCAG Color Contrast Right (by/via) · · , ,
  181. Accessibility Beyond the “Obvious” (by) ·
  182. Web Accessibility: ARIA 101 (by/via) · · ,
  183. Twitter Reminds Us About Alt Text, but How Good Are We at It? (by/via) · · , ,
  184. SEO and Accessibility Are Symbiotic (via) · ·
  185. How to Build the Foundation for Digital Accessibility (by/via) · · , ,
  186. Why We Need CSS Speech (by) · ·
  187. Digital Accessibility—Ask Me Anything (by+/via) · ·
  188. Google on Alt Text SEO and Accessibility (by+/via) · · , , ,
  189. Common ARIA Mistakes and How to Avoid Them (by) · · , ,
  190. Designing for Users With Disabilities: 10 Factors to Consider (via) · · ,
  191. New Brutalism and Web Accessibility: What You Need to Know (by/via) · ·
  192. Accessibility Checkers—a Good Start, Not a Solution (by/via) · · ,
  193. What I Learned About SVG Accessibility (Among Other Things) From NBC News’ Senate “What If” Project (by) · ·
  194. Some Things I Took Away From an Event Apart 2022 in Denver (by/via) · · ,
  195. Intro to Why Accessibility Is Important for Good SEO (via) · · ,
  196. Representation in “alt” Text (by) · · ,
  197. How to Write Good Alt Text (by) · · , ,
  198. WCAG 2.2 Success Criteria (by) · ·
  199. 4 Required Tests Before Shipping New Features (by) · ·
  200. Five Months Worth of Takes on the Digital Accessibility Space (by/via) · · ,
  201. When Going Somewhere Does a Thing: On Links and Buttons (by) · · , , ,
  202. Where Are the Accessibility Statements? Digital Accessibility Shouldn’t Be a Surprise (via) ·
  203. 3 Things to Consider Before You Implement CAPTCHA for Accessibility (via) · ·
  204. A Beginner’s Complete Guide to Form Accessibility: The 5 Things Accessible Forms Need and How to Fix Common Errors (via) · · ,
  205. Learn Accessibility (by/via) · ·
  206. Yes, Accessibility Is Also a Backend Concern (by) ·
  207. Intersectionality, Accessibility, and Inclusion (via) · · ,
  208. Websites Need to Be Accessible to Be Inclusive (by+/via) · ·
  209. A Deep Dive Into WCAG 2.2—and Beyond (by+/via) · · ,
  210. Accessibility (by+/via) · · ,
  211. A Designer’s Guide to Documenting Accessibility (by/via) · · , ,
  212. The Indisputable Truth About Accessibility (by/via) · ·
  213. Blind People Need to Be Considered More When Making Data Visualizations (by/via) · ·
  214. Attitudes to Digital Accessibility Survey 2022 (via) · · ,
  215. A “details” Element as a Burger Menu Is Not Accessible (by/via) · · ,
  216. It’s Good to Make Mistakes (by) · · ,
  217. Clarifying Color Contrast and Font Size Guidelines (by) · · , ,
  218. Accessibility Is Systemic (by) ·
  219. How to (Not) Make a Button (by) · · , , ,
  220. Brief Note on Super- and Subscript Text (by) · · , ,
  221. Accessibility Is for Every One (by) ·
  222. Buttons and the Baader–Meinhof Phenomenon (by) · ·
  223. Five Things You Can Do to Be More Inclusive (by) · ·
  224. Designing for People With Cognitive Disabilities and Everyone Else (by/via) · · ,
  225. Why the Number Input Is the Worst Input (by/via) · · , ,
  226. Accessibility in Times of Headless (by/via) · · ,
  227. On Better Browsers: Arbitrary Media Queries and Browser UIs (by) · · ,
  228. When Is It OK to Disable Text Selection? (by/via) · · ,
  229. The State of Digital Accessibility: Three Key Challenges (by/via) · · ,
  230. Making Sense of WAI-ARIA: A Comprehensive Guide (by/via) · · , ,
  231. Disability Is Not a Dirty Word (by) · ·
  232. Better Accessible Names (by) · ·
  233. Justin Yarbrough Talks About Alt Text (by/via) · · , ,
  234. The “details” and “summary” Elements, Again (by) · ·
  235. Are Modals in Web Design a UX Disaster? (via) · · , ,
  236. The Realities and Myths of Contrast and Color (via) · · , ,
  237. W3C Accessibility Maturity Model (by+/via) · ·
  238. HTML Markup Tips for Developing Accessible Websites (by/via) · · ,
  239. The Accessibility and Usability Journey of Drupal’s Primary Navigation (by/via) · · ,
  240. Focus Appearance Explained (by) · · , ,
  241. Comparing JAWS, NVDA, and VoiceOver (via) · · , , , , , , ,
  242. Don’t Overwrite Visual Labels With “aria-label” (by) · · ,
  243. Accessible Lists and Tables (via) · · ,
  244. Neutrality Isn’t an Option When It Comes to Accessibility (by) ·
  245. Small Steps: Celebrating Four Accessibility Wins (by/via) · ·
  246. An Argument Against CSS Opacity (via) · · , ,
  247. Communication Around Digital Accessibility Must Improve: How Users and Businesses Alike Are Failing to Advance Digital Accessibility (via) · ·
  248. What Is Closed Captioning? (by/via) · · ,
  249. Short Note on “figure” and “figcaption” (by) · ·
  250. Why Every University Needs an Accessible Standard Website Template (via) · · ,