51–57 of 57 posts
The accessibility of this leaves a lot to be desired: - There are no landmarks. - The keyboard navigation works poorly. - There are no live regions to show changing content. - The markup is a sea of divs and spans, so there is no structure to the content. - There is no visible focus indicator. Some of the advanced layouts do not work at all in Safari, accessible or otherwise.
To be fair, a lot of simple stuff doesn't work on Safari. I recently noticed that Graylog's static navbar is broken on Safari, and only on Safari.
I use Safari because it offers great battery life but I don't expect it to work well everywhere, it sucks as a browser.
Earlier quoted context omitted.
thanks for your response. The project is still actively under development and accessiblity is something not yet fully implemented but the goal is to get there eventually very quickly. I have not advertised as fully accessible. Can you clarify a bit more on the keyboard navigation working poorly. may be logging a issue on the repo would help me to solve it quickly. as for problems in safari, i use a windows laptop and…
I understand the importance of accessibility (obviously) but I've see that there is a whole community whose first response to anything new is "what about..." as if its unthinkable that you would build a V0 without considering every possible special interest. I think everyone if pulled up by progress, and building something new, even if it doesnt work for everyone out of the gate is still a step in the right direction…
Nice! Many years ago I built something like that as my first JS project. Oh the days.
This is really cool! Does it support printing or converting to pdf well?