Buildmorphic

Accessibility

The aim is WCAG 2.1 AA. Tell us where it falls short.

What has been done

Plain HTML with headings in order, labels on every field, and a visible outline on whatever has the keyboard focus. Nothing needs a mouse. Nothing needs scripts to be readable. Colour is never the only way something is signalled.

Text resizes with the browser, the layout works down to a phone, and motion is switched off for anyone whose system asks for that.

Where it is weaker

The site is dark only. There is no light theme, and there is not going to be one.

Source code is shown in a scrolling table with line numbers, which is awkward to read aloud. The raw file and the zip are plainer alternatives.

Project websites are written by their owners, so their accessibility is down to them, not to us.

If something blocks you

Say so and it gets fixed. Contact is through the site, and a report on any project page reaches a person. There is no deadline on this beyond as soon as it can be done.