Granapolis, South Nebrahoma, takes the following measures to ensure accessibility:

• Appoint an accessibility officer and/or ombudsperson.
• Provide continual accessibility training for our staff.
• Assign clear accessibility goals and responsibilities.
• Review all accessibility complaints and take all appropriate measures to provide equal access to content that becomes degraded.

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Granapolis is partially conformant with WCAG 2.0 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

Additional accessibility considerations Although our goal is WCAG 2.1 Level AA conformance, we have also applied some Level AAA Success Criteria: Images of text are only used for decorative purposes. Re-authentication after a session expires does not cause loss of data. Some videos have sign language interpretation

Feedback

We welcome your feedback on the accessibility of our website. Please let us know if you encounter accessibility barriers.

Phone: 123-456-7890
E-mail: accessibility@example.org
Visitor Address: 25 East Midland Avenue, Granopolis, SN 55432

We aim to respond to accessibility feedback within 2 business days, and to propose a solution within 10 business days. By completing the Form on this page you will be submitting your complaint to our Accessibility Coordinator.

Accessibility Coordinator

Brian Pope
Phone: 123-456-7890
E-mail: accessibility@example.org 

Plan of Action:

• Our website launched on 1/1/2023 and has been continuously edited for errors and new content additions
• Our content editors have been trained in WCAG 2.0/2.1 AA compliance and our approval process for publishing live content routes through our Accessibility Coordinator's office
• Legacy content such as documents are being reviewed and updated to meet current standards
• Our goal is to have our legacy content/ documents updated by (add date)

Build your own Accessibility Statement- 

https://www.w3.org/WAI/planning/statements/generator/#create 

Add a Form Builder Detail widget to this page in live- add a means to contact Accessibility Coordinator with complaints etc.

https://training.weknowgovernment.com/brian-s-example-pages/accessibility-feedback-and-requests/ 

What to consider when building your own Accessibility Statement:

• Have 1- funnel to it
• Be clear and concise
• Provide the ability for a person to get in contact with the right person if they need something- Use a Form if possible
• Follow through on your promises
• Make it easy to find for your visitors
  • mine is in the Header and the Footer of every page
  •