Jump to content

Wikipedia talk:Manual of Style/Accessibility

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
"WT:ACCESS" redirects here. For the related wikiproject talk page, see Wikipedia talk:WikiProject Accessibility.
"WT:COLOR" and "WT:COLOUR" redirect here. For WikiProject Color's talk page, see Wikipedia talk:WikiProject Color.

Accessibility of scrolling tables. Different template

[edit]

Graham87. You noted in this discussion, Talk:COVID-19 pandemic deaths/Archive 1#Scrolling versus expanded tables, that the scrolling tables in the related article (COVID-19 pandemic deaths) were not a problem. You said: "it doesn't affect totally blind screen reader users." Those were a particular set of scrolling tables discussed here:

I want to know if this is also true for the scrolling tables (from a different template) in this version of a list article with 3 scrolling tables:

This method for scrolling tables is discussed here:

--Timeshifter (talk) 14:22, 6 July 2024 (UTC)[reply]

@Timeshifter: They generally work fine here. The only exception is JAWS under Chrome, but I think that's a JAWS issue and not a problem with the tables per se ... the combination of JAWS and Chrome is having problems with all sorts of tables at the moment. Graham87 (talk) 14:32, 6 July 2024 (UTC)[reply]
All sticky headings use pure CSS. For screenreader users it should be just fine because of that. If anything, it's more likely to be a problem for people with partial blindness or for older users etc, as the position of the element changes, which might be confusing to some. I can also imagine that the max-height vertical scroller can be a bit of a problem for screenreader users on mobile phones, as having a vertical scroller within a vertical scroller can be confusing for discovery, but as long as there are no controls inside the vertical scroller, that too seems unlikely to cause a problem. —TheDJ (talk • contribs) 08:15, 8 July 2024 (UTC)[reply]

Collapsing on mobile

[edit]
Note that mobile versions of the website do not support collapsing, so any collapsible content will automatically be uncollapsed.

This seems out of date; it works just fine on my phone or when I try the mobile preview on my computer. I'll remove it for now but let me know if anyone objects. Closed Limelike Curves (talk) 19:13, 27 July 2024 (UTC)[reply]

Alt text for images

[edit]

Dear visually impaired readers of Wikipedia. I sometimes add alt text to images to aid accessibility. I aim to be as succinct as possible while also being as correct as possible. The latter goal tends to make the descriptions lengthier but I try to keep them under 250 words. I mention color because I think that's important even if some some of our visually impaired readers have been blind since birth. I am not visually impaired and I don't use screen readers. The reason I am writing is to ask for suggestions of things to avoid when writing alt text. Things that bother you in alt text that you wish the writers would not do. That way I could better understand things from the perspective of a person who uses alt text. By the way, I've also started to use AI image generators to see how well my descriptions can duplicate the image. It's an interesting experiment and the results suggest that a picture requires far far more than a thousands words to describe as is commonly said. Nevertheless, most of the time the descriptions are reasonable approximations. Jason Quinn (talk) 10:21, 13 August 2024 (UTC)[reply]

@Jason Quinn: Thanks very much for this. As a totally blind person from birth, I can't think of anything to add but I find it hard to evaluate alt text because I don't know what I'm missing; see my comments in this discussion. Graham87 (talk) 15:30, 13 August 2024 (UTC)[reply]

Alt text for icons in templates

[edit]

How should a template handle alt text on an icon, if the icon can be changed? Some templates need |alt= parameters for selectable images, but what about a template where the image should be purely decorative? Should it have an |alt= parameter, or should it use the same alt text consistently?

I'm asking about general best practices but will link examples that brought this up. {{Archive}} has a little filing cabinet icon, but this can be changed to anything. An alt parameter and link parameter were added after this edit request: Template talk:Archives/Archive 1#Accessibility improvement for image. I'm thinking though that it would likely be more straightforward to just always have the alt text be something like "archiving icon". I've searched through pages that make use of the "alt" parameter. It's rarely used and when it is used, it is usually "Icon of a filing cabinet". I've listed several examples of its usage below.

