> For the complete documentation index, see [llms.txt](https://docs.acecentre.org.uk/aac-policy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecentre.org.uk/aac-policy/aac-policy.md). # AAC Policy A guide to developing an effective AAC policy in education settings ### Published by Ace Centre Hollinwood Business Centre Oldham OL8 3QL 0800 080 3115 [www.acecentre.org.uk](http://www.acecentre.org.uk/) Registered Charity No. 1089313 ### Coordinated by Katy Leckenby and Samantha McNeilly with the help of many colleagues at Ace Centre Edited by Tina Voizey This guide builds upon Ace Centre’s “Developing AAC Policies in Schools” document from 2001 with contributions from 25 professionals working in the field of AAC. It has been revised and updated to meet the needs of the current situation within education settings in England, leading the way forward for successful inclusion of AAC users, through the promotion of AAC policies. We would like to thank all those who contributed to the original document and recognise the work of the editors who pulled it together to share with the world; Sue Chinner Gillian Hazell Paul Skinner Pat Thomas Gill Williams \ We would also like to thank our Partnership schools who have driven and shaped this new edition; Brays School Co-Op Delius Greenfold School ### Copyright Copyright ©2024 by Ace Centre All rights reserved No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, without prior permission of Ace Centre. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.acecentre.org.uk/aac-policy/aac-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.