Frontend Dogma

“accessibility” Archive (3)

  1. Web and App ADA Lawsuits: 6 Trends So Far in 2023 (via) · · ,
  2. 4 Ways to Improve Mobile Accessibility (by) · ·
  3. Screen Magnification: Digital Accessibilitiy (via) · · , ,
  4. Top Tips From a Web Accessibility Evaluator at WebAIM (by/via) · · ,
  5. Magnification and Zoom Accessibility Guide—Everything You Need to Know (via) · · , ,
  6. Live Regions in React (by) · · , ,
  7. WCAG 2.2 Removes 4.1.1 Parsing and How axe-core Is Impacted (by/via) · · , ,
  8. Designing for Inclusion (by/via) · · ,
  9. Three Key Principles for an Accessible Website (by+/via) · ·
  10. Thoughts From “Meet Safari for Spatial Computing” (by) · · , , ,
  11. Continuous Accessibility (by) · · ,
  12. Can Web Developers Be Held Liable? (by/via) · ·
  13. The Five Types of People Who Produce Inaccessible Code (by) · ·
  14. 6 Quick Tests You Can Do to Test Your Forms for Accessibility (by) · · ,
  15. Design vs. Accessibility and the CSS “visually-hidden” Class (by/via) · · , ,
  16. You Can Stop Using “user-scalable=no” and “maximum-scale=1” in Viewport Meta Tags Now (by) · · , ,
  17. The Universal Focus State (by) · · ,
  18. Sticky Content: Focus in View (by/via) · · , ,
  19. No, “AI” Will Not Fix Accessibility (by) · ·
  20. Testing Sites and Apps With Blind Users: A Cheat Sheet (by+/via) · · , , , , ,
  21. Before Your Next Frontend Pull Request, Use This Checklist (by+/via) · · , , , , ,
  22. Assume the Position—a Labelling Story (by/via) · · ,
  23. Accessible Rich Internet Applications (WAI-ARIA) 1.2 (via) · · ,
  24. Accessibility and Artificial Intelligence (by) · ·
  25. Accessibility Testing—Pay Attention to the Details (via) · ·
  26. The Problem With Automatically Focusing the First Input and What to Do Instead (by) · · , ,
  27. WCAG 2.2 Misses Mark on Defining Visible Focus (by) · · , ,
  28. How We Created an Accessible, Scalable Color Palette · · , , ,
  29. Accessible Components: The Hamburger Menu · · ,
  30. Accessibility Audits for All (by) · · ,
  31. Don’t Meddle With User Input (by) · ·
  32. The Problem With Nested Fieldsets and How to Avoid Them (by) · · , ,
  33. How Screen-Reader Users Type on and Control Mobile Devices (by/via) · · , , , ,
  34. When to Use Plain Text or Images Instead of MathML (via) · · ,
  35. We Need to Talk About How We Talk About Accessibility (by+/via) · · ,
  36. Brief Note on Popovers With Dialogs (by) · · , , ,
  37. Levelling Up Accessibility Skills in Your Organisation (by+/via) · ·
  38. “display: contents” Considered Harmful (by) · ·
  39. Reading a Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR) (by/via) · · ,
  40. Addressing Timeout Modals: Navigating the Nuances for Inclusive Web Design (by/via) · · ,
  41. A Beginners Guide to Digital Accessibility (by) · ·
  42. What Devs Can Do on Global Accessibility Awareness Day (by) · ·
  43. Are We There Yet? WCAG 2.2 Is at the Candidate Recommendation [Stage] v3 (by/via) · · ,
  44. Accessible Numbers (by) · ·
  45. Why Is Web Accessibility Important? (by/via) · ·
  46. Semantics and the “popover” Attribute: What to Use When? (by) · · , ,
  47. Fieldsets, Legends, and Screen Readers Again (by/via) · · , , , ,
  48. Using HTML Landmark Roles to Improve Accessibility (by/via) · ·
  49. HTML Landmark Roles Screen Reader Demo (by/via) · · , , , ,
  50. The Problem With Disabled Buttons and What to Do Instead (by) · · ,
  51. Screen Readers Don’t Announce When the User Reaches the “maxlength” Character Limit (by/via) · · , , , ,
  52. Respect Your Children (by/via) · · ,
  53. ShatGPT (by) · ·
  54. React Testing Library and Accessibility (by) · · , , ,
  55. Digital Accessibility Is a Bigger Education Issue Than We Think—Here’s What We Can Do About It (by/via) · ·
  56. Why “font-size” Must Never Be in Pixels (by) · · , ,
  57. Short Note: Why Isn’t “role=presentation”/“none” Allowed on Focusable Elements? (by) · · , ,
  58. Progress Over Perfection: The Better Way for Communication and Accessibility Advocacy (by) · · , ,
  59. Accessible Target Sizes Cheatsheet (by/via) · ·
  60. The Potentially Dangerous Non-Accessibility of Cookie Notices (by/via) · · , , ,
  61. Meeting WCAG Level AAA (by/via) · · , ,
  62. Designing and Coding for Voice (by) · ·
  63. Visually Accessible Data Visualization (by/via) · ·
  64. Audio Accessibility in Miro: A Hackathon Story in 3 Acts (by/via) · · ,
  65. Answering “What ARIA Can I Use?” (by/via) · · , , , ,
  66. Web Accessibility: A Reference to Creating Inclusive Websites (via) ·
  67. Breaking Down Accessibility Barriers: Top 4 Challenges With Screen Magnifiers (by/via) · · ,
  68. Shifting Left, or: Making Accessibility Easier by Doing It Earlier (by) · · , ,
  69. HTML Accessibility API Mappings 1.0 (by+/via) · · ,
  70. Don’t Override Screen Reader Pronunciation (by) · · , , ,
  71. Accessibility in Design Systems: Building More Inclusive Products for a Better User Experience (via) · · , , ,
  72. Chasing Rainbows (by/via) · · , ,
  73. Establishing Metrics for Accessibility ROI (by) · · ,
  74. What’s New in WCAG 2.2? (by/via) · · ,
  75. The Alt Text War—SEO vs. Accessibility (by/via) · · , , ,
  76. Foundations: Accessible Names and Descriptions (by/via) · · , ,
  77. Designing for Reduced Motion (by/via) · ·
  78. What Makes a Good Screenshot? (by/via) · ·
  79. Five Pieces of Advice for More Accessible Websites (by) · ·
  80. Exposing Field Errors (by) · · , , ,
  81. Accessibility for Designers: Where Do I Start? (by) · · ,
  82. When I Get That Low Contrast Feeling, I Need Non-Textual Healing (by/via) · · ,
  83. 10 Ways to Hide Elements in CSS (by/via) · · ,
  84. We Need Accessibility Action (by) · ·
  85. The Ultimate Guide to Automatic Accessibility Testing in CI/CD for React Apps · · , , , ,
  86. Alternative Text in the Wild: 5 Alternative Text Examples (via) · · ,
  87. The WebAIM Million (via) · · , ,
  88. Guardrails for Better Accessibility Support in Frontend (by) · · ,
  89. Connecting Dots of an Accessibility Audit (by/via) · ·
  90. Accessibility vs. Emojis (via) · · , ,
  91. A Quick Guide to Reviewing a VPAT ACR (by) · · , ,
  92. CSS-Only Widgets Are Inaccessible (by) · ·
  93. The “search” Element (by) · · ,
  94. What We’ve Learned About Designing for Accessibility From Our Users (by/via) · ·
  95. Accessible but Never Boring: Rebranding the Wise Design System for Everyone II (by/via) · · ,
  96. Certifications Should Be Hard (by) · · ,
  97. When Is “:focus-visible” Visible? (by) · · ,
  98. Visually Hidden Content Is a Hack That Needs to Be Resolved, Not Enshrined (by) · · , , ,
  99. Annotating Designs for Accessibility (by/via) · · ,
  100. How Screen Readers Read Special Characters: An Update (by/via) · · , , , ,
  101. Hijacking Screenreaders With CSS (by/via) · · , , , ,
  102. Foundations: Pointer Gestures (by/via) · ·
  103. It’s About Time CAPTCHAs Become Accessible (via) · ·
  104. Accessibility Beyond Code Compliance (by) · ·
  105. Accessibility and Design Systems: The Deep-Dive Q&A (by+/via) · · ,
  106. The H1 Conundrum: Understanding the Challenges of Heading Level One (by/via) · · , ,
  107. Fix Color Contrast—Web Accessibility for Text and UI Design (by) · · ,
  108. Making Calendars With Accessibility and Internationalization in Mind (by/via) · · ,
  109. Best Practices for Structuring Accessibility Testing (by/via) · · ,
  110. We Don’t Need “.visually-hidden” (by/via) · · , ,
  111. “content” Is Your Content? (by/via) · · , , ,
  112. My Ideal Accessible Components Resource Is Holistic, Well Tested and Easy to Use (by) · ·
  113. ARIA Live Regions for JavaScript Frameworks (by/via) · · , , ,
  114. 50.1% Empty Links (by) · · , , ,
  115. Client-Side JavaScript and React Criticism: What Comes Next? (by) · · , , , ,
  116. Toolkit Tuesday: Using YouTube for Captions and Transcripts (via) · · , ,
  117. Are You Making These Five Mistakes When Writing Alt Text? (by/via) · · , ,
  118. The WebAIM Strategic Accessibility Framework (via) · ·
  119. The Web Needs a Native “.visually-hidden” (by) · ·
  120. Accessible but Never Boring: Rebranding the Wise Design System for Everyone (by/via) · · ,
  121. A Native “Visually Hidden” in CSS? Yes Please! (by/via) · · , , ,
  122. A Beginner’s Guide to Manual Accessibility Testing (via) · · ,
  123. Without Accessibility, There Is No Privacy or Security (via) · · ,
  124. How People Read Online (by/via) · · , ,
  125. Conformance and Accessibility (by) · · ,
  126. A Guide to Accessible Form Validation (by/via) · · , , ,
  127. How to Style Your Alt Text (by) · · , ,
  128. Successful Teams Ensure 100% of Their Members Understand Keyboard Accessibility (via) ·
  129. The Importance of Adding Accessibility Design Reviews to the Design Process (by/via) · · ,
  130. Open Captions vs. Closed Captions: What’s the Difference? (via) · · ,
  131. How Shadow DOM and Accessibility Are in Conflict (by/via) · · ,
  132. Automatic Captions: Our Experiments and Best Practices (via) · · , ,
  133. Understanding the Cost of Not Being Accessible (by) · ·
  134. Not Everyone Uses a Computer in the Same Way That You Do (by/via) · ·
  135. ARIA vs. HTML (by) · · , , ,
  136. Keys to an Accessibility Mindset (by/via) · ·
  137. Ideas for Making Accessibility and Equity a Core Part of the Software Development Lifecycle (by) · · ,
  138. Avoid Spanning Table Headers (by) · · , ,
  139. Software Accessibility for Users With Attention Deficit Disorder (ADHD) (via) ·
  140. If You’re Going to Do a Job, Do It Properly (by) · ·
  141. A Step-by-Step Guide to Building Accessible Carousels (by/via) · · , , ,
  142. Screen Readers Don’t Convey the Semantics of “strong” and “em” (by) · · , , , ,
  143. Scaling Accessibility Through Design Systems (by+/via) · · , ,
  144. Buttons, Links, and Focus (by) · · , , ,
  145. A Practical Approach to Automated Accessibility (by) · · ,
  146. Automation Is Not the Enemy (by) · · ,
  147. Automated Testing Won’t Solve Web Accessibility (by) · · ,
  148. Foundations: Introduction to WAI-ARIA (by/via) · · ,
  149. The Troublesome Life and Lamentable Death of Success Criterion 4.1.1 · · , ,
  150. Testing Colour Accessibility With Dev Tools (by/via) · · , , ,
  151. How to Build Accessible Main Navigation? (by/via) · · ,
  152. Focus Appearance Thoughts (by) · · ,
  153. Non-Text Content Contrast Also Matters (by) · · ,
  154. WCAG 2.2 Update: It’s Time to Say Goodbye to the Parsing Criterion (by) · · ,
  155. Understanding Color and Accessibility (by) · ·
  156. Setting Expectations for Asking ChatGPT Web Accessibility Questions (by) · ·
  157. External Links: In or Out (by/via) · · , ,
  158. Léonie Watson on Accessibility (by+/via) · · ,
  159. New WCAG 2.2 Features Rated (by) · · ,
  160. Accessible Hamburger Buttons Without JavaScript · · ,
  161. Use the Dialog Element (Reasonably) (by) · · ,
  162. Musing Upon an “[alt]” Text Badge on Images (by) · · ,
  163. Are We There Yet? WCAG 2.2 Is at the Candidate Recommendation Stage Again (by/via) · · ,
  164. A Simple Custom (by) · · , ,
  165. If You Need a Link, Don’t Use a Button (by) · · , , ,
  166. Creating a Community That Values Accessibility (via) · ·
  167. Be a Digital Ally: Further Exploration of WCAG 2.2 (via) · · ,
  168. Web Accessibility Global Usage Survey · ·
  169. Comparing Level Access Automated Tools to Manual Accessibility Testing (by) · · , ,
  170. Comparing Manual and Free Automated WCAG Reviews (by) · · , ,
  171. Accessible Writing Is Just Good Writing (via) · ·
  172. Blind News Audiences Are Being Left Behind in the data Visualisation Revolution: Here’s How We Fix That (by/via) · ·
  173. Foundations: Visible Focus Styles (by/via) · · ,
  174. Manual Accessibility Testing (via) · ·
  175. The Main Areas of WAI-ARIA (by) · ·
  176. Closed Captions and Subtitles UX (by/via) · · ,
  177. 2023 Design Trends From an Accessibility Perspective (via) · · ,
  178. Stock Photos of People With Disabilities (by/via) · · ,
  179. A New Accessibility Strategy for the GOV.UK Design System (by+/via) · · ,
  180. JAWS, NVDA, and VoiceOver Braille Viewers (by) · · , , , , , ,
  181. WAI–Adapt Explainer (by+/via) ·
  182. Quick Thoughts on Typeface and Font Accessibility (by) · · ,
  183. Carry On Testing 2023 (by/via) · ·
  184. A Beginner’s Guide to Link and Text Accessibility (via) · · , ,
  185. Overlapping Interactive Areas (by) · ·
  186. Fluid Typography: Predicting a Problem With Your User’s Zoom-In (by/via) · · , ,
  187. User Stylesheets Are Still Pretty Great and Should Be More Widely Supported (by/via) · · ,
  188. What Is the Difference Between Alternative Text, Long Description, and Caption? (by/via) ·
  189. Top 10 Accessibility News of 2022 (via) · ·
  190. Obscure CSS: Restoring Visibility (by) · ·
  191. An Inclusive and Planet-Friendly Digital Style Guide (by/via) · · , , , ,
  192. Aligning Jakob Nielsen’s 10 Usability Heuristics With the WCAG 2.1 (by) · · , ,
  193. The Intended Consequence of Inaccessible Digital Ads (by+/via) · · ,
  194. Quick Start for Evaluating and Testing Web Accessibility (by+/via) · · ,
  195. Building an Accessible Theme Picker With HTML, CSS, and JavaScript (by) · · , , ,
  196. Accessibility Convincing (by/via) · · , ,
  197. Useful Accessibility and Usability Examples to Help Improve Your Designs (via) · · ,
  198. Foundations: Target Sizes (by/via) · ·
  199. Bad Performance Is Bad Accessibility (by) · ·
  200. Prevent Focused Elements From Being Obscured by Sticky Headers (by/via) · · , ,
  201. How to Find and Fix the Top 3 Accessibility Issues (via) · · , ,
  202. 5 HTML Elements, and a Partridge in a Despair Tree (via) · · ,
  203. Accessibility Starts With an Organisation’s Culture (by/via) · ·
  204. A Guide for Making Apps Accessible · ·
  205. Top 5 Accessibility Issues in 2022 (by/via) · ·
  206. State of A11Y (via) · ·
  207. Federal Web Accessibility Focus Has Private Sector on Notice (by/via) · ·
  208. Accessible Front-End Patterns for Responsive Tables II (by/via) · · ,
  209. WCAG 3.0: Are We There Yet? (by/via) · · ,
  210. Five Myths About Digital Accessibility (by) · · ,
  211. WCAG—Priority of Constituencies (by) · · ,
  212. W3C Publishes WCAG Testers Consistency List (by/via) · · ,
  213. Meaningful Labels Using ARIA—or Not (by/via) · · , ,
  214. Accessible Front-End Patterns for Responsive Tables (by/via) · · ,
  215. Accessibility: The Land That “Time to Interactive” Forgot (by/via) · · ,
  216. Website Accessibility Is Not an Afterthought ·
  217. The 411 on 4.1.1 (by) · · ,
  218. Swearing and Automatic Captions (by) · · ,
  219. Reading the Meter (by/via) · · ,
  220. Brief Note on Description List Support (by) · · , , ,
  221. Landmarks and Where to Put Them (by/via) · · , ,
  222. You Don’t Need ARIA for That (by/via) · · ,
  223. Accessibility and MVPs (by) · ·
  224. Which Images Need Descriptive Text? (by) · ·
  225. Making Microservices Accessible (by) · ·
  226. HTML Semantics and Accessibility Cheat Sheet (via) · · , ,
  227. Shadow DOM and Accessibility: The Trouble With ARIA (by) · · , , ,
  228. Making Accessibility Simpler in Higher Education and Beyond (by) · ·
  229. Addressing Concerns About CSS Speech (by) · ·
  230. Positioning Notification Messages With Accessibility in Mind (by) · ·
  231. Setting Up a Screen Reader Testing Environment on Your Computer (by) · · , , ,
  232. Preparing for WCAG 2.2 (by+/via) · · ,
  233. Accessibility and Inclusive Design Systems (by/via) · · , ,
  234. The Value of Accessibility (by+/via) · · ,
  235. Page Title Conventions (by) · · ,
  236. Incorporating Accessible Design Elements Into Your Web Site (by/via) · ·
  237. DOJ and Congressional Updates on Digital Accessibility (via) · ·
  238. Analyzing the Top 100 Retailers for Digital Accessibility (via) · · ,
  239. A Guide to Keyboard Accessibility: JavaScript (by/via) · · , ,
  240. Brief Note on “aria-readonly” Support (by) · · , , ,
  241. Using Automated Test Results to Improve Accessibility (by+/via) · · ,
  242. Accessibility Is in Style—Styles and Style Guides (by/via) · · , , , ,
  243. 5 Insider Tips to Make Accessibility Part of Workflow (by/via) · · ,
  244. Significant Improvements for Screen Readers Now in Nightly Firefox (by/via) · · , , , ,
  245. Your Accessibility Claims Are Wrong, Unless… (by) · ·
  246. A Guide to Keyboard Accessibility: HTML and CSS (by/via) · · , , ,
  247. Don’t Disable the Zoom Functionality (by) · ·
  248. What’s New in WCAG 2.2 (by/via) · · , ,
  249. The Anatomy of “visually-hidden” (by/via) · ·
  250. Are You Using an Accessibility Overlay to Help Disabled Users? Don’t! (by/via) · · ,