@User I had a look at the calendar widget just now. It's a bit of a mixed bag, but more usable then the new treeview. In a screenreader's browse mode, things work reasonably well. The table is a proper table, so table navigation commands work, and hitting enter on a cell that has content in it does open the correct note. So, I'd say this view is ...usable, but not pleasant to use, and here's why. - Cells that have content (i.e. are clickable because they have a note associated with them) are not semantically differentiated from the rest, making them hard to recognize as having a note associated, mostly because clicking any day in the calendar will just create a new journal note for that day. This is reasonably easy to fix with a bit of ARIA. - If you can currently arrow through the calendar (i.e. use the arrow keys to focus a particular day in the table) then this does not currently work with screenreaders. There are established patterns for fixing something like this though so this should be easy to fix if we do a bit of research. If this is not currently possible, it would help immensely if it were to be, as it makes sure people don't have to fall back to a screen reader's browse mode implementation. Finally a slight sidenote, currently the only way to get the calendar view to work is to enable the webUI which also enables the inaccessible treeview 🙂