One of the best parts of working on large corporate and government websites is that these sites must comply with…

One of the best parts of working on large corporate and government websites is that these sites must comply with accessibility guidelines. Failing to do so exposes that website to the possibility of a law suit if it can be proven that the site is discriminating against people with disabilities for no reasonable reason.

Accessibility (a11y) compliance can seem onerous to web developers who generally learn things on the job and are often unaware of these requirements. It’s a fact however that accessible web sites are simply good web sites ie. sites in which the developer:

treats HTML tags the way they were intended to be used

respects the idea of user focus and the possibility of keyboard navigation

doesn’t use JavaScript to subvert the basic operation of the browser

respects the URL

doesn’t break the browser back button.

Being forced to think about these things not only makes websites usable by a wider range of people, it actually make websites more useful for everyone.

The hard parts of accessibility are in overcoming developer ignorance and in flagging problems. For that there are a number of automated tools and developer widgets. I believe that all developers of web sites, no matter how small, should learn to use these tools.

⚡️ WAlt is an alternative syntax for WebAssembly text format.

⚡️ WAlt is an alternative syntax for WebAssembly text format. It’s an experiment for using JavaScript syntax to write to as ‘close to the metal’ as possible. It’s JavaScript with rules. .walt files compile directly to WebAssembly binary format.

Highlights:

Write “close to the metal” JavaScript!

No C/C++ or Rust required, just typed JavaScript.

Zero dependencies 100% written in JS.

Fast compilation, integrates into webpack.

https://github.com/ballercat/walt

Slate respects URLs.

Slate respects URLs. This is so much better for the web than what most content producers do. This is also in contrast to Google’s utter contempt for URLs both in its own properties and what it does to the web with AMP pages.

URLs are good. They should be succinct, readable and useful. If the web was about one specific thing, it’d be about URLs.