Your Name: Jonathan Altman
Your twitter handle: @async_io
A few words about yourself: Whole-system engineer, software engineer who isn't good at generating graphically pleasing front-ends from scratch
Talk title: Web Accessibility: Less Stick, More Carrot
Talk abstract:
Typically, 508 compliance is done by hiring consultants to either explain everything we did wrong with our front end or to either implement the accessibility or sit with the developers to tell them how as they do it. Wouldn’t it be better if we had our toolkits make it easier to be better on accessibility compliance. Remember Twitter Bootstrap? Until it came along, while a developer could make a decently laid-out, well-designed front end without being a graphic designer, it was harder. Shouldn’t we be making our React/Vue/Angular/Web Components components similarly easy to use by incorporating accessibility in them?
Talk will cover what’s wrong about accessibility process today, what developer experience we should be providing to developers building front-ends, and an exploration of how to start making accessibility easy in at least one front-end toolkit (probably React+Semantic-UI or maybe React-bootstrap).
Expected length: 30-45 minutes
Available months: July or later
Your Name: Jonathan Altman
Your twitter handle: @async_io
A few words about yourself: Whole-system engineer, software engineer who isn't good at generating graphically pleasing front-ends from scratch
Talk title: Web Accessibility: Less Stick, More Carrot
Talk abstract:
Typically, 508 compliance is done by hiring consultants to either explain everything we did wrong with our front end or to either implement the accessibility or sit with the developers to tell them how as they do it. Wouldn’t it be better if we had our toolkits make it easier to be better on accessibility compliance. Remember Twitter Bootstrap? Until it came along, while a developer could make a decently laid-out, well-designed front end without being a graphic designer, it was harder. Shouldn’t we be making our React/Vue/Angular/Web Components components similarly easy to use by incorporating accessibility in them?
Talk will cover what’s wrong about accessibility process today, what developer experience we should be providing to developers building front-ends, and an exploration of how to start making accessibility easy in at least one front-end toolkit (probably React+Semantic-UI or maybe React-bootstrap).
Expected length: 30-45 minutes
Available months: July or later