Accessibility statement

Our accessibility target is WCAG 2.2 level AA on every page, in all
site languages and both colour themes. The known partial criterion
is described below. This statement records our checks, their tested
coverage and how to report a barrier.

What is checked before a release

The release gate runs automated checks on representative pages
across templates and all site languages, in both colour themes. A
failure stops publication; the checks establish the results for the
tested pages and conditions.

  * Structure, names and contrast. axe-core audits names, roles,
landmarks, heading order and colour contrast, with its best-practice
rules switched on as well as the WCAG ones.

  * The keyboard. A real Tab key is pressed from the top of a page
to the bottom, and every stop is checked for a focus indicator that
can be seen and that nothing covers. The first stop is a link
straight to the content.

  * Target size. Targets are checked against the 24 by 24 CSS-pixel
minimum, with the inline and spacing exceptions in criterion 2.5.8.

  * Spacing and larger text. The page is laid out once with wider
line, letter, word and paragraph spacing and once with its text at
twice the size, and either way must lose no content and gain no
sideways scroll.

  * Readable lines. Measured prose is checked for at most 80
characters per line (40 for Chinese, Japanese and Korean scripts),
left alignment of wrapped multi-sentence text, line spacing of at
least

  1.5 and paragraph spacing. These checks exercise reading-layout
requirements from the AAA criterion 1.4.8 Visual Presentation.

Two more are run on demand rather than before every release. One
lays the pages out 320 CSS pixels wide, the width 1.4.10 Reflow is
written for, and checks that nothing needs a sideways scroll. The
other stretches every string of the interface to up to two and a
half times its length, as an automatic translation may, and checks
that the layout holds.

Built to be read any way

  * Text links use underlines. Buttons, cards and navigation also
use shape and visible labels to identify their actions.

  * Movement is ornament only: the turning cogs, the portrait and
the brand mark. All of it stops when your system asks for reduced
motion.

  * The site runs without JavaScript. Complete lists, links and
menus use HTML, CSS and the browser's native controls.

  * Every page declares its language to help browsers and assistive
technology select the appropriate language.

  * Photographs carry text alternatives. Credits for the band
photographs are included in the accessible markup.

The pages are written in HTML, CSS and SVG, with WAI-ARIA where HTML
alone does not name something, and every page is complete without
executable JavaScript.

The one criterion met in part

1.4.13 Content on Hover or Focus. The current CSS labels remain
visible while you move the pointer onto them. They cover other
content and have no keyboard dismissal control, so this criterion is
met only in part.

Each label repeats its icon’s accessible name. Moving the pointer or
focus away closes it.

What does not apply

Some criteria concern things this site does not contain:

  * audio and video, so captions, audio description and media
alternatives;

  * forms that send anything, so the criteria on input errors: the
contact page hands you to your own mail app or phone;

  * time limits of any kind;

  * gestures, dragging and device motion, which nothing here asks
for;

  * signing in, which this site never asks you to do.

Where the checks stop

Our evaluation has the following scope:

  * Automated findings apply to the pages, viewports, states and
browser engines actually tested.

  * Recorded manual checks cover selected keyboard and zoom
interactions; VoiceOver, NVDA and switch-device sessions are outside
that record.

  * A person judges link purpose, wording and meaningful reading
order.

  * Open-menu checks measure layout, targets and keyboard access;
contrast over its translucent fill needs separate review.

  * Image-backed contrast is measured at selected surfaces and
viewport widths.

  * Focused hosts share the templates but have their own overlays;
their rendered checks run on demand.

Tell us about a barrier

If something here stands in your way — a page you cannot reach, a
label that says the wrong thing, text you cannot read — write to
welcome@engineer.company with the address of the page and what
happened. A person reads every message, and we reply personally.

Want your own site held to the same checks? talk to us (every build,
not once a year).

hThis page on the web	URL:https://brand.engineer.company/accessibility/	brand.engineer.company	70
