[ndarilek]

No worries, I get that we're probably not a demographic you've considered, and like I said, I don't even know if in the end this tool will work for me.

To give you an idea of what I'm thinking of, I've looked into https://github.com/dennybritz/neal-react (unfortunately the hosted demo appears to no longer be up.) I'm sure this will bring out the "JavaScript shouldn't be abused like this!" haters, and I'm not the biggest React fan, but I like that I can position a few high-level components without having to think "I need 2 divs, one that's a panel, one that's X width and another 12-X, etc." Granted, I've never built anything with this React library and don't even know if it looks good, but it's closest to what I want in a page design system. Just give me a few high-level blocks that are responsive and look good, and I'll go from there.

[cameronrohani]

I recently read a really great book about issues similar to this called "politics of design". Making things more accessible to everyone honestly really excites me. I hope that every time I ever make something I get called out on all of it's accessibility flaws. So thank you for bringing it to light :)

[astronautjones]

This probably sounds idiotic, but I am so wildly inspired by how much more coherent your presence, even here on HN is, as opposed to people who can see. Big up and I hope you have all the success you seek

[rhizome]

It's a common sentiment on HN that degradability and accessiblity are time and money wasters that have no real value since screenreaders can handle JavaScript now.

[mrexroad]

Examples?