Vince Aggrippino 🇺🇸🇲🇾

Web Development & Design Enthusiast

#CSS #JavaScript #HTML #Node #Python #React #Vue #Linux

Website: https://aggrippino.com
GitHub: https://github.com/VAggrippino
CodePen: https://codepen.io/VAggrippino

Last Notes

2025-03-30 07:13:24 UTC

- reply

It works without using any reset at all.
Are you sure you need it? User agent stylesheets are a lot more consistent across browsers now than they were before.
I don't use one.
#CSS

2024-09-23 06:26:24 UTC

- reply

I still see it too and it's been more than 2 weeks since your thread.
10k+ Downloads, 4.4 Stars
I live in Malaysia. Did they remove it just from the US market, or is that a total fail for the Play store to remove a fraudulent app?

2024-09-20 04:58:42 UTC

- reply

You can argue that screen readers *should* support that attribute and I might agree with you in a lot of cases, but it doesn't change the fact that they don't... on any platform.
I've also learned from many sources that the title attribute is at least useless and occasionally harmful to the user experience.
This isn't from my own head. People smarter than you and I put together have been harping on this topic for years.
I'm resisting the urge here to share a dozen links from disparate sources, but I will share one. The following shows a discussion which acknowledges that browser vendors aren't exposing the title accessibly. I'd say that contradicts the idea of it being a problem with screen readers.
https://www.w3.org/html/wg/wiki/ChangeProposals/notitlev2#New_information:_Browser_vendors_have_not_made_a_commitment_to_provide_.28input.29_device_independent_access_to_title_attribute_content

2024-09-20 04:45:23 UTC

- reply

I understand your argument, but I'm hesitant to agree because I also read this article by Adrian Roselli recently: https://adrianroselli.com/2021/10/blaming-screen-readers-red-flag.html

2024-09-20 04:38:14 UTC

I've heard about how the title attribute isn't helpful to users of assistive technologies.
But I thought <abbr> elements were different. After all, the title "provides a hint to user agents on how to announce/display the content while informing all users what the abbreviation means."... according to MDN.
It turns out that "all users", here, means sighted users who navigate with a mouse. If you navigate with a keyboard or even view the site on a mobile (touch) device, you're <abbr title="Shit Outta Luck">SOL</abbr>.
Screen readers don't read the title attribute on <abbr> elements. Keyboard and touch navigation don't have a hover event.
I found an article that suggests using the <dfn> element with the ::after pseudo-element's content property and the attr() CSS function. It doesn't solve the problem completely, but it is an improvement.
https://openinclusion.com/blog/presenting-abbreviations-acronyms-for-screen-reader-users/
#HTML #CSS #WebDev #WebDesign #a11y

2024-08-23 10:40:40 UTC

- reply

Well, you got a chuckle out of me 😅
I imagine the intersection between people who've seen the 40+ year old movies and people who are active on Mastodon is pretty small, though.
The books, of course, are timeless but it seems that the concerns of another legendary author, Ray Bradbury, have also come to fruition... Mass media has all but eliminated interest in books.