Many screen readers have the ability to call up a list of table captions and allow the user to jump directly to a table, which is very helpful for users who wish to revisit a table, or just look up information from a particular table. Where a table immediately follows a section heading, the caption becomes somewhat redundant if it simply repeats the heading, because screen readers can generally navigate to particular sections (and many users will be accustomed to navigating Wikipedia articles in that manner).
Sat, Nov 18
The choice of cells for markup for row headers and row scope is rather more problematical. Priority should be on adding scope for column headers as that should be easily achievable and much less likely to encounter opposition.
Aug 5 2017
Apr 15 2017
I think that whatever solution is reached, it should comply with relevant policies on the Wikipedias that are affected by it. On enwiki, (https://en.wikipedia.org/wiki/Wikipedia:Image_use_policy#Displayed_image_size), the following policy is in place:
Jun 30 2016
On English Wikipedia we have https://en.wikipedia.org/wiki/Module:Wikidata and https://en.wikipedia.org/wiki/Module:WikidataIB as examples of using Lua to get values from Wikidata. Each of them deals with multiple values for a property reasonably well in most cases, particularly when the values represent items that are internally wiki-linked.
Apr 13 2016
Just to answer the question in your example: although all text is related to a font-size setting, images are generally not sized in relation to the base font size. In other words, zoom is not synonymous with changing font size. Of course registered users wanting to change the balance between image size and font size don't need buttons to change font size, as they can set different default image sizes in their preferences.
Mar 27 2016
One of the problems that you will encounter is that the contents of an infobox are ultimately subject to consensus on individual articles (on the English Wikipedia at least). That implies, for example, that a "town template" can't have "country_required=true" coded into it as that level of decision-making is presently delegated to individual articles that use the template. The best we could accomplish without further central consensus is to ensure that an individual article can set something like "|country=_NODISPLAY_" which would override any template settings and suppress the display of the country field.
Sep 23 2015
The point about AAA-compliance is that we should be reaching it unless it is impractical to do so, when we can fall back to AA levels. Normally where we are simply picking a background/foreground combination, there is never a reason good enough to not comply with AAA, but when we have two different text colours that have to be distinguishable from each other as well as the background, there will arise circumstances when AAA is simply not possible. One example is when you are obliged to stick with greyscale or a single hue. There just isn't sufficient room for the contrast required by AAA at normal text sizes.
Sep 19 2015
Jul 13 2015
May 11 2015
This issue manifests itself most often when using "bundled references" - https://en.wikipedia.org/wiki/Wikipedia:Citing_sources#Bundling_citations - where a single citation calls up multiple sources. Semantically references are a list and what we really ought to be doing is for the bundled references to be a nested list within one item of the overall list. However, the visual presentation of references is often the dominant factor among editors and they try to make each reference in the bundle display on a new line. This is sometimes implemented by inserting a raw <p> tag into the wikitext to create a paragraph and that is (i) semantically incorrect; and (ii) an annoyance for users of screen readers. Using <br> is similarly problematical.