RINT, Routeboxes and more
[edit]
As many of you most likely will know, I have been improving {{Rail-interchange}} (or RINT for short) and {{Routebox entry}} over the past few days to make these local templates, rather than being dependent on Wikipedia's RINT template, having to import many small templates in the process. Thus far, I've achieved the following:
- I have created User:Wauteurz/RINT, which is a local version of {{Rail-interchange}}, which mostly uses {{Routebox entry}} to produce a result like so: U4 .
- I've adapted {{Routebox entry}} to accept more customisation. Right now, the additions are limited to roundovers, with the option to add no, somewhat or fully rounded corners. Examples: 4 SPR 7bis .
- I've written documentation, along with all symbols used for European networks for as far as these were present in the original RINT template link. Please note that round-overs may not have been added everywhere, and that some cities may not be complete yet. Colours or images may also be off or not working, as the template is very much still in development.
The following additions and/or changes are planned:
- Andree has shown interest in merging {{station}} and {{rint}}, but cannot do so so long as this possible replacement for RINT is still in the works.
- More options are planned for Routebox entry, most notably the option to output diamond shapes (Used on the New York Subway among others).
- A full coverage of the new RINT for all of Asia, Africa (currently lacking from RINT), Oceania and North and South America.
- Conditional markup for RINT, as currently exists for Germany:
{{User:Wauteurz/RINT|de|s|[№]}}with any number for [№] gives S41 , S56 , S357 or many others. - Optional: Compatibility between {{Routebox}} and {{Routebox entry}} leaves a lot to be desired. This can be changed to where Routebox entries (which will also be made via RINT) can be used in {{Routebox}}.
The goal of these changes is to give Wikivoyage a universal look to lines, rather than using thousands of PNG and SVG files from Commons rendered at different widths from 11 to 60px. I'd like you to answer the following questions:
- Are you in favor of replacing {{rint}} as it stands currently?
- If so, are you interested in replacing it with User:Wauteurz/RINT? (It will of course be renamed to "rint" once it is at a point where it can be replaced).
- Are you interested in more options to {{Routebox entry}}, and if so, what options would you like to see? I cannot guarantee that they can be achieved, but I can try.
- While I'm already at it, is there anything you would want RINT to do or support that it currently doesn't?
I'll continue working on the template for a while, as I would be very much in favor of using it for RINT (and not only because I have invested half of my week into the template). Anything in the template is subject to change if there is a desire for it. I'll be awaiting your answers and will be able to answer any of your questions or explain anything that may not be clear. Thank you in advance.
-- Wauteurz (talk) 11:02, 9 March 2018 (UTC)
- I am pretty sure that people have opinions on the matter. I'd like some confirmation before I plunge forward and replace templates. Speaking of: User:Wauteurz/RINT/box (the improved {{Routebox entry}} has had its functionalities expanded with customisation of border colours, rounded edges and mouse-over texts/tooltips. This is everything that I wanted to add to it. Since it is a non-destructive change, I'll plunge forward and update Routebox entry sometime soon unless anyone that wouldn't agree steps forward in the upcoming week. Furthermore, Andree has managed to make {{station}} call RINT without having to enter two templates (which can in circumstances break listings). We're rapidly approaching the goal and I for one would like to hear from the rest of Wikivoyage, so please, let your voice be heard!
-- Wauteurz (talk) 18:13, 11 March 2018 (UTC)
- Played with RINT and having fun with it... The images appear for the most part to link to a Wikipedia article - if not in Wikipedia they will link to Create a Wikivoyage page. (looks ok now) - thought I would mention that. Instead of linking to Wikipedia for U-Bahn (Berlin) I created maplinks instead or no link if OSM data not available (the listing or marker icons still go to their specific locations on a map). I didn't try mapshapes but managed to create the U-Bohn routes on a test map. Others such as S-Bohn etc. did not appear to have any OSM linkage (I may be incorrect on that note). Also, if Wikidata etc. were in sync, would it have been possible to use the image field found there instead. (probably not since not all are in wikidata or have some other image present). Other concern would be the size of the template and whether or not it may need to interact (using a case or switch statement) with another set of templates. (also just wondering if it can be done with a module and tables or not?) Anyhow; looks nice and hope users will find it useful. Best wishes! -- Matroc (talk) 02:04, 13 March 2018 (UTC)
- Forgot to mention - S-Bahn station Lichtenberg example - when one clicks on the Go icon - a map pops up - click on that icon on the map - the title box with image of station - the title S-Bahn station Lichtenberg followed by images for S5, S7, S75 and U5 bleeds over the edge of the box -- Matroc (talk) 03:40, 13 March 2018 (UTC)
Accessibility of map pins / tube map references
[edit]Hey there, I've been slowly preparing Wikivoyage for night mode. On the most part it's looking pretty good for that, but I'm noticing that we have many problematic accessibility issues in the standard version of the site. I'm using https://chromewebstore.google.com/detail/wcag-color-contrast-check/plnahcmalebffmaghcpcmpaciebdhgdf to get an overview of the issue in our pages.
- Problem 1 - Listing numbers
In our use of colors for maps - for example the map pins we use e.g. the Do, See etc.. templates we generate boxes with the pin number inside them. In the London article for example "Watch Tennis at Wimbledon" as a gray box with white text. This does not pass WCAG AA ( https://webaim.org/resources/contrastchecker/) so means that text is unreadable to certain users. - Problem 2 - the pins. For the pins themselves, I am not sure of the constraints at play here, but again the colors and backgrounds are not always accessible.
- I'm also seeing some accessibility issues in templates like VIC where the white text on blue is not accessible to some readers. In this case we can probably switch from white text to black text, or alter the background colors slightly (where possible).
Proposed solutions:
- I'd like to suggest that we move away from text on backgrounds for this sort of thing. For example instead we could move the color alongside the text it represents like in this example:
https://en.m.wikivoyage.org/w/index.php?title=London&diff=4847875&oldid=4847186&title=London&diffonly=1. Could we do something similar to this work for the See, Do etc.. templates?
- I think we should provide some better guidelines to editors - particularly in the template namespace. Do we have any existing pages that guide editors around how they use colors on this site?
Thanks in advance for your input and ideas!
Jdlrobson (talk) 22:52, 17 March 2024 (UTC)
- I can only really comment anything meaningful to your third point, being a major contributor to RINT myself. Editing labels like VIC would be highly problematic, as RINT's purpose is to reflect the labelling as it appears in place. The Victoria line simply uses that blue and that white. Switching the colours to anything else would make it more difficult for a reader to recognise the branding when visiting. Besides, a lot of these colours have passed design boards galore - TfL's lines are one of those. A single Chrome plugin flagging it as an accessibility issue is not something I would value over representing reality accurately. There no doubt are some labels that pose genuine accessibility issues, but they are best resolved in a case-by-case scenario.
- That said, I did change {{RbE}}, the template responsible for generating the RINT labels, to use red instead of light grey whenever a colour is not defined, as red is the most common line colour. That should resolve the biggest accessibility issue with RINT that can be fixed en-masse.
― Wauteurz (talk) 21:33, 18 March 2024 (UTC)- Yeah, while it is tempting to change the colours from an accessibility standpoint, changing the colour defeats the entire purpose of the template. --SHB2000 (talk | contribs | meta) 09:59, 20 March 2024 (UTC)