mrdowden, to accessibility
@mrdowden@mastodon.social avatar

Last week I published a blog post on the use of iframes and their impact on web accessibility. I hope you find this helpful and welcome feedback. https://andromedagalactic.com/blog/iframe-accessibility #accessibility #wcag https://andromedagalactic.com/blog/iframe-accessibility

stvfrnzl, to accessibility
@stvfrnzl@mastodon.online avatar

Gerade auf gesehen: http://wcag-auf-deutsch.de/

Danke an alle Beteiligten, das kann vielen Leuten helfen! 🙌

yatil, to accessibility
@yatil@yatil.social avatar

Happy 25 years of WCAG!

On this day in 1999, the Web Content Accessibility Guidelines 1.0 were published. WCAG 2.2 is still one of the most important standards on the web, ensuring a base level of access for everyone.

1.0 – May 5, 1999 https://www.w3.org/TR/WCAG10/
2.0 – Dec 11, 2008 https://www.w3.org/TR/WCAG20/
2.1 – Jun 5, 2018 https://www.w3.org/TR/WCAG21/
2.2 – Oct 5, 2023 https://www.w3.org/TR/WCAG22/

#wcag #a11y #accessibility

WebAxe, to accessibility
@WebAxe@a11y.info avatar

History of web accessibility / User Experience & Content / Gian Wild https://www.youtube.com/watch?v=itBP3FA-E70 #a11y #wcag

pkiff, to accessibility
@pkiff@mastodon.social avatar

New PAC (PDF Accessibility Checker) released on 18 April:

Version 2024.2 is a minor update with bug fixes and a handful of improvements including:

  • new interface language options
  • improved display on small screens
  • ability to double-click a summary check and jump to that section in detailed report

PAC is a free PDF accessibility checker for Windows that performs automated checks against many PDF/UA and some WCAG criteria.

[1] https://pac.pdf-accessibility.org/en/download

deconspray, to accessibility
@deconspray@mastodon.social avatar

Understanding and implementing the Web Accessibility Content Guidelines (WCAG) can be difficult for even trained experts. Catherine helps us with WCAG 2.2′s newest guideline by explaining the requirements and providing examples of how to improve our user interfaces.

https://buff.ly/3UbC65F

@WebDevelopment

kaveinthran,

@deconspray @WebDevelopment Do we have articles like this for every success criteria of ?

SteveFaulkner, to accessibility
@SteveFaulkner@mastodon.social avatar

AN #A11Y SERVICE ANNOUNCEMENT from @patrick_h_lauke

#WCAG

SteveFaulkner, to ai
@SteveFaulkner@mastodon.social avatar

Re: AI and the future of Web accessibility Guidelines
'Absolute statements such as “it will never work”, and “AI will be better than people at X” are not helpful to the conversation because it is very unlikely to be an absolute result in the end. Different contexts, different machine-learning approaches, and different data-sets will produce different results.'

https://lists.w3.org/Archives/Public/w3c-wai-gl/2024AprJun/0043.html

WebAxe, to accessibility
@WebAxe@a11y.info avatar
patrick_h_lauke, to accessibility
@patrick_h_lauke@mastodon.social avatar

approximately 73.2553% of issues i've seen recently come from "we decided to keep our UI nice and clean by hiding shit in a tooltip!", followed by the crushing realisation of what it means to have an accessible tooltip

SteveFaulkner, to accessibility
@SteveFaulkner@mastodon.social avatar

"when does it end?" asks @patrick_h_lauke

AI and the future of Web accessibility Guidelines

"Once you bring in the "AI will do it" line of thinking, we may as well
just remove any author requirement, and WCAG becomes just a list of
requirements for AI user agents to massage any old web content into
something accessible."

#a11y #WCAG #ai

https://lists.w3.org/Archives/Public/w3c-wai-gl/2024AprJun/0007.html

WebAxe, to accessibility
@WebAxe@a11y.info avatar
arnauddelafosse, to accessibility
@arnauddelafosse@mastodon.social avatar
mitelg, to random
@mitelg@phpc.social avatar

had an interesting discussion about AI in tech moderated by @kleinmann

now we are talking about and
important topic for everyone in the upcoming months

ppatel, (edited ) to accessibility
@ppatel@mstdn.social avatar

Are there freelance #accessibility people or those who have time to work on a possible audit? If you're a beginner in the field and haven't done this kind of work, let me know as well. I'm willing to mentor. Please DM.

#a11y #WCAG

patrick_h_lauke, to accessibility
@patrick_h_lauke@mastodon.social avatar

having a sudden clarity clarence moment today while reviewing one of my old WCAG pull requests... https://github.com/w3c/wcag/pull/1570#issuecomment-1987250364 #a11y #accessibility #wcag

BryceWrayTX, to webdev
@BryceWrayTX@fosstodon.org avatar

Post >> Contrast and change • Readability and accessibility — pick any one? Not really.

https://www.brycewray.com/posts/2024/03/contrast-change/

WebAxe, to accessibility
@WebAxe@a11y.info avatar

Future of accessibility guidelines, with Deque's Glenda and Wilco

https://www.youtube.com/watch?v=cfOifHbfJtw&t=55s

"With WCAG 3 still years away and no plans for WCAG 2.3, how can accessibility guidance keep up?"

#wcag #axecon #a11y

stvfrnzl, to Blog
@stvfrnzl@mastodon.online avatar

I published a short and sweet #blog post about three resources to help you understand the #WCAG (Web Content Accessibility Guidelines) better:

https://stevefrenzel.dev/posts/wcag-more-like-what/

Featuring #stark, @intopia & @yatil

#accessibility #a11y #html #css #JavaScript #WebDev #Frontend #InclusiveDesign #Disability

caztcha, to accessibility
@caztcha@fedibird.com avatar

The Japanese translation of WCAG 2.2 has just been released!

#wcag #a11y #accessibility

https://waic.jp/translations/WCAG22/

WebAxe, to accessibility
@WebAxe@a11y.info avatar
deconspray, to accessibility
@deconspray@mastodon.social avatar

Key highlights from the WebAIM Million 2023 report show that of the 1 million home pages tested, 96.3% of home pages had detected WCAG failures. We should be ashamed of ourselves.

https://uxdesign.cc/we-should-all-be-ashamed-of-the-web-webaims-2023-accessibility-report-5233c8583dd9

#Accessibility #A11y #WCAG

eric, to webdev
@eric@social.coop avatar
alan42, to accessibility
@alan42@mastodon.social avatar

So duplicate IDs (F77) no longer mean a WCAG fail as they refer to 4.1.1 (obsolete)?

I thought I had read duplicate IDs still fail, even though 411 is obsolete..?

#wcag #a11y

  • All
  • Subscribed
  • Moderated
  • Favorites
  • Leos
  • tsrsr
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • hgfsjryuu7
  • Youngstown
  • InstantRegret
  • slotface
  • khanakhh
  • rosin
  • ngwrru68w68
  • kavyap
  • PowerRangers
  • tester
  • tacticalgear
  • cubers
  • everett
  • vwfavf
  • ethstaker
  • osvaldo12
  • Durango
  • mdbf
  • cisconetworking
  • modclub
  • GTA5RPClips
  • normalnudes
  • anitta
  • All magazines