Accessibility.
Last updated
The standard we build to, where this site stands today, and how to tell us when something does not work.
What this covers
The standard, the status, and how to reach us.
Atlerix Technologies, Inc. operates this website. This explains the accessibility standard we build to, where this site stands today, and how to tell us when something does not work.
It covers this website. Work we do for a client is governed by the written agreement for that work.
The standard we build to
WCAG 2.2, level AA.
We build to the Web Content Accessibility Guidelines, version 2.2, at level AA. It is the level most accessibility law references.
In practice that means a page should work without a mouse, at high zoom, on a small screen, and with a screen reader reading it aloud.
Where this site stands
Tested as we build.
Every page can be operated from the keyboard alone. Each one opens with a link that skips past the navigation, and every control keeps a visible focus indicator so you can see where you are. Text meets the contrast the standard asks for. Pages reflow to a 320 pixel screen without scrolling sideways. Movement is removed for anyone whose system asks for reduced motion; fades that confirm a control still run.
The site has not yet been tested by someone who uses a screen reader every day. Automated checks and careful building catch a great deal, and they do not catch everything. Until that testing happens we describe this page as a work in progress. We do not claim the site conforms.
What we know is outstanding
The list as it stands today.
A full pass with a screen reader, and testing with people who rely on assistive technology, not our own checks alone.
We would rather publish a short honest list than a claim we cannot stand behind. If you find something missing from it, the next section is the fastest way to tell us.
If something does not work
One address, and we will answer.
Email legal@atlerix.com. Tell us what you were trying to do and what happened instead. If you can, say which page you were on and what device or software you were using. That detail is usually what makes a problem findable.
We treat this as a fault to be fixed, not feedback to be filed. We will tell you what we found and let you know when it is corrected.
The sites we build for clients
The same standard applies.
We build client websites to the standard described here. Accessibility is part of building a page properly, not an extra quoted separately at the end.
We do not install accessibility overlay widgets. They advertise instant compliance from a single line of script, they do not fix the markup underneath, and many of the people they claim to help have said plainly that they get in the way.
The pages that go with it.
This page covers how the site is built. What happens to anything you send through it, and the terms for using it, are set out separately.