koena, to accessibility French
@koena@mastodon.social avatar

🎂 Happy birthday ! Il y a 25 ans le 5 mai 1999 est publiée la 1ère version des Web Content Guidelines, les normes internationales pour l' du . @w3c https://buff.ly/4bJDMdL

WebAxe, to accessibility
@WebAxe@a11y.info avatar

Is Swiping a Path-Based Gesture?
By James Edwards.
https://www.tpgi.com/is-swiping-a-path-based-gesture/

stvfrnzl, (edited ) to accessibility
@stvfrnzl@mastodon.online avatar

Question to , , & folks:

How do you feel about duplicate links in articles, blogs, whatever? Meaning: A certain word is a link (let's say "HEALTH") leading to an external website.

Would it annoy you if this word was always a link and it's mentioned for example 20 times in an article? Or would you rather have it only once to make it easier to scan for links?

Is there a related success criteria?

jscholes,
@jscholes@dragonscave.space avatar

@stvfrnzl Screen reader user. I'd prefer only the first instance to be unambiguously linked. If there are salient links sprinkled throughout the piece, maybe a collapsed "Featured in this Post" section or something at the end could collect them together in a single links list.

stvfrnzl,
@stvfrnzl@mastodon.online avatar

@jscholes thanks for sharing, appreciate it! ✨

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 https://andromedagalactic.com/blog/iframe-accessibility

stvfrnzl, to accessibility
@stvfrnzl@mastodon.online avatar

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

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

#accessibility #a11y #wcag #translation #disability #barrierefreiheit

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/

WebAxe, to accessibility
@WebAxe@a11y.info avatar

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

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

pkiff,
@pkiff@mastodon.social avatar

The new interface language options allow you to select which language to display the PAC (PDF Accessibility Checker) interface from this list:
English
Deutsch (German)
Français (French)
Español (Spanish)
Nederlands (Dutch)

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 ?

siblingpastry,
@siblingpastry@mastodon.world avatar
SteveFaulkner, to accessibility
@SteveFaulkner@mastodon.social avatar

AN SERVICE ANNOUNCEMENT from @patrick_h_lauke

patrick_h_lauke,
@patrick_h_lauke@mastodon.social avatar
yatil,
@yatil@yatil.social avatar
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

mandaris,
@mandaris@social.lol avatar

@SteveFaulkner I know you’re being serious, but i couldn’t help but think that only the sith talk in absolutes

SteveFaulkner,
@SteveFaulkner@mastodon.social avatar

@mandaris there is always room for other emotions. I had to look up your Sith reference, as I am not a Star Wars fan. 🖖🏼

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

patrick_h_lauke,
@patrick_h_lauke@mastodon.social avatar

what then follows is usually a long series of "bargaining" efforts to justify why the tooltip doesn't need to be keyboard-triggerable, or that it doesn't need to be hoverable with the mouse, or that it's ok that it also contains interactive controls inside it but doesn't receive logical focus, or... when in the end, the simplest answer is "just don't use a bloody tooltip and have the stuff there for all to see/use. at a stretch, use a disclosure widget"

ChasMusic,
@ChasMusic@ohai.social avatar

@patrick_h_lauke I haven't seen this, probably because the tooltips are hidden, which means to me they don't exist. But, ¿any examples?

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

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

yatil,
@yatil@yatil.social avatar

@SteveFaulkner @patrick_h_lauke And that doesn’t even address the fact that every user would have a different experience depending on how much they are willing to pay for “AI”. It’s a good fallback or a way to get more/specific/other information than what is in the alternative text from the image.

Maybe we should have term limits in W3C Working Groups ;-)

patrick_h_lauke,
@patrick_h_lauke@mastodon.social avatar
WebAxe, to accessibility
@WebAxe@a11y.info avatar
  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • rosin
  • mdbf
  • khanakhh
  • ethstaker
  • osvaldo12
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • InstantRegret
  • Youngstown
  • everett
  • slotface
  • kavyap
  • JUstTest
  • cubers
  • Durango
  • cisconetworking
  • tacticalgear
  • ngwrru68w68
  • modclub
  • GTA5RPClips
  • normalnudes
  • Leos
  • tester
  • provamag3
  • anitta
  • lostlight
  • All magazines