5 ms·
That report is brilliant. I'm impressed with the openness, clarity, and also the fact that javascript isn't mandatory to read it. Take note web devs!
by fodmap 5y ago
That report is brilliant. I'm impressed with the openness, clarity, and also the fact that javascript isn't mandatory to read it. Take note web devs!
- izietto 5y agoTake note web designers! I don't want to play the blame game, but if a page is designed in such a way that JS is required to implement it web devs (like me) can't do much about that!
- marcellus23 5y agoI think it's the responsibility of web devs to push back against designs like that. Designers aren't even aware of this kind of stuff -- it's your job to make the case why it's bad. If you push back and you get overridden, fine. But I doubt that most devs ever do that.
- open-source-ux 5y agoI really like the efforts of GOV.UK to make their content clear, unambiguous and easy to understand. In particular, avoiding jargon unless it is needed. Of course, jargon has it's place when it addresses a technical or specialised audience. From a different domain, here is an excellent blog post from 2019 on how to write clear health information for people with varying levels of literacy. (And no, it doesn't mean "dumbing down" your writing.) Pee and poo and the language of health: https://digital.nhs.uk/blog/transformation-blog/2019/pee-and-poo-and-the-language-of-health https://digital.nhs.uk/blog/transformation-blog/2019/pee-and...
- pabs3 5y agoTheir post about how they only use JS minimally: https://technology.blog.gov.uk/2016/09/19/why-we-use-progressive-enhancement-to-build-gov-uk/ https://technology.blog.gov.uk/2016/09/19/why-we-use-progres... https://news.ycombinator.com/item?id=12538144 https://news.ycombinator.com/item?id=12538144
- fodmap 5y agoThanks for those links, and thanks for your work!