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.
Why so negative?
Nothing in that list was "negative". They were all dry factual statements. Tone policing people for being "negative" when they're not is in and of itself quite a negative thing.
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.
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 that will eventually lift everyone up. So don't worry about the "what about..." people, they want to bring everybody down
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…
Detailed criticism is meant to bring people up, not down. There are better web communities if the only thing you want to get is encouragements (not that encouragement is bad, but it's way cheaper than criticism). It's your choice to see the critique as "this is a roadblock", or "this could be a good roadmap item".
Nothing in that list was "negative". They were all dry factual statements. Tone policing people for being "negative" when they're not is in and of itself quite a negative thing.
Seriously? The very first line was negative:
"leaves a lot to be desired"
If you don't want to be considered a jerk, in polite company you would say something like "This is a nice project. I have a few suggestions and bugs regarding accessibility:"
I expected `tree` to allow multiple side by side (but still synced) timelines. For instance in your examples there'd be one line for European ops, and another for Japanese. Any plans to add that?
agree, the mode need to be renamed. tree can be misleading. suggestions are welcome
At the same time, this is not public infrastructure. This is a gift to you.
If someone gives you a broken gift you should tell them so they can return it to be mended..
If someone gives you a gift you think is broken, you ask them to empower you to help mend it. And if they offer to get it mended, you at least offer to go with them.
That said, yes accessibility should be prioritized.