4 ms·

> We also intend to build functionality for users to automatically generate accessible PDFs from HTML documents. This would mean that publishers will only need

by qqii 7y ago

> We also intend to build functionality for users to automatically generate accessible PDFs from HTML documents. This would mean that publishers will only need to create and maintain one document, but users will still be able to download a PDF if they need to. Oh I see you've added that. The problem with PDF to HTML is thst your trying to fit something static back into something dynamic. I also don't see how pdf rendering is any less complicated. There are many browser implementations that can easily render gov.uk without issues.

macspoofing 7y ago
This raises the question of how they create these 'HTML documents'. As far as I'm aware, there really isn't an HTML document format. More than likely, these documents will be created by some web-based system (maybe even proprietary and cloud-based, making portability extremely hard) and simply exported as PDF later. That's how every web-based content management system does it today. It's very convenient right now, but when it comes to document maintenance for the next few decades, I'm not sure that's better than something like PDF or ODF.
- petepete 7y ago
  The code is available on GitHub, you can see for yourself. It's mostly written in a customised markdown variant called Govspeak[0]. You appear to be jumping to ridiculous conclusions. Decisions on how we deliver content are made on the back of a huge amount of research. It's more accessible than it's ever been, other governments and organisations are following our lead. To suggest PDF, ODF or other crippled, inaccessible, OS-constrained formats over HTML - something everyone can read with any of their devices - shows you need to do more research before posting your ill-informed views. [0] https://github.com/alphagov/govspeak https://github.com/alphagov/govspeak Edit: Also, web page have plenty of other advantages. Indexed by every search engine, bookmarkable/shareable headings. What other medium offers that?
- qqii 7y ago
  You can find out more about how GDS operates on their github[0]. [0]: https://alphagov.github.io/ https://alphagov.github.io/

by qqii 7y ago

macspoofing 7y ago

This raises the question of how they create these 'HTML documents'. As far as I'm aware, there really isn't an HTML document format. More than likely, these documents will be created by some web-based system (maybe even proprietary and cloud-based, making portability extremely hard) and simply exported as PDF later. That's how every web-based content management system does it today. It's very convenient right now, but when it comes to document maintenance for the next few decades, I'm not sure that's better than something like PDF or ODF.

petepete 7y ago
The code is available on GitHub, you can see for yourself. It's mostly written in a customised markdown variant called Govspeak[0]. You appear to be jumping to ridiculous conclusions. Decisions on how we deliver content are made on the back of a huge amount of research. It's more accessible than it's ever been, other governments and organisations are following our lead. To suggest PDF, ODF or other crippled, inaccessible, OS-constrained formats over HTML - something everyone can read with any of their devices - shows you need to do more research before posting your ill-informed views. [0] https://github.com/alphagov/govspeak https://github.com/alphagov/govspeak Edit: Also, web page have plenty of other advantages. Indexed by every search engine, bookmarkable/shareable headings. What other medium offers that?
qqii 7y ago
You can find out more about how GDS operates on their github[0]. [0]: https://alphagov.github.io/ https://alphagov.github.io/