@e-dream.ai - would love an invite ;-)

@vale.rocks - check out www.zotero.org

Why not aim for 4K?

The picture has been made in 2018 at the "American Dream"-Tour of LCD Soundsystem in Luxembourg. Setlist: www.setlist.fm/setlist/lcd-...

PS: 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.

Yeahhh - 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...

... for the posts and replies.

Plus 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.

And 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.

My favorite quote on this: "there´s never the time to do it right, but there´s always the budget to do it again"

Besides 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) ...

@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.

... and for sure WIX is not the answer. The answer is always "depends".

If 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.

Then 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.

Better 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.

Just a reminder regarding #Lighthouse from @matuzo.at : www.matuzo.at/blog/buildin...

There 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.