aardrian, 2 months ago (edited 2 months ago)

Page 319.

I am angered the #Overlay Community Group has its propaganda referenced in this document. And a bit angry at @w3c for allowing the CG to leverage the W3C brand

“[369] See W3C, Overlay Capabilities Inventory: Draft Community Group Report (Feb. 12, 2024), https://a11yedge.github.io/capabilities/ [https://perma.cc/2762-VJEV]; see also W3C, Draft Web Accessibility Evaluation Tools List, https://www.w3.org/WAI/ER/tools/ [https://perma.cc/Q4ME-Q3VW] (last visited Feb. 12, 2024).”

#accessibility #a11y

aardrian, 2 months ago

The #UserWay / #AudioEye CG has continually misrepresented its relationship with the W3C, which I have documented:
https://adrianroselli.com/2022/09/accessibility-at-the-edge-w3c-cg-is-an-overlay-smoke-screen.html

The CG head doesn’t seem to think there is anything wrong with this behavior. I am of the opinion this behavior violates the @w3c CG rules (on a plane so cannot look it up easily).

So now an #overlay BS document is referenced in a DoJ document.

Yeah, I may be angry.

aardrian, 2 months ago

I have updated three posts on my site with this info (mostly the same content, tweaked for each post):

• “#UserWay Will Get You Sued”
https://adrianroselli.com/2021/09/userway-will-get-you-sued.html#CGDoJ

• “ADA Web Site Compliance Still Not a Thing”
https://adrianroselli.com/2022/03/ada-web-site-compliance-still-not-a-thing.html#Update09

• “‘Accessibility at the Edge’ W3C CG Is an Overlay Smoke Screen”
https://adrianroselli.com/2022/09/accessibility-at-the-edge-w3c-cg-is-an-overlay-smoke-screen.html#Update05

Misrepresentation and misuse of the W3C brand and its employee / contractor relationships is the UserWay (now #LevelAccess) norm.

#overlay #accessibility #a11y

yatil, 2 months ago

@aardrian The “Capabilities” document also uses the W3C logo but does not indicate prominently that is a community group document which has no standards relevance. They do not use the ReSpec toolkit that should be used here.

I think this is a clear violation to the CG Guidelines how I remember them, and that the document is misattributed to W3C shows that this is highly misleading as it is. I hope @w3c and @wai can ensure that this is changed.

yatil, 2 months ago

@aardrian @w3c @wai I crated an issue: https://github.com/a11yedge/capabilities/issues/12

aardrian, 2 months ago

@yatil @w3c @wai Swell. Thanks!

w3c, 2 months ago

@aardrian @yatil @wai Thank you for bringing this to our attention. We're following up.