Accessibility statement.

Policy updated August 2026

Commitment

ASPC aims to make its website, research, and institutional information usable by the widest practical audience.

The current accessibility target is the Web Content Accessibility Guidelines 2.2 at Level AA. Accessibility is treated as an ongoing responsibility involving design, content, code, downloadable documents, testing, and user feedback rather than a one-time certification.

Current features

• Keyboard-accessible navigation and controls
• Visible focus indicators and skip navigation
• Responsive layouts and scalable text
• Reduced-motion support
• Alternative text for meaningful imagery
• Accessible HTML editions for publications
• Semantic headings, labels, lists, tables, and status messages
• Keyboard operation for archive search suggestions and filters

Publications and alternative formats

Every ASPC publication is provided as an accessible HTML edition in addition to its designed PDF edition. The HTML version should be used when a PDF’s page-oriented layout, tables, or reading order creates a barrier. Visitors may request assistance locating a document or ask whether another practical format can be provided.

Links to source publications on external government websites are controlled by the issuing institution. ASPC cannot alter those files but welcomes reports identifying a source that is difficult to access so an alternative official edition can be located where available.

Known limitations

Designed PDFs may not provide the same reflow and navigation experience as their HTML equivalents. Complex source tables, external documents, and third-party pages may also have limitations outside ASPC’s control. Very large text settings or browser-level overrides can occasionally affect decorative layouts, although the underlying information should remain available.

ASPC prioritizes barriers that prevent navigation, form submission, document access, search, or comprehension of essential information.

Testing and maintenance

Reviews should include keyboard-only use, visible focus, heading structure, labels and instructions, color contrast, zoom and text scaling, narrow-screen reflow, reduced motion, alternative text, status announcements, internal links, and representative screen-reader checks. New templates and substantive interface changes should be reviewed before release.

Report a barrier

Use the website-issue category on the contact page and include the page address, task, device, browser, and barrier encountered. Do not send sensitive information.

ASPC aims to acknowledge actionable accessibility reports within five business days. Resolution time will depend on the nature of the barrier and whether an external source or service is involved.