Page Alt text Image Description
Wikipedia talk:WikiProject Computing/Computer Programming task force/Archive Index File:Replacement filing cabinet.svg File:Replacement filing cabinet.svg Icon of a filing cabinet
User talk:Jsayre64 Oregon File:Oregon DEM relief map.gif Small map of Oregon
Template talk:Jct Jct File:Jct plate.svg License plate reading "JCT"
User talk:XAM2175/2023/06 Icon of a filing cabinet File:Replacement filing cabinet.svg Icon of a filing cabinet

Useful parameter or simpler to use standardized alt text regardless of icon image? Rjjiii (talk) 20:51, 23 August 2024 (UTC)[reply]

Yeah making the alt text "Archiving icon" sounds sensible to me. Graham87 (talk) 04:04, 24 August 2024 (UTC)[reply]
Purely decorative images should have no link and no alt text according to accessibility experts since ever. What's the concern with that option? Izno (talk) 04:10, 7 September 2024 (UTC)[reply]
If the template allows the image to be chosen on the page where it's used, an editor can choose an image that is not public domain or available under an equivalent license. All creative commons images need to link to the page with their attribution information. Rjjiii (talk) 04:33, 7 September 2024 (UTC)[reply]
The |alt= and |link= parameters are unrelated; the value of one does not affect the meaning of the other. Setting |link= to an empty string can be a problem. If use of the image requires attribution (this includes, but is not limited to, the CC BY and CC BY-SA licenses), we must be able to reach the file description page so that the attribution may be seen. Indeed, WP:EIS#Link says: Except for public-domain images, it must always be possible for the reader to reach the image-description page, so |link= should be used only with |thumb images. Setting |alt= to an empty string does not, of itself, violate any policies so is much less of an issue. But if Graham87 suggests |alt=Archiving icon, I would go with that 100%. --Redrose64 🌹 (talk) 09:16, 7 September 2024 (UTC)[reply]
Typically, though, there would already be a text heading or description conveying the same information. In that case, having alt text on the decorative image that replicates the text is superfluous. isaacl (talk) 15:43, 7 September 2024 (UTC)[reply]
If the image in a template like this needs to be linked for attribution, it'd be better if there was alt text on the image (despite its slight redundancy). Graham87 (talk) 09:10, 8 September 2024 (UTC)[reply]

Discussion at WP:HD § Accessibility question

[edit]

 You are invited to join the discussion at WP:HD § Accessibility question. -- Marchjuly (talk) 07:40, 28 August 2024 (UTC)[reply]

Mobile skin and block quotations

[edit]

Page watchers may be interested in Wikipedia talk:Manual of Style § Mobile skin and block quotations. Please feel free to participate there. Izno (talk) 04:07, 7 September 2024 (UTC)[reply]

WP:NOBR notes

[edit]

are there any acceptable uses for the HTML line break <br/>? on a recent edit of mine, I substituted a {{ubl}} template into the HTML line break, as this was not being used for a list but as a visual break for the default size, separating the series title from the year in a table, for visual harmony.

I have seen this sort of visual break in many articles that I have edited, especially less cared ones, but how should it be handled? is it COMPLETELY discouraged it, even for use cases where there is legitemately no factor other than aesthetics or what to do instead? Juwan (talk) 12:21, 19 September 2024 (UTC)[reply]

Not to hock my own slogan, but essentially as I understand it, break means pause. That is to say, line breaks are acceptable when they actually represent semantic breaks in content, perhaps roughly equivalent to a paragraph break. They should neither be used to create the appearance of lists nor to manually wrap a single block of text, but beyond that there are actually plenty of plausible applications. Infobox templates themselves actually use them a lot under the hood. Remsense ‥ 论 12:24, 19 September 2024 (UTC)[reply]
oh, that's actually a great essay! if you think it is appropriate please link it on the section, that's exactly what I was looking for. Juwan (talk) 12:49, 19 September 2024 (UTC)[reply]
It's incomplete at the moment, and I like the idea that others would link such things rather than me if they find it useful so that only useful things get linked, so if you think it would help others then go for it! Remsense ‥ 论 12:56, 19 September 2024 (UTC)[reply]
Line breaks are for visual appearance only, and so semantically they are equivalent to whitespace. Appropriate semantic markup should be used as applicable. Line breaks should be used sparingly. As browser widths change or other elements are added to the page, the page will automatically be laid out differently by browsers, and manual overrides can work against this process producing a pleasing result. isaacl (talk) 18:40, 19 September 2024 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Manual_of_Style/Accessibility&oldid=1246723218"