[Author of the 18F blog post here]<p>Accessibility and L10N are app-level concerns, not something that cloud.gov is going to be able to help with. However, 18F works on other efforts aimed at helping people do those things better, eg <a href="https:&#x2F;&#x2F;18f.gsa.gov&#x2F;2015&#x2F;09&#x2F;28&#x2F;web-design-standards&#x2F;" rel="nofollow">https:&#x2F;&#x2F;18f.gsa.gov&#x2F;2015&#x2F;09&#x2F;28&#x2F;web-design-standards&#x2F;</a><p>As for security and other devops concerns, which is what cloud.gov is about: This is why we&#x27;re in a scaling&#x2F;pilot phase now. A successful PaaS should reduce the depth of expertise needed to do those things right. That said, there are things like awareness of 12factor.net app design principles which are very unevenly distributed in government once you get outside of 18F. We will be concentrating on generating materials and documentation to make learning about those things in the context of cloud.gov as self-service as possible, and expand the pilot outward to those who need help even approaching the concept of a PaaS once we have more of those materials.