aardrian

aardrian, 4 hours ago to accessibility

I would be pissed with Google’s new fake search if I was WebAIM. It directly sources WebAIM (from an old survey), but it doesn’t link to the WebAIM survey results it cites. Instead it links to BoIA (an #AudioEye #overlay company) and Assistiv Labs.

The option to see web results is buried in the “More” kebab, and even then the link is third from last.

Reminder not to use Google to search (in case you still do).

#accessibility #a11y #AI

aardrian, 1 day ago to accessibility

I have been reading through the State of HTML 2023 results site (https://2023.stateofhtml.com/) and I am so disappointed in the overall #accessibility efforts — both in the questions and in the code.

This may become a blog post.

I filed 3 issues today, have filed 15 since late 2022, and only 2 have been addressed:
https://github.com/Devographics/Monorepo/issues/created_by/aardrian

But these surveys keep pushing problematic info in problematic UIs, giving the wrong impression of… everything.

#a11y #HTML

aardrian, 2 days ago to random

I’m tthinking the guy next to me on the plane does not approve of my mask since as soon as the wifi became available he loaded The Drudge Report on his phone and looked for stories about masks (the NC law being the first hit).

aardrian, 3 days ago to accessibility

With Chrome announcing support for UIA, it might be worth retesting some of your patterns with Narrator, Voice Access, Magnifier: https://developer.chrome.com/blog/windows-uia-support?hl=en

I didn't think UIA was quite mature, but I am also old enough to forget Windows’ prior but somehow also current #accessibility APIs. So I may simply be wrong.

#a11y

aardrian, 3 days ago to accessibility

Playing a little catch-up this week, so throwing this out sans context…

“Baseline Does Not Really Cover Baseline Support”
https://adrianroselli.com/2023/12/baseline-does-not-really-cover-baseline-support.html

Web Platform Baseline does not track browser support for #accessibility features built into the web platform. If you need to understand whether browsers support accessibility features as your own base level set of requirements, for legal or other compliance reasons, then Web Platform Baseline does not represent a baseline.

#a11y #HTML

aardrian, 4 days ago (edited 2 days ago) to random

I have been volunteered to run the “Practical and Complex Examples of ARIA Live” unconference session at #AccessU2024. So come by 116 at noon with your lunch and… unconference.

aardrian, 4 days ago (edited 4 days ago) to accessibility

Oh hey, it’s #GAAD.

Be on the lookout for the (mostly corporate) performative A11yship of #GAAD which is about to fill your timelines.

A couple years ago I demonstrated #overlay companies as the worst offenders:
https://adrianroselli.com/2022/05/the-performative-a11yship-of-gaad.html

#accessiBe #AudioEye #FACILiti #LevelAccess #UserWay #accessibility #a11y

aardrian, 4 days ago to random

Today at AccessU I weighed in on a group discussion and one of folks said they were surprised I wasn’t more cynical about the topic. Someone else in a separate chat commented how measured I was in my responses from what they expected. Another wondered why I wasn’t swearing.

I get the sense my online persona might be a lot gruffer than I am IRL. Might need to tweak one of those.

aardrian, 5 days ago (edited 2 days ago) to accessibility

I got name-checked in Jessica Weber’s 2024 #AccessU2024 Legal Update! It was for #AudioEye’s SLAPP #overlay suit.

Got to lunch very late because people wanted to ask me questions, but not in front of the AudioEye executive who was in the room.

https://knowbility.org/programs/accessu-2024/the-2024-accessu-legal-update

#accessibility #a11y

aardrian, 6 days ago to random

While sitting on the tarmac at Austin’s airport waiting for our gate to become available, I decided to find a public transportation option to get to downtown Austin. Google Maps suggested I walk to neighboring Travis County Correctional Complex and catch a bus from there. Only 4½ hours total.

aardrian, 7 days ago to accessibility

EFF “Podcast Episode: Building a Tactile Internet”
https://www.eff.org/deeplinks/2024/05/podcast-episode-building-tactile-internet
Featuring @ChanceyFleet

#accessibity #a11y

aardrian, 10 days ago to random

This is a big reason I find demands that users upgrade to the latest release to be unrealistic, and why companies need to support more versions than “latest minus one” or “current release minus 6 months” or whatever.

Reminds me of current problems with Sonos or Tandem.

https://mastodon.stickbear.me/@seedy/112412309443250570

aardrian, 10 days ago to random

I have heard anecdotally about the ongoing enshittification of Google’s Disability Support team responses. Which makes sense; Google got the PR credit on launch and, since it generates no direct revenue, seem to have let it languish.
https://dragonscave.space/@simon/112413244854931465

I just want multi-trillion dollar companies to honor their own commitments. Weird, right?

aardrian, 10 days ago to accessibility

I, for one, am curious how allowing tables (et al) in <option> is going to work when the issue discussing it is deferring #accessibility to another issue — in which none of them are participating.

WHATWG #10310: HTML parser changes for stylable <select>
https://github.com/whatwg/html/issues/10310

#a11y #html

aardrian, 10 days ago to accessibility

Looking for TalkBack bug confirmation before I file an issue. Test page:
https://cdpn.io/pen/debug/ExzxwxW

TalkBack does not expose the contents of the tabpanel in the first example (“Auto Tab Panel sans Interactive Child”). Looking for confirmation from another Chrome 124 / TalkBack 14.2 / Android user. Or prior experience.

#accessibility #a11y

aardrian, 10 days ago to accessibility

The Stack Overflow / OpenAI news does not alarm me too much. There is lots of bad #accessibility information there. I did a talk on it.

Twice:
• https://adrianroselli.com/2017/09/slides-from-a11ytoconf.html
• https://adrianroselli.com/2018/03/csun-2018-everything-i-know-about-accessibility-i-learned-from-stack-overflow.html

Essentially OpenAI is slurping more crap info so it can regurgitate more crap info. Which, frankly, is kind of its entire value proposition.

#a11y

aardrian, 10 days ago to random

Apparently IRC spam is still a thing?

aardrian, 12 days ago to accessibility

“Level-Setting Heading Levels”
https://adrianroselli.com/2024/05/level-setting-heading-levels.html

TL;DR: Avoid setting heading levels greater than six (6). This applies whether using aria-level or the proposed headingstart HTML attribute. Use HTML <h#> elements whenever possible.

#accessibility #a11y

aardrian, 11 days ago to accessibility

Thinking back to that time when WCAG 2.2 first went to review and French #overlay company #FACILiti, best known for its SLAPPs, asked to get a side-door added to WCAG for overlays:
https://www.w3.org/blog/2020/wcag22-wide-review/#comment-83070

#accessibility #a11y

aardrian, 12 days ago (edited 9 days ago) to random

“Digital Ocean” is a…

aardrian, 13 days ago to random

I only just found out Jack Dorsey left the board of Bluesky. Apparently deleted his account forever ago.

I’m not leaving Masto, but it’s good to know the problematic people are consolidating at Twitter.

aardrian, 13 days ago to random

“A Brief Note on Highlighted Text”
https://adrianroselli.com/2024/05/a-brief-note-on-highlighted-text.html

TL;DR: If you plan to style text highlighted by the browser, you must give it sufficient contrast — 3:1 for the highlight block against its background and (probably) 4.5:1 for the text within that highlighted block against that background.

aardrian, 16 days ago to random

It’s not wrong. But it’s not right, either.

“Creating Fluid Typography with the CSS clamp() Function”
https://www.sitepoint.com/fluid-typography-css-clamp-function/#:~:text=setting%2016px%20(or%20whatever%20value%20you%20want)%20as%20the%20root%20font%20size

It is, however, nice to see that my advocating for less broken fluid type approaches has paid off, even if the handwavy ‘accessibility’ explanations don’t point to my post that first raised them. It’s cool, it’s only my ego (and detailed explanations with examples).

aardrian, 17 days ago (edited 17 days ago) to accessibility

Irony.

It's unfortunate when good messages are undercut (while also validated in this case?) because the site hosting them uses an #accessibility #overlay. In this case, #UserWay by #LevelAccess.

Edited to add link to valuable article: https://www.c-q-l.org/resources/articles/many-disability-professionals-dont-understand-ableism/

aardrian, 18 days ago to accessibility

I think <seleclist> is dead? Not clear to me why, but I don’t have time to wade in.

But now Chrome is proposing allowing any element within <select> and I am… wary:
https://github.com/whatwg/html/issues/10310

I get that I don’t grok the work that goes into the UA rendering engine, but I am very worried about the #accessibility impact given it is not even addressed in the proposal.

Corrections to my assertions welcome.

#a11y #HTML