@e-dream.ai - would love an invite ;-)
22.03.2025 13:41 โ ๐ 2 ๐ 0 ๐ฌ 1 ๐ 0@mmorba-a11y.bsky.social
@e-dream.ai - would love an invite ;-)
22.03.2025 13:41 โ ๐ 2 ๐ 0 ๐ฌ 1 ๐ 0@vale.rocks - check out www.zotero.org
31.12.2024 17:29 โ ๐ 1 ๐ 0 ๐ฌ 1 ๐ 0Why not aim for 4K?
31.12.2024 17:26 โ ๐ 1 ๐ 0 ๐ฌ 1 ๐ 0The picture has been made in 2018 at the "American Dream"-Tour of LCD Soundsystem in Luxembourg. Setlist: www.setlist.fm/setlist/lcd-...
31.12.2024 17:18 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0A 360 planet picture made during the gig of LCD Soundsystem in Luxembourg showing the crowd looking like a little ball with people standing on it allover, surrounded by the stage with the band and buildings flying in the sky.
Wish you all a great start into 2025.
31.12.2024 17:13 โ ๐ 2 ๐ 0 ๐ฌ 1 ๐ 0PS: still no one - not even the authors - have an exact idea of what this really means and how and what should be tested. I bet for high-contrast mode support is mandatory for web. Dark theme optional for apps/web. All is depending on the introduced local country laws and rulings.
31.12.2024 17:05 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0Yeahhh - my fav quote on this for 2025: EN 301 549 Section 11.7 User Preferences and as EU still only has unaccessible PDFยดs on this, thanks to Canada: accessible.canada.ca/en-301-549-a...
31.12.2024 16:58 โ ๐ 1 ๐ 0 ๐ฌ 1 ๐ 0... for the posts and replies.
31.12.2024 15:31 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0@bsky.app - my feature wish for 2025: an edit button
31.12.2024 15:30 โ ๐ 2 ๐ 0 ๐ฌ 1 ๐ 0Plus a lack of effective communication instead of time wasting meetings or slack/email-threads and most of all the missing responsibility definied with the PO name next to it.
31.12.2024 15:29 โ ๐ 1 ๐ 0 ๐ฌ 2 ๐ 0And as I guess you meant the "preventing" barriers for designers and developers: a lack of a11y awarness from product owners/top management, resulting in "we do that later" (= never ever) due to a feature driven culture, reeventing the wheel, constant refactoring things by UX & no time for testing.
31.12.2024 15:25 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0My favorite quote on this: "thereยดs never the time to do it right, but thereยดs always the budget to do it again"
31.12.2024 15:22 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0Besides the typical ones (lack of contrast, ALT, landmarks etc.), the ones I experience most often are missing keyboard support (= no screen reader support), wrong ARIA usage (#DIVsasters), combined with no visible focus indicator. Also bad UX in general: complex language (the biggest barrier) ...
31.12.2024 14:34 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0@techcrunch.com - how are the requirements for virtual tours regarding accessibility in 2025? From my point of view a virtual tour on an e-commerce/estate website needs to be accessible and WCAG compliant, e.g. offering keyboard only navigation, not mouse only.
31.12.2024 14:19 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0In case anyone is doing a research on #a11y of virtual tour and digitalTwin solutions/providers, please apply. Hey @matterport.bsky.social - how are you doing with e.g. keyboard access (please no DIV buttons)?
31.12.2024 14:10 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0... and for sure WIX is not the answer. The answer is always "depends".
31.12.2024 14:05 โ ๐ 1 ๐ 0 ๐ฌ 1 ๐ 0If I would need to choose between the mentioned I would go for Shopify. The major challenge in not locked down systems most often are the 3rd party plugins/themes/extensions/modules, which too often have not been developed with accessibility in mind. I hope for a search filter to exclude these ones.
31.12.2024 14:03 โ ๐ 1 ๐ 0 ๐ฌ 2 ๐ 0Then you just need to remove all the barriers first, which are preventing designers and developers from doing their jobs. This is the real challenge: inventing the right process to deliver high quality products.
31.12.2024 13:56 โ ๐ 1 ๐ 0 ๐ฌ 1 ๐ 0Better late than never. Nevertheless what really counts in the end is the markup in production e.g. in the userยดs browser or in the app. Therefore I hope 2025 will also be the year of accessible markup and code with less #DIVsasters than at the moment.
31.12.2024 13:53 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0Just a reminder regarding #Lighthouse from @matuzo.at : www.matuzo.at/blog/buildin...
24.12.2024 06:52 โ ๐ 4 ๐ 0 ๐ฌ 1 ๐ 0There is no best CMS. Also before using a CMS, have a look at the backend UI accessibility is recommended. The posted interpretations are very misleading. @mgifford.bsky.social - maybe there should be made an update or a more visible remark. The survey results did not cover any manual testing.
24.12.2024 06:51 โ ๐ 2 ๐ 0 ๐ฌ 1 ๐ 0If itยดs a link, itยดs not good if it looks like a button.
24.12.2024 06:44 โ ๐ 3 ๐ 0 ๐ฌ 0 ๐ 0If you think that it's clever to make radio buttons look like buttons because of accESsiBILiTY, let me tell you that it's not. It's confusing af for screen reader and keyboard users.
I've shared this post a hundred times but it explains the problem well.
tink.uk/perceived-af...
#AccessibleTooltips please.
24.12.2024 06:43 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0Check out the amazing posts from #HTMHell
24.12.2024 06:42 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0#1 rule of ARIA: no ARIA is better than BAD ARIA.
24.12.2024 06:39 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0Friends, I still get requests for #accessibility consultations. I'm not currently taking any consultation work, and I love to give recommendations for independent consultants when clients ask for them.
If you're an independent #a11y consultant, please reply below so I can add you to the list!