Add new failure technique for non-semantic ruby annotation#4829
Add new failure technique for non-semantic ruby annotation#4829
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@adampage, love this failing technique! I would also suggest adding a reference to 1.3.2 (at the top as well as describing it in description/examples), because expecially in example 3, the meaning changes when the text is read in sequence. |
Oh yes, excellent, I’ll add that. Thanks, @giacomo-petri. 🙏🏻 |
|
Hi @kfranqueiro, I temporarily authored this one as F999.html and used that for the assorted file references. Is there a right way for me to choose/reserve a new failure number? |
…ang]` element (#4852) In #4829, cspell gave me [“unknown word” failures for “_tou_” and “_shi_”](https://github.com/w3c/wcag/actions/runs/20857561983), so I resolved them by [adding a file-specific override](https://github.com/w3c/wcag/pull/4829/files#diff-911db262cf96b6fa444f9cf0fc8fe00952325cda6b66c53952ea15d552ef42adR58-R59). A little further down in `cspell.yml`, I noticed a regex for ignoring any elements with the `lang` attribute — which is exactly where my unknown words had occurred in #4829. However, my `lang` content contained multiple lines, whereas the regex seems to be looking for single line matches.
|
There isn't really a way to "reserve" per se - they're primarily first-come first-serve. We used to wait until the last minute and use temporary slug filenames until we were ready to merge, but more recently we resolved to take the next unoccupied ID, and if that shows a conflict by the time we're ready to merge it, increment it again. |
|
Thanks, @kfranqueiro. I’ve snagged the next unoccupied ID and will be ready to bump it once more if necessary. |
|
discussed on the TF call. need further research/testing/checking with native Japanese SR users to work out accessibility support of the "correct" way to mark these things up. |
|
Hello, @murata2makoto and @MakotoUeki. It’s a pleasure to meet you both. If you have time, I’d be very grateful for any feedback you might be willing to share on this pull request. Your perspectives and recommendations would be very valuable. Here are preview links for the new failure technique and three supporting examples: I’ve also authored a companion PR — #4830 — which mainly updates the existing H62 technique to remove usage of the deprecated Here are preview links for those: Thank you very much for your time and consideration. |
4 participants
Resolves #4746.
Preview links:
<abbr title>to convey ruby annotations<sup>to convey ruby annotations<span>to convey ruby annotations