This article is within the scope of WikiProject United States, a collaborative effort to improve the coverage of topics relating to the United States of America on Wikipedia. If you would like to participate, please visit the project page, where you can join the ongoing discussions.
This article is within the scope of WikiProject Volleyball, a collaborative effort to improve the coverage of Volleyball on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.VolleyballWikipedia:WikiProject VolleyballTemplate:WikiProject VolleyballVolleyball articles
This article is within the scope of WikiProject Women's sport (and women in sports), a WikiProject which aims to improve coverage of women in sports on Wikipedia. For more information, visit the project page, where you can join the project and/or contribute to the discussion.Women's sportWikipedia:WikiProject Women's sportTemplate:WikiProject Women's sportWomen's sport articles
Latest comment: 2 months ago4 comments2 people in discussion
@Koavf: I appreciate you describing the accessibility issues you resolved in your recent edit; I was previously unaware of these. I've produced a table (below) that accommodates MOS:DTAB specifications, and I'd like your input on it first. MOS:FONTSIZE permits text rendered at 85% or higher, so I honestly don't see a problem with rendering it at 95% here, which would render it at the same size as the prose text. Neither MOS:DTAB nor MOS:DTT seem to mandate a specific colour or distinction between data columns, so I used style="background" to paint the "Team" column's data cells the same as the rest of the table's data cells. MOS:TABLECAPTION also permits the use of style="text-align", so I used it to mimic a prose text heading. Would these changes be fine per MOS:ACCESS, or would it run into some other accessibility issues I'm also unaware of?
Your willingness to collaborate is beautiful and inspiring. I am fine with whatever styling (e.g. the text-align), but for me, I have a hard time reading 85% and sometimes even 90% font-sizes as some days my corneal dystrophy acts up and some days it doesn't. Since I am not someone who has regular (i.e. persistent) accessibility issues, I don't typically do something with my browser to adjust this, and I just struggle thru, so I always try to just change it to 100% unless there are something like 70 columns. As far as my limited understanding of accessibility issues, this matches everything that is required and you have done some wonderful work. Thanks, A--I really appreciate anyone willing to work with me on accessibility issues, as I tend to get very... testy? chippy? defensive? about it, which is not always appropriate. ―Justin (koavf)❤T☮C☺M☯ 04:26, 6 March 2024 (UTC)Reply
I appreciate the kind words and your perspective on the issue, though this is why I wanted it to be set at 95% specifically, not 85% or 90%. For some reason, Wikipedia renders text in wikitables a bit larger than prose text, and a reduction to 95% renders it at the same size as prose text. I figured if you're able to read prose text, you'd be able to read that, too. — AFC Vixen 🦊 16:35, 6 March 2024 (UTC)Reply
That's not what I'm seeing, but I'm not actually measuring it. And in terms of legibility to me in particular, I can read the above table without my eyes watering, yes. Thanks again. If you are motivated to help me with these table semantics issues (MOS:TABLECAPTION, MOS:COLHEADERS, col/row scopes, colors, etc.), then I will be your best friend forever. ―Justin (koavf)❤T☮C☺M☯ 19:15, 6 March 2024 (UTC)Reply
