@inautilo.bsky.social#Development #Proposals
The web needs interactive lists · A UI pattern native platforms already provide ilo.im/16guig by Sarah Higley
_____
#Lists #Navigations #Interactivity #Accessibility #ScreenReaders #ARIA #WebApps #WebDev #Frontend #HTML
@frontenddogma.comScreen Reader User Survey #11 Results, by @[email protected]:
https://webaim.org/projects/screenreadersurvey11/?ref=frontenddogma.com
@deconspray.bsky.socialWebAIM’s latest survey challenges us: 83.9% say better websites matter more than better assistive tech. Are we building accordingly?
#Accessibility #A11y #ScreenReaders #InclusiveDesign #WCAG #DigitalAccessibility
@marketingnews.bsky.socialExplaining alt text #AltText #WebAccessibility #DigitalMarketing #SEO #ScreenReaders
@ppc.landExplaining alt text #AltText #WebAccessibility #DigitalMarketing #SEO #ScreenReaders
@deconspray.bsky.socialWCAG has skip links. But what about 500 lines of code? Neil Osman asks whether screen reader users need a bypass mechanism WCAG doesn't address.
#Accessibility #DigitalAccessibility #ScreenReaders #A11y #WCAG #WebAccessibility #InclusiveDesign
@inautilo.bsky.social#Development #Findings
Screen Reader User Survey #11 · What 1,780 users say about their screen reader habits ilo.im/16e7xl by WebAIM
_____
#Business #Accessibility #ScreenReaders #Content #Devices #Browser #Design #WebDesign #WebDev #Frontend
@deconspray.bsky.socialThink <figcaption> makes your video accessible? Think again. Schalk Neethling examines what assistive tech actually gets.
#Accessibility #WebAccessibility #A11y #HTML #WCAG #ScreenReaders #InclusiveDesign
@deconspray.bsky.socialIf a status update happens and a screen reader user never knows, did it really happen? Nat Tarnoff explores WCAG 4.1.3.
#Accessibility #A11y #WCAG #WCAG413 #DigitalAccessibility #ScreenReaders #InclusiveDesign #WebAccessibility
@frontenddogma.comDo Screen Readers Actually Read the Screen?, by @russmaxdesign.bsky.social:
https://www.maxdesign.com.au/articles/do-screen-readers-read-screen.html?ref=frontenddogma.com
@deconspray.bsky.socialScreen readers don't read pixels. They interpret what our code exposes. Accessibility starts with semantics, not appearance.
#Accessibility #A11y #ScreenReaders #WebAccessibility #InclusiveDesign #WCAG #DigitalAccessibility #AssistiveTechnology
@mspk-97.bsky.socialStruggling with screen readers ignoring your Shadow DOM components? Learn how the accessibility tree works and practical fixes like delegatesFocus and ARIA roles to bridge the gap. Make your web components truly accessible. #Accessibility #ShadowDOM #WebComponents #ScreenReaders https://blog.mspk.me
@deconspray.bsky.socialEven experienced devs make a11y mistakes. Jake Archibald shows why accessible names, ARIA semantics, and testing with multiple screen readers matter.
#Accessibility #A11y #WebAccessibility #ARIA #ScreenReaders #InclusiveDesign #WebDevelopment
@deconspray.bsky.socialA site can pass an automated scan and still fail its users. Accessibility isn't one-size-fits-all. Are you testing accessibility, or assumptions?
#Accessibility #DigitalAccessibility #A11y #WCAG #WebAccessibility #InclusiveDesign #ScreenReaders
@deconspray.bsky.socialdisplay:none ≠ aria-hidden=true. They hide content in fundamentally different ways. Knowing why is essential to accessible UI.
#Accessibility #A11y #ARIA #ScreenReaders #WebDevelopment #WCAG #InclusiveDesign #DigitalAccessibility
@deconspray.bsky.socialVisible ≠ announced. ARIA live regions can bridge the gap, but should we announce everything? Sara Soueidan explores the answer.
#Accessibility #DigitalAccessibility #A11y #ARIA #WebAccessibility #WCAG #ScreenReaders #UX #WebDevelopment