# Conclusion

This guide covered the common accessibility issues and solutions, yet web content often goes beyond simple or common. This is where your institution's accessibility experts and web developers can help! Never be afraid to ask for help as we all benefit. Go forth and create good!

## Contributors welcome!

This guide is written in Gitbooks with files in Github to allow for easy collaboration. Additional contributors are welcome, either as writers or editors. It would be wonderful to create a series of easy to understand guides on accessibility. Topics could include deeper-dives into topics such as audio-visual accessibility and physical facilities accessibility. Anything that can make our library world more accessible would be welcome.

## Coming soon

* A content accessibility checklist/cheatsheet

## Contact Us

Version one of this guide was created by **Jerry Yarnetsky,** a Web Services Librarian at Miami University of Ohio. He can be reached at <jerry.yarnetsky@miamioh.edu>.

Was this guide used at your college? Was this guide useful? Run into issues? Do you have suggestions for the next version? Have questions? [**Drop us a line**](mailto:jerry.yarnetsky@miamioh.edu)**!**

## Creative Commons BY-NC-SA 4.0

Version 1.2 was created in 2024 by Jerry Yarnetsky of Miami University, Oxford, Ohio. This work is licensed under a [Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-nc-sa/4.0/).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.liba11y.org/tools-resources/endnotes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
