Posts by cwilcox808@c.im
(DIR) Post #ASN4DRMRdkuBfkE1C4 by cwilcox808@c.im
2023-02-05T13:47:10Z
0 likes, 0 repeats
@frank alt text is for people, people should write alt text.When people fail to write alt text, VoiceOver's Recognition feature can attempt to describe the image contents. If it's an image of only text in an ordinary typeface, it has a decent chance of getting it right. At describing graphics, it might be better than nothing. Maybe. It will be worse than a person's attempt.
(DIR) Post #ASNu539iwhhrtvaya8 by cwilcox808@c.im
2023-02-05T23:28:19Z
0 likes, 0 repeats
@frank if you have a Microsoft 365 subscription, you could try inserting an image in a Word doc first. I know desktop versions have an alt text suggestion feature, I'd expect the mobile version to also.
(DIR) Post #ASapBwjxM5UDRWNksC by cwilcox808@c.im
2023-02-12T05:02:38Z
0 likes, 1 repeats
@simon @eric For that specific example, what you've described should be a button, not a link. To ensure a screen reader user knows clicking it did something, either add a message in an ARIA live region or move focus to an element at the beginning of the added content (don't do both). I don't have a good suggestion for how to choose which approach to use. I lean toward moving focus, which has the benefit of making the result apparent to a high magnification user.
(DIR) Post #ASg0CGdvQaasSLiTq4 by cwilcox808@c.im
2023-02-14T16:59:33Z
0 likes, 0 repeats
@simon @eric I should amend my original statement because *sometimes* the control is better as a link, rather than a button. If the block of HTML being fetched is basically a whole page being client-side routed to, especially if the address bar is updated, a link would better convey that clicking it will "go somewhere" vs. "do something."If the control is a link, moving focus is likely to be better than announcing the change, as it's closer to the HTML-native experience. Here's good research about client-side routing:https://www.gatsbyjs.com/blog/2019-07-11-user-testing-accessible-client-routing/I was originally thinking more about smaller use-cases, like applying filter parameters or pagination within a smaller component on a page.As is often the case, "it depends."
(DIR) Post #AXpBuzGm7Ct0GQaAr2 by cwilcox808@c.im
2023-07-18T16:45:47Z
0 likes, 0 repeats
@lowqualityfacts There you go, all the proof you need. Congratulations!
(DIR) Post #AY1OYQJK6vR9psAY4G by cwilcox808@c.im
2023-07-24T14:04:00Z
0 likes, 0 repeats
@bortzmeyer Most domain registrars offer the same kind of privacy protection, it's commonly used and isn't a problem.
(DIR) Post #AY1R8QsPgRnPvMse0G by cwilcox808@c.im
2023-07-24T14:32:54Z
0 likes, 0 repeats
@bortzmeyer The WHOIS directory is public, that's all there is. Any registrar has private business records of domain registrations to reference in the case of a dispute. You *are* expected to keep your contact information current with your registrar and ICANN requires registrars to send reminders every year to domain owners.Based on the link you shared, it appears Namecheap is the actual registrar, Bluesky is just a reseller. Namecheap itself also offers to keep your contact information private. Again, this is common and not risky for domain owners.https://www.namecheap.com/security/domain-privacy-service/
(DIR) Post #Ajj039t4OkWly2au7k by cwilcox808@c.im
2024-07-08T15:29:17Z
0 likes, 0 repeats
@aral @boldewyn Nesting is really nice for media queries and it's good to keep `prefers-reduced-motion` in mind when adding animations or transitions.Not all changes over time are "motion." Altering the text color does not create the illusion of movement. Transitions of `translate` or `scale` are examples of ones that benefit from being in a `prefers-reduced-motion` media query.https://www.w3.org/WAI/WCAG22/Understanding/animation-from-interactions#dfn-motion-animation
(DIR) Post #An41tVv405HM31H9Zw by cwilcox808@c.im
2024-10-16T12:17:59Z
0 likes, 0 repeats
@michelle <q> does a few things:It localizes the marks, it will use the marks that fit the `lang` set on a parent element. Add `lang="fr"` to see how the appearance of <q> changes.It automatically makes quotation marks "curly" instead of straight. Your article appears to have curly quotes in the text but my guess is something did that formatting for you, you didn't use an arcane key combination to type open quote, close quote characters. <q> uses pseudo-elements to add the right characters.Because the curly quote characters aren't a part of the text, they don't get mangled by encoding mismatches (e.g. Unicode vs. Latin-1).In languages that use them, it automatically alternates between double quote (") and single quote (') marks for nested quotations; outermost is double, next quote in is single, then inside that is double, and so on.
(DIR) Post #An41tZMpBKGejzHrlY by cwilcox808@c.im
2024-10-16T12:22:37Z
0 likes, 0 repeats
@michelle A downside to <q> is because it makes the marks a form of styling, instead of a part of the text, the marks don't survive copying and pasting into plaintext.It's also more cumbersome to type out open and close HTML tags vs. pressing Shift+' on a (English) keyboard.
(DIR) Post #AyoAwHueCufPnfDKC0 by cwilcox808@c.im
2025-10-02T18:15:19Z
0 likes, 0 repeats
@zeldman I'm not going to click that link, I don't think my device has enough RAM. 😔