This includes thinking about what elements of the UI we want to read, and where it comes from, such as the sidebars from core, skins, wikipedia or other places.
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T396579 ☂ Play interface | |||
| Resolved | Viktoria_Hillerud_WMSE | T402617 Figure out what UI content to read | |||
| Resolved | Viktoria_Hillerud_WMSE | T402621 Identify and bind relevant UI strings to DOM elements |
Event Timeline
Relevant links to take into consideration:
- MediaWiki:Sidebar (e.g. “Navigation”, “Toolbox”, “Language” sections)
- Manual:Interface/IDs and classes
Suggested UI content to be read
I think the most useful interface elements to read aloud are the sidebar menus, e.g: Main Menu, Contents, Tools and Appearance, including the list items below them.
I think the page toolbar (image below) should also be included. It contains core functions like discussion, edit and history.
Also the link section in the top right (image below), but that's maybe not as urgent.
I think it could be a good idea to pick one section that isn't too complicated when you implement the general logic. I'd guess that this would be the page toolbar since it has no dynamic elements like the menus, but I don't know for sure.
Once that is done we can have more tasks for the remaining sections that extends the logic as needed.
That sounds good. So if I summarize, theee are the identified UI content we would want to read (ranked):
- Page toolbar
- Sidebar menus (e.g: Main Menu, Contents, Tools and Appearance, including the list items below them)
- Link-section top right
If this is what we probably will go with at the moment I would consider this particular task done?

