Accessibility Standards

Accessibility standards define technical requirements that digital systems must meet to be usable by people with disabilities. These standards translate human needs into measurable criteria: contrast ratios for visual impairment, keyboard operability for motor disabilities, text alternatives for screen reader users, and timing controls for cognitive accessibility. The Web Content Accessibility Guidelines (WCAG) published by the World Wide Web Consortium (W3C) provide the authoritative technical specification, while national legislation establishes legal compliance thresholds that reference specific WCAG versions and conformance levels.

WCAG (Web Content Accessibility Guidelines)

W3C technical standard defining accessibility requirements organised into four principles (Perceivable, Operable, Understandable, Robust) with three conformance levels (A, AA, AAA).

Conformance Level

Degree of accessibility compliance. Level A represents minimum accessibility. Level AA is the standard legal requirement in most jurisdictions. Level AAA provides enhanced accessibility but is not required for full conformance.

Assistive Technology

Hardware or software enabling people with disabilities to use digital systems: screen readers, screen magnifiers, voice recognition, switch devices, and alternative input methods.

VPAT (Voluntary Product Accessibility Template)

Standardised document format where vendors report their product’s conformance with accessibility standards. Used in procurement evaluation.

WCAG 2.2 Success Criteria Reference

WCAG organises requirements into four principles. Each principle contains guidelines, and each guideline contains testable success criteria at levels A, AA, or AAA. Meeting Level AA requires satisfying all Level A and Level AA criteria.

Principle 1: Perceivable

Information and interface components must be presentable in ways users can perceive.

Principle 2: Operable

Interface components and navigation must be operable by all users.

Principle 3: Understandable

Information and interface operation must be understandable.

Principle 4: Robust

Content must be robust enough for reliable interpretation by assistive technologies.

Legal Requirements by Jurisdiction

Accessibility legislation references WCAG conformance levels with specific compliance timelines. Organisations operating across jurisdictions must meet the most stringent applicable requirement.

For mission-driven organisations, the applicable standard depends on legal registration, funding sources, and service delivery locations. A UK-registered charity delivering services in the EU using US federal funding must satisfy the requirements of all three jurisdictions, making WCAG 2.1 AA the practical minimum standard.

Platform Accessibility Requirements

Each collaboration platform type presents specific accessibility challenges. The following requirements supplement general WCAG conformance with platform-specific criteria.

Email Clients

Document Formats

Document accessibility requires both creation standards and format selection. Native formats (.docx, .pptx) generally provide better assistive technology support than PDF, which loses structural information in conversion unless explicitly preserved.

Video Conferencing

Team Messaging

Intranet and Portal Platforms

Assistive Technology Compatibility Matrix

Platforms must support the following assistive technology combinations. Testing with a single screen reader is insufficient; behaviour varies significantly across combinations.

Compatibility testing must verify:

1. All interactive elements receive focus and announce their role
2. State changes (expanded, selected, checked) announce correctly
3. Error messages associate with relevant fields
4. Dynamic content updates announce via live regions
5. Custom components expose correct ARIA semantics

The minimum testing matrix for enterprise platforms covers JAWS on Windows, NVDA on Windows, VoiceOver on macOS, and VoiceOver on iOS. This combination addresses 85% of assistive technology users in typical organisational contexts.

Procurement Accessibility Criteria

Vendor evaluation must include accessibility assessment before contract signature. Post-deployment remediation costs exceed initial accessible procurement by a factor of 4-10.

Required Documentation

Evaluation Criteria

Score each criterion 0-3 (0=not met, 1=partial, 2=substantial, 3=full conformance). Minimum acceptable score: 2 average across all criteria, with no criterion scoring 0.

Contract Requirements

Include the following accessibility clauses in procurement contracts:

1. Vendor warrants conformance to WCAG 2.1 Level AA for all features available at contract signature
2. New features will conform to WCAG 2.1 Level AA at release
3. Vendor will provide updated VPAT within 30 days of major release
4. Vendor will remediate Critical and Major accessibility defects within 90 days of report
5. Organisation may audit accessibility conformance annually at vendor’s cost if VPAT accuracy is disputed
6. Persistent non-conformance (unresolved Critical defects beyond 180 days) constitutes material breach

Common Accessibility Failures

The following failures appear repeatedly across collaboration platforms. Use this reference for prioritising remediation and vendor evaluation.

Accessibility Statement Requirements

Public-facing services require an accessibility statement. The statement must appear on a dedicated page linked from every page footer.

Required Content

Statement Template Structure

Accessibility Statement for [Service Name]

[Organisation Name] is committed to ensuring digital accessibility for
people with disabilities. We are continually improving the user experience
for everyone and applying the relevant accessibility standards.

Conformance Status
This [website/application] is [fully/partially/not] conformant with
WCAG 2.1 Level AA. [Fully conformant means.../ Partially conformant
means the following areas are not fully accessible:]

Non-accessible Content
The following content is not accessible for the following reasons:
- [Description of inaccessible content]: [Reason: disproportionate burden /
  third-party content / under remediation until DATE]

Preparation of This Statement
This statement was prepared on [DATE]. The statement was prepared based on
[self-assessment / external audit by ORGANISATION / user testing].

Feedback
We welcome your feedback on the accessibility of [Service Name].
Please contact us:
- Email: [accessibility email]
- Phone: [phone number]
- [Other contact methods]
We aim to respond to accessibility feedback within [X] working days.

Enforcement Procedure
[For UK public sector: The Equality and Human Rights Commission (EHRC)
is responsible for enforcing the accessibility regulations. If you are
not happy with how we respond to your complaint, contact the Equality
Advisory Support Service (EASS).]

Statement Maintenance

Review and update the accessibility statement:

• Annually at minimum
• Within 30 days of completing accessibility audit
• Within 30 days of significant service changes
• Within 14 days of discovering major accessibility failures

See also

• Collaboration Platform Strategy
• Video Conferencing
• Document Management
• Accessibility Testing
• Vendor and Licensing Management