[britta]

The Forest Service worked with 18F on this Open Forest project to enable people to buy Christmas tree permits online, which uses United States Web Design System components: https://openforest.fs.usda.gov/christmas-trees/forests

You can learn more about that project here, including the open source code: https://18f.gsa.gov/what-we-deliver/forest-service/ - and a few blog posts about it: https://18f.gsa.gov/tags/forest-service/

Both that Forest Service project and Federalist run on cloud.gov, which is a Platform as a Service operated by 18F.

(I work for 18F but don't officially represent it here.)

[dpcx]

https://openforest.fs.usda.gov/christmas-trees/forests has a pretty heavy dependency on Javascript (read: there's no fallback to anything non-javascript, so I get a white page). It feels like that goes against some of the things that 18F is about.

[Someone1234]

Pages don't need a fallback to non-Javascript in 2019. Accessibility technologies now fully support a JS enabled web, with accessibility standards following suit.

That leaves only those who have voluntarily disabled JavaScript (<1% of users), but fortunately those users are typically aware of how to resolve the issue of their own creation.

I've worked on public facing government websites (not 18F). We simply don't support this edge case, and our legal department supports our legal right to do so (in particular in relation to ADA requirements).

[msla]

> https://openforest.fs.usda.gov/christmas-trees/forests has a pretty heavy dependency on Javascript

And it doesn't even work with Javascript.