How can I write a book on code, where we are going, and accessibility as a grand ideal when we have no common language anymore? We have lost our focus and meaning. Our languages are fragmented. Our browsers monocultural. Where is the way forward?
2
2
13
The code is reflective of the design & business decisions? Frame it so the accountants, the CIOs, the CTOs get it which they then pass down to PM/BA/ Agile scrrum leader level to then end up in dev sprints?
1
1
2
I have issues with scrum and sprints I think they're very helpful in certain cases but I wouldn't build a whole company based on agile personally. The book is actually oriented toward as broad group because it isn't a learn to code book it's a challenge the status quo.
1
I see the best way to change the company culture is from the top, so the status quo changes company wide. As long as you get buy in by the key stakeholders, everything else should flow on from there.
1
1
We have to make accessibility a first entry point. My premise of redefining it is about exactly that is taking it out of an issue that the stakeholders have to talk about it all and making it a different concept than just about people with disabilities it's so much more.
1
I like the path you're taking with it
3
1
Replying to @absalomedia
Former HTML and xhtml working group chair @stevenpemberton called the mashup of what was going on with so-called HTML5 a 'monolithic lump' . It's more than a lump now... it's spread throughout the web like a cancer and we haven't found a cure. adding more crap is not helping!

Aug 18, 2022 · 12:54 PM UTC

1