Accessibility at the Reno Jazz Orchestra
We want everyone to be able to find a concert, read about the musicians, and buy a ticket — whatever device or assistive technology they use. This page explains where the website stands today, including the parts that are not right yet.
Tell us about a barrier
If something on this site stopped you, please tell us. We will reply, and we keep a record of what was reported and what we did about it. You do not need to know the technical cause — describing what you were trying to do is enough.
Danne Polk
Webmaster, Reno Jazz Orchestra
If you would rather not contact us directly, you can also ask us to send you concert information, dates, venues and ticket prices in another format — large print, plain text by email, or read to you over the phone.
What we are aiming for
This site is built to WCAG 2.2 Level AA, the international standard for web accessibility. As an organisation that receives federal and state funding, we are also covered by Section 504 of the Rehabilitation Act.
We claim partial conformance. The pages we have rebuilt meet the standard as far as we have been able to verify. Pages still running on our previous website do not, and we are replacing them section by section. We would rather say that plainly than claim more than we can show.
This statement was last reviewed on August 20, 2026.
What we have done
Reading the site
- Every text colour has been measured against the background it sits on, and meets or exceeds the required contrast. The measurements are built into the site’s stylesheet as an automatic check, so a colour that fails cannot be added by accident.
- Text can be enlarged using your browser’s zoom without content being cut off or overlapping.
- Links are underlined, not just coloured, so they are still obvious if you cannot distinguish the red.
- Concert dates and times are written out as real text, not only shown on poster images.
Using the site
- Everything can be operated with a keyboard. The menus use ordinary links and buttons, and Escape closes anything that has opened.
- Whatever you have selected is shown with a clear outline that we never remove.
- A “Skip to main content” link at the top of every page lets you jump past the navigation.
- Buttons and links are large enough to tap accurately — 44 by 44 pixels, which is above the standard’s minimum.
- If you have asked your device to reduce motion, the site respects that.
How it is built
- Pages use proper headings, lists and landmarks so that screen readers can navigate them.
- The visual order of the page matches the order it is read in. We chose not to rearrange content with styling, because that separates what you see from what a screen reader announces.
- Buttons that repeat — several “Get tickets” buttons on one page, for example — carry hidden text naming the date they belong to.
What is not right yet
These are the things we know about. Listing them is not an excuse — it is how we keep track, and how you can tell whether the problem you hit is one we already know about.
- We have not yet tested with a screen reader. The site is built to work with one, but built and tested are different things, and we are not going to claim the second. This is our next piece of work.
- Older pages are still being replaced. Anything outside the concert listings is still served by our previous website, which was not built to this standard.
- Some concert posters have no description. Older events were brought across from our previous system without alternative text for their artwork. The date, time, venue and description are always available as text on the page.
- Our PDF documents have not been checked, including the annual report. If you need anything from a PDF in another format, ask us and we will send it.
- Buying a ticket takes you to another company’s website. Those pages are not ours and we cannot fix them. If you have trouble completing a purchase, contact us and we will take your booking directly.
- Videos may not have accurate captions. Automatic captions are often wrong, particularly with music. We are reviewing them.
How we check
We keep a written conformance record listing every requirement of WCAG 2.2 Level AA, what we have measured, what we have built but not yet verified, and what fails. It is reviewed when we rebuild part of the site and when we apply for arts funding. If you would like a copy, ask Danne Polk.
We are grateful to anyone who takes the time to tell us something is wrong. It is the fastest way this gets better.