ktmud commented on pull request #13575: URL: https://github.com/apache/superset/pull/13575#issuecomment-797831138
> @ktmud all your counter arguments make sense. > Questions: > Have we done any research on the real need of addressing accessibility issue? Is the number big enough to justify investing 2X(engineer + design + product)to achieve the same feature goal? Superset is an OSS so to me, even 0.1% of users is a big enough number. Those challenges need to be categorized and looked at separately. And have we done enough exploration to prove that there's absolutely no way to solve these challenges within DND? What about keyboard shortcut? Have we done research on how the biggest BI tool in the market,Tableau, solved these challenges? @Steejay @mihir174 > > we have been constantly balancing requests for fixing broken NVD3 charts vs adding new Echarts, fixing broken FilterBox vs enhancing new native filter. We all have the same goal which is to provide the best UX to our users(i take back my statement of 'our goal is to get rid of select') It's the divided attention or lack of focus stopping us from getting to the ultimate goal. There is a movement called [Inclusive Design](https://en.wikipedia.org/wiki/Inclusive_design) I'm not sure if you have heard of. Basically it says instead of thinking things like accessibility as an investment that benefits only a small fraction of users, we should have the mindset of being inclusive from the very beginning. It doesn't necessary slow you down in the process, but will help you reach to more users. I have yet to see how supporting click-to-select would slow things down or introduce the so-called 2x maintenance cost. If we want to get rid of it because it doesn't sit well with the DnD experience, that's fine, but in terms of code maintenance, I find it hard to believe it'd be 2x the effort. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
