Bhupesh Singh

This happens all the time in native mobile apps too.

iOS: Apply the .isHeader trait to heading text

Android: Give heading text the Heading role

Congratulations!

This also applies to mobile devices like phones and tablets. Yes, people use AT like keyboards with mobile devices too!

Donate to Fundraiser for Paula Johnson's Medical & Recovery Fund, organized by Todd Libby My name is Todd Libby, and I am starting this on the behalf of my… Todd Libby needs your support for Fundraiser for Paula Johnson's Medical & Recovery Fund

#TeamPaula shirts are now available to help offset the costs of future retests/surgeries for Paula. cottonbureau.com/p/SB3E9T/shi... You can also give/share the link here gofund.me/50744c9bf please. Proceeds go directly to the medical fund. Thanks for your support and Merry Christmas.

Safety & Deception: The Impact on Accessibility | Todd Libby | Magnolia Conf 2025 YouTube video by Magnolia Conf

My @magnolia.boo talk is up: youtu.be/P-P50Ztejfo?...

Hi Todd,
I follow the exact same process while testing the color contrast ratio of texts against the gradient background.

#A11y folks,
I have 1 query.
On applying text spacing bookmarklet, a dropdown coded with <select>, <option> remains unchanged. I’m unable to apply spacing adjustments. Is there an exception if code is not modified by author?
I can’t find anything that talks about exception of this kind in WCAG doc

Hi #A11y folks,
I'm reading about A11y support for Figma prototypes. Do anyone of you have experience in testing Figma prototypes. I'm curious to know how's the screen reader & keyboard support. Any issues or limitations you are facing while testing.
Any insights would be really helpful.
Thanks

Working on the Safety & Deception guidelines for WCAG 3 (still not finalized and far from that point) and I'm pondering including for review the og:image for a social media post and deceptive pattern (image isn't relative to article it supposedly belongs to) but have NO examples.

Deceptive pattern. A path intended to take a user along to something they may not want to do WITH intent. Coercion, deception, and manipulation.

Anti-pattern. Bad UX, bad design, or over-engineered solutions that create barriers.

Either way, they both are inaccessible solutions to UX challenges.

Celebrating with The Perfect Toast - TPGi In which Lloydi tries to come up with an approach to toasts (and not-toasts) to satisfy various annoyances and WCAG failures with this notification pattern.

I wrote something about toasts (and indeed not-toasts) on the TPGi blog. You may find something here useful. You might also find my sense of humour grating. Well, you pays your money* and you takes your choice.

www.tpgi.com/celebrating-...

[* No money required. It's all free!]

Just to clarify. It’s always beneficial to users to have a larger target size. So, we should aim to have a target size of at least 24 by 24 CSS pixels. Larger target sizes help users activate these controls easily. Thanks to James Edwards for the clarification.

If you have an undersized lone control with target size less than 24 by 24 CSS pixels & if it doesn't have any adjacent targets nearby but has sufficient spacing around it, then it will pass success criterion (SC) 2.5.8 Target Size. All thanks to the Spacing exception.
#accessibility

Was reminded of this historical artefact i penned/collated upon the release of #HTML5 back in 2014

#HTML @w3c.bsky.social #WebStandards

html5doctor.com/the-ride-to-5/

This has been a long time coming - but I'm glad to report that the vast majority of WCAG's Reflow Understanding document has been rewritten.

Lots of work and discussions in our attempt to make what Reflow actually requires more... well... understandable.
www.w3.org/WAI/WCAG22/U...

Back in 2003 when i was an #a11y babe in the woods I co-authored and presented a paper "Acc Testing Software Compared" with my then boss Andrew Arch (now of @intopia.bsky.social). What great strides the #accessibility #industry have made in the last 22 years

web.archive.org/web/20030720...

mind the WCAG automation gap

"Disclaimer: this content was partially produced via automation FTW! Don’t fear the AI future or the reaper."

#a11y #WCAG #testing #automation #ai

html5accessibility.com/stuff/2025/0...

Friday bookmarklet drop!

👉 a11y-tools.com/bookmarklets...

#devtools #frontend #tools

Let's chat about Android phones. Not your personal preference for a phone. I don't care (seriously I don't. Please don't tell me) but why it's important to give support to Android apps that's comparable to iOS when it comes to accessibility.
(1/4(

Listen to disabled people.
Believe disabled people.

Accessible notifications with ARIA Live Regions (Part 1) – The personal website of Sara Soueidan, inclusive design engineer

Friendly reminder that I shared *an extensive* guide to ARIA live regions so you can learn more about:
- what they are
- what to use them for
- how to use them
- what *not* to use them for (!important)

Part 1: www.sarasoueidan.com/blog/accessi...

Part 2: www.sarasoueidan.com/blog/accessi...

#a11y

Serial killer prompts for a valid CSS selector and then kills, or rather, removes them from the DOM.

Friday bookmarklet drop. This week I bring you SERIAL KILLER!

Enter a valid CSS selector to match elements in a page and watch them all disappear!

buff.ly/4ijMmmV

Obligatory tagfest: #devtools #bookmarklet #favelet #webdev

Panel added to screen reports viewport height and width and also zoom level. If page is zoomed, the panel itself is zoomed back to desired size so that it doesn't take over the screen.

It's Friiiiiiiiidaaaaaay! So here's another little bookmarklet for you.

Viewport Details
👉 https://buff.ly/4bbXpME

👁 FYI
#HTML #a11y articles by me
html5accessibility.com/stuff/

🖼️ #WCAG conforming methods for hiding decorative images:
<img alt>
<img alt="">
<img role="presentation|none"
<img aria-hidden="true">

#a11y #webDev #HTML

html5accessibility.com/stuff/2022/0...

Screenshot of the bookmarklet having just run, indicating links that have correctly identified that they will open in a new window, but also those that appear to have type of graphical errors in the warning, and those that are missing them entirely

Trump's a twat
Musk's a twit
Here's your Friday bookmarklet:

Check New Window Links: https://buff.ly/3Qgfyzp

1/3

screenshot of the Accessibility Worker section of HTMLZ displaying 12 shirts

Tough times for my fellow accessibility workers so I have cut prices on a range of shirts. Now only $US 12-14 (+VAT where applicable)

#a11y #accessibility #workers

www.etsy.com/uk/shop/HTML...

✊🏼Know your Standards - updated 07/02/2025

"Regularly people link to or quote from some outdated version of a specification. This can be confusing and detrimental to understanding, if the information is no longer correct or relevant."

#ARIA #a11y #HTML

html5accessibility.com/stuff/2020/1...

HTML Element test file index
Last updated 03 February 2025

#HTML #ARIA #WebDev #WebStandards

stevefaulkner.github.io/AT-browser-t...

Considerations for making a tree view component accessible A deep dive on the work that went into making the component that powers repository and pull request file trees.

I'm pretty proud of this tree view component I helped to make. I wrote about the nuance of what went into it in the hopes that it can serve as a reference for others. #a11y github.blog/engineering/...