ashleemboyer.com
Deaf, ND, multiply disabled. W3C Invited Expert participating in WCAG 3. Software eng. & consultant: @ashlee.semanticfish.com Blog: ashleemboyer.com More writing: @semanticfish.net Interests: crip theory & critical access/disability studies.
👤 Joined on 24 April 2023
Followers
Following
Total Posts
@ashleemboyer.bsky.social@ashleemboyer.bsky.social → @ashleemboyer.compremarcu.bsky.social
nyxfluffpaw.bsky.social
fyradating.bsky.social
Not Found
antiantiai.bsky.social
segyges.bsky.social
amoveablefeed.bsky.social
neilhimself-nail.bsky.social
neilhimself.neilgaiman.com
sneakyness.com
i-like-to-moob-it.bsky.social
coachchron.com
attie.ai
altnps.bsky.social
Not Found
psychopropane.bsky.social
Not Found
kancin.bsky.social
imlunahey.com
veblendirectors.bsky.social
Not Found
Not Found
Not Found
Not Found
kamabla.bsky.social
More like email is running from me
Show PostThe email will not find me today or tomorrow.
Show Post… Never mind missing the bugs, features, heuristics, and more built into a DOM parser and screen reader engine. Unless your goal is satisfy a dashboard while removing humans from your #accessibility testing. #a11y #ScreenReader
Show Post“Accessibility-first screen reader prediction” is not a solution, folks. Parsing a DOM and building your _own_ accTree to then *emulate* how desktop screen readers _might_ announce a page as if *maybe* using read-all just ends up putting more burden on human testers. …
Show Post