Accessibility

Commitment

Working toward WCAG 2.1 AA

We aim to meet the Web Content Accessibility Guidelines version 2.1 at level AA throughout the workspace and this website. That means designing for keyboard use as well as pointer use, keeping text readable against its background, labelling controls clearly, and making sure that the meaning of a page does not depend on colour alone. We treat accessibility as part of building the workspace well, not as an addition to it.

We review new pages and features against these guidelines as we build them, and we test with a range of tools and with people who use assistive technology. Where we find a gap, we record it and fix it.

In practice

What this means for the workspace

• Every interactive control can be reached and used with a keyboard.
• Text and background colours are chosen to keep contrast comfortable.
• Images carry alternative text that describes their purpose.
• Headings and landmarks follow a logical order for screen readers.
• Pages remain usable when text is enlarged.

Some people prefer to change colours, text size or spacing in their browser. The workspace is built to allow those changes without breaking the layout, so that a colleague can use the settings that suit them best.

Feedback

Tell us when something does not work

Accessibility is never finished, and your experience matters more than any checklist. If you meet a barrier in the workspace or on this site, write to [email protected] and describe what happened and what would have helped. We will look into it and reply, and where a fix is needed we will record it and address it as a priority.

If you would rather speak to a person, call us on +1 (215) 555-0142 or +1 (215) 555-0187. We are happy to talk through any part of the workspace and to suggest a way of working that suits your needs.

Ongoing

A lasting commitment

We keep this page current because accessibility is a continuing responsibility rather than a single project. As the workspace grows, our attention to it grows with the work. If you would like to know how a particular feature behaves with your own assistive technology, ask us, and we will find out and tell you plainly.

Assistive technology

Built to work with the tools people use

The workspace is written so that screen readers, magnification, speech input and keyboard-only use all make sense of it. Controls announce what they are and what state they are in. Pages follow a sensible order of headings, and the main content can be reached quickly without wading through the rest of the page. Focus moves in a way that a keyboard user can follow.

We test with more than one assistive technology, and we know that a single test pass can miss a real barrier. That is why feedback from the people who use the workspace day to day carries so much weight. If a particular technology behaves unexpectedly with the workspace, tell us, and we will investigate it as a priority.